Builder ffmpegsos-solaris10-i386 Build #13474

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpegsos-solaris10-i386' triggered this build

Steps and Logfiles:

1. git update ( 4 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 ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_sos.sh' failed ( 2 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 #259933

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Thu 05 Mar 2026 17:02:04
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	6e322fa58263d61a5517182010405c09656673af

   Comments

   configure: warn about excessive stack usage
   Use a 120 KiB per-function threshold. This roughly matches the default
   thread stack size on Musl, which is 128 KiB, leaving some headroom for
   caller frames.
   
   This warning draws attention to functions in the codebase that may have
   excessively large stack frames. A few functions could benefit from
   reducing their frame size.
   
   120 KiB is a reasonable limit. If a function requires more stack, it
   likely would benefit from restructuring the code.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • configure