Files
werkator/docs/prs/2026-10-11-PR#151-restart-split.md
claude-code 5ae89f63b0
werkator build succeeded after 03:42
werkator/deploy build succeeded after 00:09
Restart at the newest commit as a step of its own, Mutation-CRAP gate holds again (v1.41.2) (#151)
Co-authored-by: claude-code <claude-code@javagil.de>
2026-10-11 07:08:12 +02:00

33 lines
1.4 KiB
Markdown

> **WARNING:** This document describes only the change applied in this PR.
> It may already be outdated once the next PR is merged.
> Historic PR-documentation is not maintained along with new PRs — treat it as a snapshot, not as current documentation.
## Problem
The nightly mutation build of 2026-10-11 failed its Mutation-CRAP gate on `main` (d95b7e6, the merge of PR#150).
`BuildsApiController.restart` scores 15.64; the limit is 15.
It stood at 14.07 before; PR#150 added the refusal of the newest commit to it.
## Non-Goals
- No change of behaviour; the existing scenarios of PR#150 stay.
## Solution
- `restartAtNewestCommit` takes the newest-commit branch of `restart`: the refusal and the origin head.
`restart` keeps the token check and the repetition of the latest recorded commit.
- Measured locally with PIT on `BuildsApiController`, `BuildRestarts` and `RestartPolicy`:
| Method | Mutation-CRAP |
|---------------------------------------------|---------------|
| `BuildsApiController.restart` | 8 (was 15.64) |
| `BuildsApiController.restartAtNewestCommit` | 3 |
| `BuildRestarts.newestCommitRefusal` | 5 |
The highest score of the three classes is the unchanged `BuildsApiController.current`, 13.70.
## Additional Changes
- The plan notes the split under `#restart2`.
- Version 1.41.2 with its release note.