Finish item 474 in the plan
CI / tests (pull_request) Successful in 5m27s

This commit was merged in pull request #674.
This commit is contained in:
Lilleman
2026-11-20 21:26:47 +01:00
parent 73183957ae
commit 64e33ae209
2 changed files with 2 additions and 22 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- `mutate-changes` mutates a Python script from its own folder where a test beside it imports it by its file name, as in `import run_harness`, so mutmut finds the tests' calls to it. A crash inside mutmut now becomes one report line that names mutmut's error, not a traceback, and the other folders still report.
- do-epic starts an issue in Jira as its chunk starts: it assigns the issue to the account it works as, unless someone else holds it, and the new settings `jira-start-transition` and `jira-sprint-board` in its `config.toml` move the issue and add it to a board's active sprint.
- Load no MCP server in the bench's headless `claude -p` judge and in the reviewer-merge trials' new-findings call either, so text an outsider wrote cannot reach one. A new check fails any Python file that passes `--tools` more often than `--strict-mcp-config`.
- Load no MCP server in the six headless `claude -p` calls that deny the model tools, so text an outsider wrote cannot reach one.
+1 -22
View File
@@ -12,9 +12,8 @@
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 474 | 0.15.0 | | | **Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.** | 2 | 2 | 3 | 5 | 3 | 1.1 by 4 | 1.5 |
| 472 | 0.15.0 | | owner | **Let a project's config name a working branch per epic, such as `TW-12345`, that chunks branch off, merge into and keep level with `main`, so a person merges the finished epic into `main` in one pull request.** | 4 | 2 | 3 | 7 | 7 | 1.5 by 6, 1.6 by 7 | 1.1 |
| 467 | 0.15.0 | 472, 474 | question | **Cut 0.15.0 as soon as every other item in it has merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 467 | 0.15.0 | 472 | question | **Cut 0.15.0 as soon as every other item in it has merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 469 | 0.15.1 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
| 446 | 0.16.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
| 462 | 0.16.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
@@ -77,26 +76,6 @@
## Details
### 474. Run `mutate-changes` in a repo whose tests import a script by its file name, such as Timewave's `docs-and-tools`, and name a crash inside mutmut in one line.
Found on 2026-11-20 while shipping TW-13648 in Timewave's `docs-and-tools`: `mutate-changes` failed twice there, so its worker mutated 18 changed lines by hand instead. The first run failed on a module path: the tests in `docker/scripts/` import the script under test as a top-level module (`import run_harness`), which mutmut's copy of the tree doesn't resolve as the tests expect. The second run crashed inside mutmut, with a `KeyError` in its worker pool.
- Find why each run failed, from a run against `docs-and-tools` at the commit TW-13648 merged.
- Where the module path is the cause, make `mutate-changes` run tests that import a script by its file name, as `docs-and-tools` does, the way they run outside mutmut.
- Where mutmut itself crashes, catch that crash and say so in one line naming mutmut and the error, so the worker knows to mutate by hand, instead of a traceback.
- Item 462 covers tests that fail in mutmut's copy of claude-config itself; check whether one fix serves both.
Release: lilleman moved it to 0.15.0 on 2026-11-20, ahead of epic TW-13503, which changes `docs-and-tools` in six sub-tasks. mutmut costs no tokens and tries every mutation it knows on each changed line; a worker that mutates by hand pays tokens for each edit, test run and revert, and tried only 18 mutants on TW-13648.
Touches:
- `bin/mutate_changes/mutmut_tool.py`: `mutate_folder`, `read_folder`, `project_setup`, `copy_files`, `mutate_copy`, `configured_run`
- `bin/mutate_changes/mutmut_setup.py`: `mutmut_config`
- `bin/mutate_changes/mutmut_mutants.py`: `module`, `mutant_globs` (small)
- `bin/mutate_changes/tool_process.py`: `failed` (small)
- `bin/mutate_changes/test_mutate_changes.py`
- `bin/mutate_changes/test_mutate_changes_runs.py`
### 472. Let a project's config name a working branch per epic, such as `TW-12345`, that chunks branch off, merge into and keep level with `main`, so a person merges the finished epic into `main` in one pull request.
Today every chunk branches off the default branch and its pull request merges into it. A team whose rules keep merges into `main` with a person, such as Timewave's, then sets `merge = "human"`, and the loop stops at every chunk until someone merges. lilleman asked on 2026-11-20 for a working branch per epic instead: agents merge each chunk into a branch named as the epic, such as `TW-12345`, and when the whole epic is done and reviewed, a person merges that branch into `main` in one pull request.