Builder ffmpeg-solaris10-i386 Build #13771

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpeg-solaris10-i386' 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 ( 12 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 ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Kacper Michajłow

   kasper93ohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #267401

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Sat 16 May 2026 13:09:56
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	dc74fe70b28df8ff69f99b693665163bf9a6a16a

   Comments

   avformat/demux: use correct close function for custom io
   You may look and think `AVFMT_FLAG_CUSTOM_IO` check is enough, but this
   is not what it seems. This flag means that user provided custom
   AVIOContext, before creating AVFormatContext and it should not be
   closed. However nested sub-demuxers may still open an temporary io, and
   those have to be closed and use correct io_close2 function.
   
   You can see 0dcac9c3f0f8f32009098edb704fac4b08bac951 and
   ef01061225088c4945f5e309bc695ea5beb2a867 where this flag is cleared for
   nested opens to avoid leaking those.
   
   lavf micro version bumped so API users can know if it is safe to use
   custom io.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • libavformat/demux.c
   • libavformat/version.h