Skip to content

ci(mutation): exclude the allocating LineSet mutant; twenty shards - #1902

Merged
dekobon merged 2 commits into
mainfrom
fix/issue-1736-wave-4
Nov 13, 2026
Merged

dekobon merged 2 commits into
mainfrom
fix/issue-1736-wave-4

Conversation

@dekobon

@dekobon dekobon commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Fourth, small wave of work on #1736: what the confirming run 43437925608 on main at 3fd38e5d showed. 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

Commit What it does
ci(mutation): exclude a LineSet mutant… The one timeout, 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 shards Shards of 291 took 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 s per mutant). Twenty holds about 261, roughly 213 minutes at the slowest rate seen; the step timeout is 270. The guide now says to size for that rate, not the median

Evidence

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

codecov Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.54%. Comparing base (bcf580d) to head (d42c3c1).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           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     
Flag Coverage Δ
rust 98.53% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dekobon
dekobon merged commit d42c3c1 into main Nov 13, 2026
75 of 76 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant