• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

kubernetes-sigs / inference-perf / 42897495192
87%

Build:
DEFAULT BRANCH: main
Ran 10 Nov 2026 08:53PM UTC
Jobs 1
Files 141
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

10 Nov 2026 08:39PM UTC coverage: 86.263% (-0.006%) from 86.269%
42897495192

push

github

web-flow
Cap each mutant's memory in the mutation ratchet (#1035)

Part of #872

A mutant that removes a loop's exit can allocate until the runner dies,
long before mutmut's own timeout fires. Tests that patch
`load_generator.sleep` with an `AsyncMock` record every await, so each
mutmut worker grows about 200 MB/s. Four of them at once take the 16 GB
runner down with "The runner has received a shutdown signal" and no
summary. The step's `continue-on-error` cannot catch a dead runner, so
the job goes red on every PR that brings `LoadGenerator.run_stage` or
one of those tests into scope: #823, #829, #832, #834, #835, #852, #882,
#941, #946 and #1031.

Now each mutant's pytest run may grow 2 GiB past what it inherits from
mutmut's fork server. Past that it exits with mutmut's timeout code and
counts as caught, the verdict mutmut's own timer would have reached. The
stats run, the clean run and the setup diagnosis stay uncapped.

Changes:
* The `mutation_child_hits` plugin arms a CPU-time timer in
`pytest_configure` when `MUTANT_UNDER_TEST` names a mutant and
`MUTATION_MEMORY_HEADROOM` is set. Every 0.1 s of CPU it reads VmData
and exits 36 past the headroom.
* An RLIMIT_DATA 1 GiB above the headroom backstops processes the tests
fork, which inherit the limit but not the timer.
* `mutmut()` passes `MUTANT_MEMORY_HEADROOM` (2 GiB) to every mutmut
command. Nothing else sets it.
* Tests for a growing mutant exiting 36, a single oversized allocation
hitting the limit, the stats run and an unset headroom staying uncapped,
and only `mutmut()` passing the variable.
* One paragraph on the cap under Wall time in
`docs/mutation_testing.md`.

Other changes:
* `pytest_unconfigure` disarms the timer. Interpreter shutdown restores
SIGPROF's default action, which would kill the process on the next tick.

The limit alone is not enough. A failed allocation at the limit can
abort Python, mutmut records that as suspicious, and the ratchet counts
suspicious as a survivor and reruns it... (continued)

13702 of 15884 relevant lines covered (86.26%)

0.86 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
79.17
-1.04% inference_perf/datagen/base.py
Jobs
ID Job ID Ran Files Coverage
1 42897495192.1 10 Nov 2026 08:53PM UTC 141
86.26
GitHub Action Run
Source Files on build 42897495192
  • Tree
  • List 141
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #42897495192
  • f2a65dda on github
  • Prev Build on main (#42889203792)
  • Next Build on main (#42917842637)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc