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

Builder ffmpeg64-solaris10-i386 Build #13510

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

Projectffmpeg
Repositoryhttps://git.ffmpeg.org/ffmpeg.git
Branchmaster
Revisione3bcb9ac76c949bfa3c4c67ca47dfb153d8e82d4
Got Revisione3bcb9ac76c949bfa3c4c67ca47dfb153d8e82d4
Changes3 changes

BuildSlave:

unstable10x

Reason:

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

Steps and Logfiles:

  1. git update ( 12 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 ( 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:

NameValueSource
branch master Build
builddir /export/home/buildbot/slave/ffmpeg64-solaris10-i386 slave
buildername ffmpeg64-solaris10-i386 Builder
buildnumber 13510 Build
codebase Build
got_revision e3bcb9ac76c949bfa3c4c67ca47dfb153d8e82d4 Git
project ffmpeg Build
repository https://git.ffmpeg.org/ffmpeg.git Build
revision e3bcb9ac76c949bfa3c4c67ca47dfb153d8e82d4 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. Soham Kute

Timing:

StartMon Mar 30 01:08:22 2026
EndMon Mar 30 01:08:42 2026
Elapsed20 secs

All Changes:

:

  1. Change #262781

    Category ffmpeg
    Changed by Soham Kute <officialsohamkuteohnoyoudont@gmail.com>
    Changed at Mon 30 Mar 2026 01:01:39
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision dc8183377cd3c7a7294af68b6bc5108fba354011

    Comments

    avutil/tests/file: replace trivial test with error-path coverage
    The original test only mapped the source file and printed its content,
    exercising none of the error branches in av_file_map().
    
    Replace it with a test that maps a real file (path via argv[1] for
    out-of-tree builds) and verifies it is non-empty, then calls
    av_file_map() on a nonexistent file twice: once with log_offset=0 to
    confirm the error is logged at AV_LOG_ERROR, and once with log_offset=1
    to confirm the level is raised by one, covering the
    log_level_offset_offset path in av_vlog().  A custom av_log callback
    captures the emitted level independently of the global log level.
    The two error cases share a single for() loop to avoid duplication.
    
    Add a FATE entry in tests/fate/libavutil.mak with CMP=null since
    there is no fixed stdout to compare.
    
    Signed-off-by: Soham Kute <officialsohamkute@gmail.com>

    Changed files

    • libavutil/tests/file.c
    • tests/fate/libavutil.mak
  2. Change #262782

    Category ffmpeg
    Changed by Soham Kute <officialsohamkuteohnoyoudont@gmail.com>
    Changed at Mon 30 Mar 2026 01:01:39
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision 9bf999c24ffbbfcde7f6722f4c1081c629a7a30e

    Comments

    avcodec/tests: add encoder-parser API test for H.261
    Add tests/api/api-enc-parser-test.c, a generic encoder+parser round-trip
    test that takes codec_name, width, and height on the command line
    (defaults: h261 176 144).
    
    Three cases are tested:
    
    garbage - a single av_parser_parse2() call on 8 bytes with no Picture
    Start Code; verifies out_size == 0 so the parser emits no spurious data.
    
    bulk - encodes 2 frames, concatenates the raw packets, feeds the whole
    buffer to a fresh parser in one call, then flushes.  Verifies that
    exactly 2 non-empty frames come out and that the parser found the PSC
    boundary between them.
    
    split - the same buffer fed in two halves (chunk boundary falls inside
    frame 0).  Verifies the parser still emits exactly 2 frames when input
    arrives incrementally, and that the collected bytes are identical to
    the bulk output (checked with memcmp).
    
    Implementation notes: avcodec_get_supported_config() selects the pixel
    format; chroma height uses AV_CEIL_RSHIFT with log2_chroma_h from
    AVPixFmtDescriptor; data[1] and data[2] are checked independently so
    semi-planar formats work; the encoded buffer is given
    AV_INPUT_BUFFER_PADDING_SIZE zero bytes at the end; parse_stream()
    skips the fed chunk if consumed==0 to prevent an infinite loop.
    
    Two FATE entries in tests/fate/api.mak: QCIF (176x144) and CIF
    (352x288), both standard H.261 resolutions.
    
    Signed-off-by: Soham Kute <officialsohamkute@gmail.com>

    Changed files

    • tests/api/Makefile
    • tests/api/api-enc-parser-test.c
    • tests/fate/api.mak
    • tests/ref/fate/api-enc-parser
    • tests/ref/fate/api-enc-parser-cif
  3. Change #262783

    Category ffmpeg
    Changed by Soham Kute <officialsohamkuteohnoyoudont@gmail.com>
    Changed at Mon 30 Mar 2026 01:01:39
    Repository https://git.ffmpeg.org/ffmpeg.git
    Project ffmpeg
    Branch master
    Revision e3bcb9ac76c949bfa3c4c67ca47dfb153d8e82d4

    Comments

    avformat/tests: add FATE tests for yuv4mpegpipe pixel formats
    The existing fate-lavf-yuv420p.y4m covers only the default format.
    Add four entries that pass -pix_fmt explicitly to the lavf_video
    macro: yuv422p, yuv444p, yuv411p, and gray.
    
    These exercise the branches in yuv4mpegpipe_write_header() that write
    the "C422", "C444", "C411", and "Cmono" chroma descriptor strings in
    the stream header.  All four are gated on ENCDEC(RAWVIDEO,YUV4MPEGPIPE)
    and added to FATE_LAVF_VIDEO_SCALE so they inherit the requirement for
    CONFIG_SCALE_FILTER that lavf_video's -auto_conversion_filters needs.
    
    Reference files were generated from the actual encoder output and
    follow the md5+size+CRC format used by the other lavf references.
    
    Signed-off-by: Soham Kute <officialsohamkute@gmail.com>

    Changed files

    • tests/fate/lavf-video.mak
    • tests/ref/lavf/gray.y4m
    • tests/ref/lavf/yuv411p.y4m
    • tests/ref/lavf/yuv422p.y4m
    • tests/ref/lavf/yuv444p.y4m