Builder ffmpeg64-solaris10-sparc Build #12862

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 ( 8 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 ( 9 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. Dariusz Marcinkiewicz

   darekmohnoyoudont@google.com

Timing:

All Changes:

:

1. Change #252449

   Category	ffmpeg
   Changed by	Dariusz Marcinkiewicz <darekmohnoyoudont@google.com>
   Changed at	Tue 16 Dec 2025 22:53:10
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	c41155e614bec5891f9adb78c9d2ca43270d9e02

   Comments

   libavcodec: support frame dropping in libvpxenc
   vp8 encoder can be configured to drop frames, when e.g. bitrate
   overshoot is detected. At present the code responsible for
   managing an internal fifo assumes that we will get an output frame per
   each frame fed into encoder. That is not the case if the encoder can
   decide to drop frames.
   
   Running:
   ffmpeg -stream_loop 100 -i dash_video3.webm -c:v libvpx -b:v 50k
   -drop-threshold 20 -screen-content-mode 2 output.webm
   
   results in lots of warnings like:
   [libvpx @ 0x563fd8aba100] Mismatching timestamps: libvpx 2187 queued
   2185; this is a bug, please report it
   [libvpx @ 0x563fd8aba100] Mismatching timestamps: libvpx 2189 queued
   2186; this is a bug, please report it
   
   followed by:
   [vost#0:0/libvpx @ 0x563fd8ab9b40] [enc:libvpx @ 0x563fd8aba080] Error
   submitting video frame to the encoder
   [vost#0:0/libvpx @ 0x563fd8ab9b40] [enc:libvpx @ 0x563fd8aba080] Error
   encoding a frame: No space left on device
   [vost#0:0/libvpx @ 0x563fd8ab9b40] Task finished with error code: -28
   (No space left on device)
   [vost#0:0/libvpx @ 0x563fd8ab9b40] Terminating thread with return code
   -28 (No space left on device)
   
   The reason for the above error is that each dropped frame leaves an
   extra item in the fifo, which eventually overflows.
   
   The proposed fix is to keep popping elements from the fifo until the
   one with the matching pts is found. A side effect of this change is that
   the code no longer considers pts mismatch to be a bug.
   
   This has likely regressed around 5bda4ec6c3cb6f286bb40dee4457c3c26e0f78cb
   when fifo started to be universally used.
   
   Signed-off-by: Dariusz Marcinkiewicz <darekm@google.com>

   Changed files

   • libavcodec/libvpxenc.c
   • libavcodec/version.h