bootstrap from 2026.9.24.1, and the verification that read the right file - #689
Open
Sunrisepeak wants to merge 1 commit into
Open
Sunrisepeak wants to merge 1 commit into
Sunrisepeak wants to merge 1 commit into
Conversation
…file 2026.9.24.1 is released, mirrored to GitCode by the local top-up as each archive appeared (8/8 byte-identical with the GitHub release), and indexed (openxlings/xim-pkgindex#871, latest on all three platform tables, pointer at 4440c50). The sandbox verification script's section E searched target/ for compile_commands.json, which mcpp writes at the project root, so it failed on both releases and the old release's failure was read as the expected one. It now reads the file after each configure and checks the fingerprint by the number of build directories. With it, the SubOS sandbox with CN mirrors reads fails=0 on 2026.9.24.1 and fails=6 on 2026.9.21.3, the six CHANGE assertions, every GUARD passing on both. The plan and the analysis move to landed; the design stays active for the payload-contract clauses scheduled with the next LLVM batch.
This branch has not been deployed
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
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.
Summary
.xlings.json: the bootstrap pin moves to 2026.9.24.1, which is released, mirrored and indexed:.sha256uploaded to GitCode by the local gtc as it appeared, GET 200 at the upstream size, and 8/8 byte-identical with the GitHub release; every archive matches its sidecar;latestis exactly three lines naming 2026.9.24.1, and the index pointer'sindex_versionis 4440c50. A SubOS sandbox with the CN mirror resolveslatest -> 2026.9.24.1on its firstxlings update.compile_commands.jsonfromtarget/, where mcpp does not write it, so it failed on both releases and the old release's failure was read as the expected one. It now reads the project-root file after each configure and checks the fingerprint by the number of build directories.Sandbox readings (SubOS
v924,--sandbox, CN mirrors for xlings and mcpp)macos_deployment_targetfrom Linux: triple, env override, fingerprintfoo:refused;xim:msvc@systemrefused as a spelling<mutex>, index recipe fix,xim:gcc@16.1.0, mcpp-index consumers (yaml-cpp on gcc 16 and 15, CLI11, fmt on gcc and llvm)The MSVC toolset selection is Windows-only and is covered by e2e 760 (Visual Studio 2026, MSVC 14.51.36231) and 239 on #688's CI.