Repository navigation
ci(mutation): exclude the allocating LineSet mutant; twenty shards - #1902
Merged
Merged
Conversation
Run 43437925608 on `main` at 3fd38e5 judged one mutant a timeout: `replace + with * in LineSet::last_word`. With `*` a set's last word is its offset times its length, `union_with` reserves that far, and every merge up a space tree multiplies the span again. The suite notices, with 551 failed tests in that log, but a nested fixture then asks for 168 GB and the test binary stalls past the timeout before it reports. Run 43278927651 judged the same mutant caught, so the verdict depends on the runner. The header's third kind now reads "non-terminating, or allocating without bound, under mutation". The configured list differs from the unconfigured one by exactly forty-seven mutants. Refs #1736
Run 43437925608 put eighteen shards of 291 mutants through in 108 to 237 minutes. The two slowest held no escape and no timeout, so the 2.2x spread is between runners doing the same work: 22 to 49 seconds per mutant. Two shards passed the 200 minutes the guide gives as the point to raise the count, and 237 leaves little under the 270-minute step timeout. Twenty holds about 261 of the list's 5227 mutants, roughly 213 minutes at the slowest rate seen. The guide now says to size for that rate and not the median. `make actionlint`, `make mutation-workflow-test` and `make mutation-report-test` pass. Refs #1736
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1902 +/- ##
=======================================
Coverage 98.53% 98.54%
=======================================
Files 405 405
Lines 125777 125777
Branches 125342 125342
=======================================
+ Hits 123933 123942 +9
+ Misses 1120 1112 -8
+ Partials 724 723 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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.
Fourth, small wave of work on #1736: what the confirming run 43437925608 on
mainat3fd38e5dshowed. Config, workflow and guide only.Refs #1736. This does not close it: 8 mutants wait on #1885, #1886, #1887, #1889 and #1890.
The run
18 of 18 shards complete: 4935 caught, 8 missed, 1 timed out, 284 unviable. The 8 missed are exactly the 8 blocked on those five bugs; nothing else escaped.
Commits
ci(mutation): exclude a LineSet mutant…replace + with * in LineSet::last_word. It is noticed (551 tests fail in that log), but every merge up the space tree multiplies the set's span, a nested fixture asks for 168 GB, and the test binary stalls past the timeout before it reports. Run 43278927651 judged the same mutant caught, so the verdict depends on the runner. The header's third kind now reads "non-terminating, or allocating without bound, under mutation"ci(mutation): split the run across twenty shardsEvidence
bcf580d0(perf(abc): fix the two quadratic costs the #1868 ancestor-climb audit found #1901).cargo mutants --list --no-config -e '**/*_tests.rs'againstcargo mutants --listover the workflow's selection differs by exactly 47 mutants: this one and the 46 onmain.--in-diff: 19 caught, 3 unviable, none missed.taplo fmt --check,make actionlint,make mutation-workflow-test,make mutation-report-testandmake markdown-lintpass. The fullmake pre-commitwas not run for this wave: no Rust changed.make bench-scaling, owed for the refactors in test: kill the second wave of escaped mutants; exclude the equivalent ones #1895 and refactor(checker): remove five unused is_non_arg overrides; exclude the decided mutants #1899, now passes on this base: all 137 probes within their bound, at a host load average of about 7.