Builder ffmpegsos-solaris10-sparc Build #13756

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpegsos-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 ( 10 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 ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Andreas Rheinhardt

   andreas.rheinhardtohnoyoudont@outlook.com

Timing:

All Changes:

:

1. Change #276798

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	934742548a3c3f34ceaef2116dda2810bacdf625

   Comments

   tests/checkasm/huffyuvencdsp: Avoid using static variable
   This has been done in order to use the same width
   for benchmarks of different instruction sets to
   make the benchmarks comparable. Yet it has a downside:
   Only one width would ever be executed when using --repeat.
   Luckily libcheckasm makes it easy to fix this:
   At the start of every test function, the internal state
   of rnd() is reset, so that it produces the same sequence
   of random values. So just removing the static variable works.
   
   This would also make this test trivially parallelizable.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/huffyuvencdsp.c

2. Change #276799

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	8984d7c239095f5fdaf2c55665386fdb0aa42183

   Comments

   tests/checkasm/sbcdsp: Avoid using static variable
   This has been done in order to use the same number of blocks
   for benchmarks of different instruction sets to
   make the benchmarks comparable. Yet it has a downside:
   Only one number would ever be executed when using --repeat.
   Luckily libcheckasm makes it easy to fix this:
   At the start of every test function, the internal state
   of rnd() is reset, so that it produces the same sequence
   of random values. So just removing the static variable works.
   
   This would also makes this test trivially parallelizable.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/sbcdsp.c

3. Change #276800

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	78193e6490b92b9749183beb0defd6c355f452aa

   Comments

   tests/checkasm/llviddsp: Fix crash with AVX2
   llviddsp functions typically operate on whole lines,
   i.e. the pointers are aligned to STRIDE_ALIGN. They
   can therefore avoid tail handling by just clobbering
   the padding (if any).
   
   The test gets a random width via 16 * av_clip(rnd(), 16, 128);
   in practice, it is very unlikely for rnd() to return
   a value between 16 and 128, so width is typically 16*16 or
   16*128. Buffers of this size are allocated later.
   
   When rnd() returns an odd number in the allowed range
   (this happens for the seed 4161216273), the buffers used
   in the test don't contain the padding that exists in actual
   usage, leading to invalid stores and also to segmentation faults
   (usage of aligned load instructions on unaligned addresses).
   
   Fix this by adding the necessary alignment to the buffers.
   
   Also don't use a static variable to store width (it is unnecessary,
   because since the switch to libcheckasm, rnd() always returns
   the same sequence of random numbers for test runs with different
   instruction sets) and use a really random width, not something
   that is mostly just one of two values and always mod 16.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/llviddsp.c

4. Change #276801

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	4a51f189ea288b2f0692a357fb2ee8fdeb935625

   Comments

   tests/checkasm/hpeldsp: Avoid using static variables
   This has been done in order to use the same height
   for each function for benchmarks of different
   instruction sets to make the benchmarks comparable.
   Yet it has a downside: Only one number would ever be
   executed when using --repeat, hiding potential bugs.
   
   Luckily libcheckasm makes it easy to fix this:
   At the start of every test function, the internal state
   of rnd() is reset, so that it produces the same sequence
   of random values. So just initialize the heights every time
   (and before actually testing any function).
   
   This also would make this test trivially parallelizable with --repeat.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/hpeldsp.c

5. Change #276802

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	4acf9f27062abbffb8eefd522df0d57355b29167

   Comments

   tests/checkasm/mpegvideo_unquantize: Avoid using static variables
   This has been done in order to use the same parameters
   that influence the number of elements to be processed
   sets to make benchmarks between different instruction
   sets comparable. Yet it has a downside: Only one parameter
   combination would ever be executed when using --repeat,
   hiding potential bugs.
   
   Luckily libcheckasm makes it easy to fix this:
   At the start of every test function, the internal state
   of rnd() is reset, so that it produces the same sequence
   of random values. So just initialize these parameters
   every time (and before actually testing any function).
   
   This also would make this test trivially parallelizable with --repeat.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/mpegvideo_unquantize.c

6. Change #276803

   Category	ffmpeg
   Changed by	Andreas Rheinhardt <andreas.rheinhardtohnoyoudont@outlook.com>
   Changed at	Mon 03 Aug 2026 09:20:39
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	2a6ed5e29c1b3e29271a3c73fe778a04ddcb5576

   Comments

   tests/checkasm/checkasm: Remove inappropriate headers
   Since the switch to libcheckasm, checkasm no longer uses
   FFmpeg's emms_c, timers, AVLFG or string handling functions,
   so remove these headers.
   This necessitated adding some missing headers (mostly string.h)
   to some files.
   
   Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

   Changed files

   • tests/checkasm/aacpsdsp.c
   • tests/checkasm/aes.c
   • tests/checkasm/af_afir.c
   • tests/checkasm/apv_dsp.c
   • tests/checkasm/cavsdsp.c
   • tests/checkasm/checkasm.h
   • tests/checkasm/crc.c
   • tests/checkasm/diracdsp.c
   • tests/checkasm/float_dsp.c
   • tests/checkasm/lls.c
   • tests/checkasm/mpeg4videodsp.c
   • tests/checkasm/opusdsp.c
   • tests/checkasm/png.c
   • tests/checkasm/qpeldsp.c
   • tests/checkasm/sbcdsp.c
   • tests/checkasm/sbrdsp.c
   • tests/checkasm/vf_nlmeans.c
   • tests/checkasm/vf_pp7.c
   • tests/checkasm/vorbisdsp.c