Builder ffmpeg-solaris10-sparc Build #12419

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpeg-solaris10-sparc' triggered this build

Steps and Logfiles:

1. git update ( 12 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 0 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 0 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 7 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config.sh' failed ( 2 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Niklas Haas

   gitohnoyoudont@haasn.dev

Timing:

All Changes:

:

1. Change #242652

   Category	ffmpeg
   Changed by	Niklas Haas <gitohnoyoudont@haasn.dev>
   Changed at	Mon 11 Aug 2025 09:38:38
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	e29a99a975b722463c19d53f67e32f12f6dfe445

   Comments

   fftools/ffmpeg_enc: don't ignore user selected chroma location
   This code always ignored the user-provided enc_ctx->chroma_sample_location
   in favor of the location tagged on the frame. This leads to a very (IMHO)
   unexpected outcome where -chroma_sample_location works differently from the
   related options like -colorspace and -color_range, the latter of which
   override the frame properties as a consequence of being configured on the
   filter graph output.
   
   The discrepancy comes from the fact that the chroma sample location does not
   itself participate in filter graph negotiation.
   
   Solve the situation by only overriding the enc_ctx option if it was left
   unspecified by the user, and otherwise printing a warning if the requested
   parameter does not match the frame parameter.

   Changed files

   • fftools/ffmpeg_enc.c