Builder ffmpegsos-solaris10-i386 Build #13608

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git update ( 7 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 ( 1 secs )
   1. stdio
5. shell_3 './configure --samples="../../../ffmpeg/fate-suite" ...' failed ( 11 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 2 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config_sos.sh' failed ( 2 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Zhao Zhili

   zhilizhaoohnoyoudont@tencent.com

Timing:

All Changes:

:

1. Change #262261

   Category	ffmpeg
   Changed by	Zhao Zhili <zhilizhaoohnoyoudont@tencent.com>
   Changed at	Wed 25 Mar 2026 05:14:23
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	3cfbf56192fb3dcabc0951dad2664b84479b3de1

   Comments

   doc/developer: allow whitespace changes mixed with functional changes
   The cosmetic-changes policy in developer.texi was written during the SVN
   era, when reviewing indentation changes mixed with functional changes
   was genuinely difficult.
   
   Since FFmpeg has moved to Git, reviewers now have simple built-in tools
   to ignore whitespace changes:
   
     git diff -w
     git log -p --ignore-all-space
   
   Forgejo's pull request UI also offers a 'Hide whitespace changes'
   toggle, making it trivial to focus on the functional diff.
   
   For those who prefer reviewing patches in their mail client, the same
   result can be achieved by saving the patch and running:
   
     git apply --ignore-whitespace <patch> && git diff -w
   
   Relax the policy so that indentation changes which are invisible to
   git diff --ignore-all-space may accompany functional changes, while
   still requiring non-whitespace cosmetic changes to be in separate
   commits.
   
   Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>

   Changed files

   • doc/developer.texi