Repository navigation
Read the newest certified variant from the index in the results-PR tests - #201
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The first automated results PR (#195, 6.7.5) failed 30 tests in this file that named 6.5.0 as the newest certified variant or the last committed one: the end-to-end harness certified a synthetic 6.6.0, now refused as older than 6.7.5; the NEWEST/COMMITTED round trip stripped 6.5.0's lines; the paragraph-placement test expected 6.5.0's closing sentence last. Those tests now read the committed index: NEWEST_ID is qualify.latest_certified, the COMMITTED round trip uses the index's last two ids, the paragraph must sit directly before the subsection's next heading, the synthetic release is one minor version above the newest certified, and the older-version refusal names the live newest version. PE641 and PE650 stay where a test reproduces the hand-built #188 and #190. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MaxGhenis
force-pushed
the
w6/results-pr-tests-live-newest
branch
from
October 21, 2026 18:55
5c10b3f to
00afa36
Compare
Contributor
Author
|
Merged by squash at head
Next: #202 is rebased onto main and retargeted. Then comes the 6.9.0 results rebuild. 🤖 Generated with Claude Code |
This was referenced Oct 21, 2026
This branch was successfully 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.
Read the newest certified variant from the index in the results-PR tests
This PR is stacked on #196; after #196 merges it retargets to main. Its diff is one commit to
tests/test_uk_replay_results_pr.py.The first automated results PR, #195 (policyengine.py 6.7.5), failed 55 tests. #199 fixes the 25 in the discover tests. This PR fixes the 30 in this file, minus the matrix-edit round trip that #196 removes. Every one named 6.5.0 as the newest certified variant, or as the last committed one. None of them had anything to do with 6.7.5's results.
VERSIONis one minor version above the newest certifiedNEWEST/COMMITTEDround tripqualify.latest_certifiedand the index's last two idsCOMMITTEDcheck"pe6.5.0…",then the new idPE641andPE650stay where a test reproduces the hand-built #188 and #190, or uses 6.5.0's committed record as a template.Verified
Fleet ops' disk pause #9 rules out local test runs, so CI is the evidence:
After #196, #199 and this PR merge, #195 is closed and its branch deleted, and the results workflow is re-dispatched for its request. A force-push rebuild would have to change
ci.ymlrelative to #195's old tip, and the bot's token no longer holdsworkflows. The bot then opens a fresh 6.7.5 PR, which lands on the normal gates.axiom: n/a: test fixtures only; no policy encoding.
🤖 Generated with Claude Code