Repository navigation
ci: test only the specs a change can affect -- t27c use-edges feeds specs/ci/affected.t27 (Closes #7565) - #7566
Merged
Merged
Conversation
…pecs/ci/affected.t27 (Closes #7565) specs/ci/affected.t27 (#7529) had no producer and no consumer. Now: - `t27c use-edges` prints every `use` edge as "importer<TAB>imported" from use_resolve::use_targets, the resolver t27c compiles with -- no second resolver. 946 edges over 1575 specs in 28 ms on the lab. - spec-guards feeds the diff, the base+head edge union and the corpus into gen/c/ci/affected.c, then runs `t27c test-report` on the selected specs only, in both trees with the same t27c: red if a spec fails more tests than on the base or stops building. RUN_ALL leaves the corpus to corpus-ratchet. Measured on the lab: a change to specs/policy/text_lines.t27 selects 3 of 1575 specs (~1 s of tests vs ~10 min for the corpus at ~0.4 s/spec); the negative control (an added `assert 1 == 2`) goes red, 1 failing vs 0. Fan-in is the long tail: base/types.t27 selects 412, math/constants.t27 277. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gHashTag
added
the
owner-approved-foreign
gHashTag
enabled auto-merge (squash)
October 7, 2026 15:33
…b compiles it too (Refs #7565) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 7, 2026
…n: step (Refs #7565) shell: run: steps 302 -> 303. quiet: one more step in a quiet shape (gated on a file existing, a variable in the path) and one more that names a path. Written by `tri census pin --bless` on the lab. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 7, 2026
Merged
Contributor
Contributor
PR DashboardGenerated at: 2026-10-07 17:02:37 UTC
Summary
Seal Status
|
This was referenced Oct 7, 2026
Owner
Author
|
Merge shepherd: own-language was red only because of the stale base.sha trap (#7489). The PR's base.sha was 2749341, so the gate counted master's own foreign changes since then, such as |
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
2 participants
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.
Closes #7565
What
t27c use-edges [--specs-dir specs]: everyuseedge asimporter<TAB>imported, sorted, repo-relative, fromuse_resolve::use_targets, the resolver t27c compiles with. There is no second resolver.git diff --name-status, the union of base and head edges, and the head corpus intogen/c/ci/affected.c(selection logic stays inspecs/ci/affected.t27). It then runst27c test-reporton the selected specs only, in both trees with the same t27c.Measured (Railway lab)
use-edgespolicy/text_lines.t27base/types.t27(worst fan-in)test-reportper specassert 1 == 2added)Foreign lines: 57 of 80 (main.rs 7, use_resolve.rs 21, spec-guards.yml 29). All three files are listed in
tools/policy/foreign-exceptions.txt.Not in this PR: gating corpus-ratchet off for selective PRs. corpus-ratchet.yml is not on the exception list, so that is the owner's call.
🤖 Generated with Claude Code