Builder ffmpeg64-solaris10-i386 Build #14083

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git updating ( 12 secs )
   1. stdio
2. shell  
   1. - no logs -
3. shell_1  
   1. - no logs -
4. shell_2  
   1. - no logs -
5. shell_3  
   1. - no logs -
6. shell_4  
   1. - no logs -
7. shell_5  
   1. - no logs -

Build Properties:

Forced Build Properties:

Responsible Users:

1. Kacper Michajłow

   kasper93ohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #280936

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 07 Sep 2026 02:34:56
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	48c613fbed336a8920a42dda31553d1bdf3cb542

   Comments

   avutil/hwcontext_vulkan: include export handle types in host transfer probe
   Probe with the same handle types the allocator will use, and require
   a memory type that satisfies the property flags alloc_bind_mem()
   requests instead of only checking for a non-empty mask. Also chain
   VkHostImageCopyDevicePerformanceQueryEXT and keep host transfers only
   when the driver reports optimal device access for the image.
   
   The previous probe was not enough, which was exposed by the blocklist
   removal enabling host transfers on NVIDIA. The same issue already
   existed on AMD, just that not many people test that target.
   
   Fixes: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23612#issuecomment-57871
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • libavutil/hwcontext_vulkan.c

2. Change #280937

   Category	ffmpeg
   Changed by	Kacper Michajłow <kasper93ohnoyoudont@gmail.com>
   Changed at	Mon 07 Sep 2026 02:40:53
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	5e95a3ddfbdb68e81bbe58db10c75961566c7c02

   Comments

   avcodec/dovi_rpudec: skip full padding byte if it is already aligned
   On some files when we land already at a byte boundary, there is a full
   padding byte added by the encoder. Skip this byte and also validate
   it's zero as the alignment padding should be.
   
   It is likely just an encoder quirk that adds padding always, and if it
   is aligned, it does full additional byte.
   
   When extremely unlikely situation happens that we cannot infer
   terminator position by looking at the surrounding bytes, calculate crc
   twice, to avoid failing it on padded streams.
   
   Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

   Changed files

   • libavcodec/dovi_rpudec.c