The pin had drifted from the SDK installed on the dev machine again: - #140
Merged
Conversation
vulkan-headers/vulkan-loader 1.4.350.1 against an SDK at 1.4.357. That gap is the mixed-vulkan-hpp trap documented in CLAUDE.md — two header versions in one binary, aborting on the first RAII call with no bad line of C++ behind it — kept out of reach only by the include-order guard. Aligning the pin to 1.4.357.0 removes the gap itself. Taken in the gap between items and BEFORE arc 2's static-scene CSM caching rather than after it: that item is justified by measured shadow-pass time, and a loader/ICD move underneath its before/after numbers would make them unattributable. What moved: vulkan-headers + vulkan-loader 1.4.350.1 -> 1.4.357.0, spirv-tools/spirv-headers likewise, glslang 16.4.0, glfw3 3.4 -> 3.5.1, imgui 1.92.8 port-version 1. shaderc, ktx, fastgltf, catch2 and VMA are unchanged. CI PROVISIONING, WHICH THE BUMP BROKE WITH NO SOURCE CHANGE glfw3 3.5.1 pulls `pthread-stubs` on Linux, and vcpkg builds that port with `vcpkg_make` rather than CMake: it refuses to configure without autoconf, autoconf-archive, automake and libtool. The Docker image did not have them, so the Linux leg failed with BUILD_FAILED — reproducibly, which is what separated it from the ftpmirror.gnu.org 502 that appeared in the same run's output (that download succeeded on the ftp.gnu.org fallback and was not the cause). The four packages are added to tools/ci/Dockerfile AND to both Linux jobs of .github/workflows/ci.yml, because autoconf-archive is not preinstalled on ubuntu-latest either — the hosted runner would have failed the same way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
vulkan-headers/vulkan-loader 1.4.350.1 against an SDK at 1.4.357. That gap is the mixed-vulkan-hpp trap documented in CLAUDE.md — two header versions in one binary, aborting on the first RAII call with no bad line of C++ behind it — kept out of reach only by the include-order guard. Aligning the pin to 1.4.357.0 removes the gap itself.
Taken in the gap between items and BEFORE arc 2's static-scene CSM caching rather than after it: that item is justified by measured shadow-pass time, and a loader/ICD move underneath its before/after numbers would make them unattributable.
What moved: vulkan-headers + vulkan-loader 1.4.350.1 -> 1.4.357.0, spirv-tools/spirv-headers likewise, glslang 16.4.0, glfw3 3.4 -> 3.5.1, imgui 1.92.8 port-version 1. shaderc, ktx, fastgltf, catch2 and VMA are unchanged.
CI PROVISIONING, WHICH THE BUMP BROKE WITH NO SOURCE CHANGE
glfw3 3.5.1 pulls
pthread-stubson Linux, and vcpkg builds that port withvcpkg_makerather than CMake: it refuses to configure without autoconf, autoconf-archive, automake and libtool. The Docker image did not have them, so the Linux leg failed with BUILD_FAILED — reproducibly, which is what separated it from the ftpmirror.gnu.org 502 that appeared in the same run's output (that download succeeded on the ftp.gnu.org fallback and was not the cause).The four packages are added to tools/ci/Dockerfile AND to both Linux jobs of .github/workflows/ci.yml, because autoconf-archive is not preinstalled on ubuntu-latest either — the hosted runner would have failed the same way.