Repository navigation
perf(CI-04): reuse validated CPython corpus references - #750
Merged
Merged
Conversation
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.
Class-corpus checks previously reran every CPython subprocess for every profile and drain/step/parked mode. Successful reference reports now share a content-addressed disk cache; Python build, host, complete corpus and reference drivers identify each entry. Damaged or failed entries are recomputed, and standalone reference checks remain fresh.
CI restores per-shard caches across PR updates without changing the regression matrix or deadlines.
Validation: 13 runner/reference tests; 11 Node source matrices (classes and native/mutable/immutable subclasses). The 1,741-case exceptions oracle took 51.148s cold and 0.005s cached locally on CPython 3.14.7/macOS arm64; this measures oracle reuse only.
Closes #746.