Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Builder ffmpeg64-solaris10-i386 Build #14137

Results:

Failed

SourceStamp:

Projectffmpeg
Repositoryhttps://git.ffmpeg.org/ffmpeg.git
Branchmaster
Revision30afbfcf6fe590b0ff58e0194223fec6353fffc5
Changes3 changes

BuildSlave:

unstable10x

Reason:

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

Steps and Logfiles:

  1. git updating ( 6 secs )
    1. stdio
  2. shell  
    1. - no logs -
  3. shell_1  
    1. - no logs -
  4. shell_2  
    1. - no logs -
  5. shell_3  
    1. - no logs -
  6. shell_4  
    1. - no logs -
  7. shell_5  
    1. - no logs -

Build Properties:

NameValueSource
branch master Build
builddir /export/home/buildbot/slave/ffmpeg64-solaris10-i386 slave
buildername ffmpeg64-solaris10-i386 Builder
buildnumber 14137 Build
codebase Build
project ffmpeg Build
repository https://git.ffmpeg.org/ffmpeg.git Build
revision 30afbfcf6fe590b0ff58e0194223fec6353fffc5 Build
scheduler schedule-ffmpeg64-solaris10-i386 Scheduler
slavename unstable10x BuildSlave
workdir /export/home/buildbot/slave/ffmpeg64-solaris10-i386 slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Niklas Haas

Timing:

StartTue Sep 15 10:24:19 2026
EndTue Sep 15 10:24:26 2026
Elapsed6 secs

All Changes:

:

  1. Change #281864

    Category ffmpeg
    Changed by Niklas Haas <gitohnoyoudont@haasn.dev>
    Changed at Tue 15 Sep 2026 12:04:36
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision ac72d7905944206b6e036e61cfee38b927e6b0e0

    Comments

    avformat/shared: add -ignore_errors option
    This allows the shared: cache protocol to ignore errors in the underlying
    URL (e.g. HTTP server went down) and continue serving the cached data
    purely from the cache file. I'm not sure what a good name would be here,
    since -ignore_errors overlaps somewhat with -retry_errors, but I think the
    distinction is clear enough. (-ignore_errors keeps going after the inner
    protocol fails, -retry_errors will retry blocks that previously failed in
    the inner protocol)
    
    One slight change is that we now call ffurl_size() on ourself during
    init. This is safe, because the spacamap is already initialized by this
    point in time, and it also embeds the correct error handling and spacemap
    update logic.
    
    Default off because it's a possibly surprising change in behavior.
    
    Sponsored-by: nxtedition AB
    Signed-off-by: Niklas Haas <git@haasn.dev>

    Changed files

    • doc/protocols.texi
    • libavformat/shared.c
  2. Change #281865

    Category ffmpeg
    Changed by Niklas Haas <gitohnoyoudont@haasn.dev>
    Changed at Tue 15 Sep 2026 12:04:36
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision 6ca9e60b0093c256bda33c178da4988961e77c41

    Comments

    avformat/shared: add spacemap metadata for the number of cached blocks
    This can only ever be a lower bound in theory, because a process could crash
    exactly in between committing the cached block and updating the count, though
    that edge case is incredibly rare.
    
    This is a backwards-compatible addition so it doesn't require a cache version
    update. New clients will simply see a gross underestimate of the number of
    cached blocks, which means the upcoming option does not work retroactively,
    but I consider that a better trade-off than invalidating all existing cache
    objects for no reason.
    
    Sponsored-by: nxtedition AB
    Signed-off-by: Niklas Haas <git@haasn.dev>

    Changed files

    • libavformat/shared.c
  3. Change #281866

    Category ffmpeg
    Changed by Niklas Haas <gitohnoyoudont@haasn.dev>
    Changed at Tue 15 Sep 2026 12:04:36
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision 30afbfcf6fe590b0ff58e0194223fec6353fffc5

    Comments

    avformat/shared: add -cache_size_max option
    This allows users to limit the amount of cached data. Note that this is
    *not* a limit on the size of the file cached. For example, a 10 GB file can
    work with a 1 GB cache size limit if the user only ever plays some parts of
    the file (e.g. 1 minute from a 100 minute stream).
    
    After this point, s->read_only is simply turned on, giving us the expected
    fallback behavior for uncached blocks.
    
    Sponsored-by: nxtedition AB
    Signed-off-by: Niklas Haas <git@haasn.dev>

    Changed files

    • doc/protocols.texi
    • libavformat/shared.c