Builder ffmpegsos-solaris10-i386 Build #14307

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

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

Steps and Logfiles:

1. git updating ( 7 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. Lynne

   devohnoyoudont@lynne.ee

Timing:

All Changes:

:

1. Change #282269

   Category	ffmpeg
   Changed by	Lynne <devohnoyoudont@lynne.ee>
   Changed at	Sun 20 Sep 2026 04:59:22
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	6705ef6df69bee020de53d17eb1406d77e785623

   Comments

   h264: give frame num gap dummies the duplicated picture's hwaccel state and POCs
   The dummies created for gaps in frame_num duplicate the previous
   reference's frame, but kept their own freshly-allocated
   hwaccel_picture_private and their field POCs at INT_MAX. Hardware
   decoders locate reference pictures through hwaccel_picture_private and
   order them by the field POCs, so predicting from a dummy read
   unrelated or uninitialized memory, and streams with lost frames
   decoded to garbage from the first gap onwards.
   
   Carry the duplicated picture's hwaccel state over to the dummy, which
   also keeps it valid after the duplicated picture leaves the DPB, and
   give the dummy sane field POCs.

   Changed files

   • libavcodec/h264_slice.c

2. Change #282270

   Category	ffmpeg
   Changed by	Lynne <devohnoyoudont@lynne.ee>
   Changed at	Sun 20 Sep 2026 04:59:40
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	2ca26883005ed3bbaff36e7dd535d52ffacd0f27

   Comments

   vulkan_video: fix 4:2:2 chroma subsampling detection
   The 4:2:2 test had the chroma shifts swapped, matching 4:4:0 instead, so
   every 4:2:2 pixel format mapped to VK_VIDEO_CHROMA_SUBSAMPLING_INVALID_KHR
   and produced a video profile with chromaSubsampling set to zero, which is
   not a valid profile to query the device's capabilities with
   (VUID-VkVideoProfileInfoKHR-chromaSubsampling-07013 and -requiredbitmask).

   Changed files

   • libavcodec/vulkan_video.c

3. Change #282271

   Category	ffmpeg
   Changed by	Lynne <devohnoyoudont@lynne.ee>
   Changed at	Sun 20 Sep 2026 04:59:47
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	135be23ab3eda748f81492c3bf16be2589aa71c7

   Comments

   vulkan_decode, vulkan_encode: do not query capabilities for unmappable pixel formats
   A pixel format whose chroma subsampling or bit depth has no video profile
   representation, such as 4:4:0 or 16-bit, ends up as a profile with zeroed
   fields, which is not valid to pass to vkGetPhysicalDeviceVideoCapabilitiesKHR
   (VUID-VkVideoProfileInfoKHR-chromaSubsampling-requiredbitmask and friends).
   Report such formats as unsupported before the query instead, through the
   same path the driver rejecting a format takes.

   Changed files

   • libavcodec/vulkan_decode.c
   • libavcodec/vulkan_encode.c

4. Change #282272

   Category	ffmpeg
   Changed by	Lynne <devohnoyoudont@lynne.ee>
   Changed at	Sun 20 Sep 2026 04:59:51
   Repository	https://git.ffmpeg.org/ffmpeg.git
   Project	ffmpeg
   Branch	master
   Revision	f5b66388088b33c8e994be083d31fc48734d629d

   Comments

   vulkan_decode, vulkan_encode: report codec profiles the device does not support
   VK_ERROR_VIDEO_PROFILE_CODEC_NOT_SUPPORTED_KHR, which drivers return for a
   codec profile they have no notion of, such as H.264 High 4:2:2, fell through
   to a silent generic failure. Report it the way an unsupported operation is.

   Changed files

   • libavcodec/vulkan_decode.c
   • libavcodec/vulkan_encode.c