Repository navigation
Mutation run: a shard's baseline is its share of what every mutant names, and the whole suite runs in dealt parts (record 0093) - #412
Conversation
…mes, and the whole suite runs in dealt parts (record 0093) Each shard's baseline is each count-th of the tests every mutant names, method by method, so across the shards each runs once: 141 a shard of 1,128, where each ran 834 to 903. A red test fails the shard that holds it. A tree that cannot be read runs the shard's own names, as before. A whole-suite run is dealt into parts of at most PART_MOST, 100, tests, each one run held to the 600 s, the next only when the last passed, so no run grows with the suite (issue 398). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…t parts, and the row stays under 260 characters Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ld, and a name that cannot be read is run in every shard and alone The Claude review and Muse: the front door's share and PART_MOST's value had no test or mutant; main() is now reached through front(), which a test drives with a shard and a filter, and PART_MOST is asserted. The Claude review, Muse and the security pass: a shard that could not read a name fell back to its own names, which could leave a test in no share; any name that cannot be read method by method now runs every name in each shard. In the whole suite, a module that cannot be read is a part of its own. Record 0093 says so, and what bounds a run of parts; tools/AGENTS.md's row says the suite runs in parts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…s module runs whole, and the row names its test Muse: a load_tests doctest's id is no test unittest runs by name; a name whose tests are not all methods of a TestCase by their own ids is now kept whole. The Claude review: a module that holds no test made a part of its own, which 3.12 exits 5 for; it now runs nothing. tools/AGENTS.md's row names the test of the dealt parts, and record 0093 says a red test fails the other shards as FLAKY. A test a module under tests/ takes from elsewhere is kept whole, so the check of an id under tests/ keeps its mutant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|



Closes #398. Record 0093, which extends 0083 without editing it. Synced with main after 0092 (#408) landed, so the records' gap check passes.
Why. #399 (record 0083) made each shard's baseline the tests its own mutants name, dealt among four workers, and accepted two gaps. Mutants name whole classes, and the shards share them, so each shard still named about 840 to 910 of the 1,128 named tests, and its baseline grew nearly as the suite does. A mutant whose named tests pass still ran the whole suite as one run held to 600 s, which took 523 s on a desk.
What changes (
tools/mutants.py, its tests,tools/AGENTS.md's row and record 0093; the workflow is unchanged)count-th from the shard's place. Across the shards each named test runs once. With eight shards each runs 141, where it ran about 840 to 910, and a share shrinks as shards are added. A share may hold none, and then nothing runs.selectedgives the share as a fourth value. The front door is nowfront(), which hands it tomain, so a test can drive it.PART_MOST, 100, each. Each part keeps the suite's order, the slow modules last.confirm's runs are unchanged: one test, or one class where its setup failed.PART_MOSTis held at 100 by a test.tests.test_tools.Trialsholds tests of 97, 72 and 31 s side by side. On a loaded desk (940 s for the suite), consecutive parts of 250 reached 420 s and of 50 still 306 s. Dealt parts of 100 made 14 parts of 9 to 124 s.Measured. The whole suite on this desk, unbroken, in its 14 dealt parts of 93 or 94 tests: every part passed, the parts took 43 to 51 s each where measured. The shares: 141 tests in each of 8 shards.
Checks (on ed97cad, after the sync and the fix round below)
make verify: every check passes, and 1,332 tests run OK.python3 -m tools.mutants: 3,224 of 3,225 killed at this desk. The one left, "a signal leaves the reader's token live" (tools/trial_reader_reads.sh), survives on main too at this desk, whose/bin/shis macOS's; it is not this change's, and CI's shards are the gate.Reviews after the sync, structured (
review-findings/1, parsed byreview_parse.py; head 820e8ce)820e8ce820e8ce820e8ce820e8cetools/mutants.py:9428tools/AGENTS.md:35tools/mutants.py:9431docs/decisions/0093-a-mutant-shards-baseline-is-its-share-of-what-every-mutant-names-and-the-whole-suite-runs-in-dealt-parts.md:10Reviews before the sync
config/rubric-pr-review.json): 2 majors, 2 minors, 3 nits; all fixed.share=sharehad no test or mutant. Nowfront(), driven by a test with a shard and with a filter, which also holdsworkers=at_once, a gap from before.PART_MOST = 100. A test asserts it, and a mutant breaks it.tools/AGENTS.md's row said the slow modules run last, which holds within each part.readheld while a name fell back to whole, so shards could part; read now needs every name read method by method. 0093 says the shares agree only where every shard lists the same tests, and thatmake verify's whole suite still runs a test no share holds.tools/AGENTS.mdrow over 260 characters (fixed in b0eb541), and the samePART_MOST, front-door and fallback findings as above.🤖 Generated with Claude Code