Builder ffmpegsos-solaris10-sparc Build #14015

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 ( 17 secs )
   1. stdio
2. shell 'gsed -i ...' ( 0 secs )
   1. stdio
3. shell_1 'gsed -i ...' ( 1 secs )
   1. stdio
4. shell_2 'gsed -i ...' failed ( 0 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 8 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 ( 1 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Martin Storsjö

   martinohnoyoudont@martin.st

Timing:

All Changes:

:

1. Change #281867

   Category	ffmpeg
   Changed by	Martin Storsjö <martinohnoyoudont@martin.st>
   Changed at	Tue 15 Sep 2026 12:10:54
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	aa63c63b85a6411b8351726abe9f5b612e96ef46

   Comments

   checkasm: aarch64: Test PMULL and CRC separately
   We have three different SIMD implementations of crc_32_IEEE_LE;
   one that uses CRC, one that uses PMULL+EOR3, and one that uses
   PMULL+EOR3+CRC.
   
   When we normally add more CPU flags progressively, we'd first
   test the CRC version, then the PMULL+EOR3+CRC version, but the
   PMULL+EOR3 version would end up untested, unless the machine
   lacks the CRC feature.
   
   Use the new checkasm cpu flag masking feature, added in
   ffmpeg's checkasm in b59a4375acf0176efaf0152117e87c15d1e2aa90,
   to allow testing these features separately.
   
   In addition to making sure we actually test all codepaths,
   this also makes it easier to benchmark all three variants.

   Changed files

   • tests/checkasm/checkasm.c