Builder ffmpeg64-solaris10-sparc Build #14302

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 ( 13 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 ( 0 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_64.sh' failed ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Thomas Devoogdt

   thomasohnoyoudont@devoogdt.com

Timing:

All Changes:

:

1. Change #281940

   Category	ffmpeg
   Changed by	Thomas Devoogdt <thomasohnoyoudont@devoogdt.com>
   Changed at	Wed 16 Sep 2026 19:03:53
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	62508d7629d820e1968016112d2d3594447a4fdb

   Comments

   fftools/ffplay: exit via do_exit() on termination signal
   sigterm_handler() called exit(123) directly, bypassing
   avformat_close_input() and therefore any protocol level shutdown, such as
   the RTSP TEARDOWN.  Set a flag instead and let the event loop leave
   through do_exit(), which keeps the 123 exit status.
   
   Add a hard exit on the 4th sigterm, similar to ffmpeg.
   
   Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>

   Changed files

   • fftools/ffplay.c

2. Change #281941

   Category	ffmpeg
   Changed by	Thomas Devoogdt <thomasohnoyoudont@devoogdt.com>
   Changed at	Wed 16 Sep 2026 19:05:34
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	9cf34b031f489dcecad5c579d0a22a956918cf36

   Comments

   avformat/rtpdec: propagate SRTP setup errors to the caller
   ff_rtp_parse_set_crypto() was void and dropped the ff_srtp_set_crypto()
   return value.  A rejected crypto suite therefore left srtp_enabled clear
   while RTSPStream.crypto_suite stayed set, and rtsp.c uses crypto_suite[0]
   as the sole guard for secure transport.  The session could thus be
   negotiated as SRTP while the RTP actually went out unprotected.
   
   Return the error instead and let ff_rtsp_open_transport_ctx() abort SETUP
   rather than continue with a half-initialised SRTP context.
   
   Signed-off-by: Thomas Devoogdt <thomas@devoogdt.com>

   Changed files

   • libavformat/rtpdec.c
   • libavformat/rtpdec.h
   • libavformat/rtsp.c