Repository navigation
bench(ci): measure what TEST_SELECTION=enforce would have saved over recent CI runs - #258
Merged
Merged
Conversation
…recent CI runs scripts/test-selection-impact.mjs derives, from saved `test-selection` artifacts and the `test (core tiers)` job timings of 28 recent CI runs (2026-11-14 20:43 to 2026-11-16 06:21 UTC), how many runs enforce mode would have reduced and the proportional test-core seconds it would have saved; docs/perf/TEST_SELECTION_ENFORCE_IMPACT.md is generated by it (`--check` verifies the committed report byte for byte) and the compact inputs live in docs/perf/test_selection_inputs/. Result for this window: 0 / 28 runs would have run a subset; all 28 selected `all` (8 full-run requests, 15 a changed file executed by no mapped test - in every case a Node `tests/*.test.mjs` or `tests/*.mjs` file, 5 a bench/example change not attributable to a test). Estimated saving 0.0 / 6669.0 s. Sampling limits are stated in the report: success-preferred sampling (failed and cancelled runs were not sampled), 28 artifacts instead of about 40, and the collection exceeded its gh-call budget (69 vs 45). The report makes no GO/NO-GO decision. The Node test suite is registered in the always-on docs-consistency action; the decomposition digest of that step is updated. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PHPCraftdream
added a commit
that referenced
this pull request
Nov 16, 2026
main gained tests/test_selection_impact.test.mjs (PR #258); the derived classification CSV and report are regenerated with scripts/classify-tests.mjs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Measurement only (no selector, planner or workflow-behaviour change): what the repository variable
TEST_SELECTION=enforcewould have changed over 28 recent CI runs.scripts/test-selection-impact.mjs— cargo-free generator (--report,--check), reuses the timestamp helpers ofscripts/ci-job-durations.mjs, asserts every printed ratio.docs/perf/TEST_SELECTION_ENFORCE_IMPACT.md— generated report;docs/perf/test_selection_inputs/— compact inputs (91 KiB).tests/test_selection_impact.test.mjs— offline fixtures (non-zero savings, unknown reasons, damaged inputs, determinism, tampered report), registered in the always-on docs-consistency action.Result (this window only)
all: 8 full-run requests (CI: full), 15 a changed Node test file (tests/*.test.mjs/tests/*.mjs) "executed by no mapped test", 5 a bench/example change not attributable to a test.Input for plan step P1.5 (selection by the crate graph): the dominant cause in this window is Node test files reaching the Rust selector's unmapped-file rule.
🤖 Generated with Claude Code