Builder ffmpeg64-solaris10-sparc Build #10832

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 ( 16 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 ( 6 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 1 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. Derek Buitenhuis

   derek.buitenhuisohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #196002

   Category	ffmpeg
   Changed by	Derek Buitenhuis <derek.buitenhuisohnoyoudont@gmail.com>
   Changed at	Thu 25 Apr 2024 16:21:25
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	6d89fd4c27b2c907acaf44f923e624a24643a2ba

   Comments

   avformat/http: Rename parse_set_cookie_expiry_time to parse_http_date
   That is what it actually does, and it will be needed for more
   than the Expiry header soon.
   
   Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

   Changed files

   • libavformat/http.c

2. Change #196003

   Category	ffmpeg
   Changed by	Derek Buitenhuis <derek.buitenhuisohnoyoudont@gmail.com>
   Changed at	Thu 25 Apr 2024 16:21:25
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	2d5fa816fb94563de6ee8585430dcc9bfa4455da

   Comments

   avformat/http: Add support for Retry-After header
   429 and 503 codes can, and often do (e.g. all Google Cloud
   Storage URLs can), return a Retry-After header with the error,
   indicating how long to wait, asd either a date, or in seconds,
   before retrying again. If it is not respected by, for example,
   using our default backoff stratetgy instead, chances of success
   are very unlikely.
   
   Some references:
       * https://datatracker.ietf.org/doc/html/rfc6585
       * https://datatracker.ietf.org/doc/html/rfc7231#section-7.1.3
   
   This adds an AVOption to respect that header.
   
   Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>

   Changed files

   • doc/protocols.texi
   • libavformat/http.c
   • libavformat/version.h