Builder ffmpeg-solaris10-sparc Build #12263

Results:

Failed shell_2 shell_3 shell_4 shell_5

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-ffmpeg-solaris10-sparc' triggered this build

Steps and Logfiles:

1. git update ( 8 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 ( 8 secs )
   1. stdio
   2. config.log
6. shell_4 'gmake fate-rsync' failed ( 1 secs )
   1. stdio
7. shell_5 '../../../ffmpeg/fate.sh ../../../ffmpeg/fate_config.sh' failed ( 0 secs )
   1. stdio
   2. configure.log
   3. compile.log
   4. test.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Niklas Haas

   gitohnoyoudont@haasn.dev

Timing:

All Changes:

:

1. Change #239811

   Category	ffmpeg
   Changed by	Niklas Haas <gitohnoyoudont@haasn.dev>
   Changed at	Tue 15 Jul 2025 12:46:11
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	053a113ad8f853c398c0e268408bfdc280b23f11

   Comments

   avutil/hwcontext_vulkan: don't over-map buffers with prior padding
   If the image data is not at the start of the buffer allocation, such as
   when the buffer has padding before the image data, this function maps too
   much memory, since src_data + src_buf->size exceeds the buffer size.
   
   Fix this by subtracting the difference between the buffer start and the
   provided image data pointer from the size of the memory range to map.
   
   An easy way to reproduce this issue is using the vf_pad filter, which
   allocates image data buffers with a nonzero offset whenever padding is
   requested before the start of the image data.

   Changed files

   • libavutil/vulkan.c