A timed-out mutant counts as killed by default, as in PIT's own mutation score; strict-v1 stays unchanged and selectable (werkcrappit { scorePolicy = "strict-v1" } / werkcrappit.scorePolicy). MEMORY_ERROR and RUN_ERROR stay inconclusive.
Why: mutants that turn a loop endless cannot be avoided; under strict-v1 every real project has methods without score and a strict gate that never passes. The hsadmin-ng probe run had 4 such methods.
Deviation from the specification's starting default documented in ADR 0006; every report names its policy.
A timed-out mutant counts as killed by default, as in PIT's own mutation score; `strict-v1` stays unchanged and selectable (`werkcrappit { scorePolicy = "strict-v1" }` / `werkcrappit.scorePolicy`). MEMORY_ERROR and RUN_ERROR stay inconclusive.
Why: mutants that turn a loop endless cannot be avoided; under strict-v1 every real project has methods without score and a strict gate that never passes. The hsadmin-ng probe run had 4 such methods.
Deviation from the specification's starting default documented in ADR 0006; every report names its policy.
CI on werkator.javagil.de: green (81 s).
PR-doc: `docs/prs/2026-10-01-PR#9-timeouts-killed-policy.md`
🤖 Generated with [Claude Code](https://claude.com/claude-code)
A timed-out mutant counts as killed, as in PIT's own mutation score;
strict-v1 stays unchanged and selectable through werkcrappit.scorePolicy
or the Gradle extension's scorePolicy. Under strict-v1 every real project
has methods without score and a strict gate that never passes, since
mutants that turn a loop endless cannot be avoided (ADR 0006).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mi
merged commit cb24f0fb01 into main2026-10-01 19:11:24 +02:00
mi
deleted branch timeouts-killed-policy2026-10-01 19:11:24 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A timed-out mutant counts as killed by default, as in PIT's own mutation score;
strict-v1stays unchanged and selectable (werkcrappit { scorePolicy = "strict-v1" }/werkcrappit.scorePolicy). MEMORY_ERROR and RUN_ERROR stay inconclusive.Why: mutants that turn a loop endless cannot be avoided; under strict-v1 every real project has methods without score and a strict gate that never passes. The hsadmin-ng probe run had 4 such methods.
Deviation from the specification's starting default documented in ADR 0006; every report names its policy.
CI on werkator.javagil.de: green (81 s).
PR-doc:
docs/prs/2026-10-01-PR#9-timeouts-killed-policy.md🤖 Generated with Claude Code