Builder ffmpeg64-solaris10-sparc Build #14004

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 5 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 ( 8 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 2 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_64.sh' failed ( 1 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Daniel Verkamp

   danielohnoyoudont@drv.nu

Timing:

All Changes:

:

1. Change #273265

   Category	ffmpeg
   Changed by	Daniel Verkamp <danielohnoyoudont@drv.nu>
   Changed at	Tue 30 Jun 2026 05:03:30
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	f1126f23380c805b4b8fd69351d189aeac8b892b

   Comments

   avformat/wavenc: Don't count padding in rf64 data chunk size
   When writing the trailer for a RF64 WAV file, the ds64 chunk's 64-bit
   version of the data chunk size incorrectly included the padding byte
   that may have been added by ff_end_tag() for the data chunk.
   
   Fix this by calculating the data chunk size before calling ff_end_tag().
   
   The data chunk padding byte is only needed when the data is not already
   a multiple of two bytes in length, which is fairly rare, requiring
   something like mono 8-bit or 24-bit PCM with an odd number of samples to
   trigger (and only with -rf64 auto or -rf64 always, neither of which is
   enabled by default), so this bug is not likely to have affected many
   real-world files.
   
   Signed-off-by: Daniel Verkamp <daniel@drv.nu>

   Changed files

   • libavformat/wavenc.c