25 Commits

Author SHA1 Message Date
lilleman 089e9b683b Add task-bench, which has Haiku fix planted bugs at a base and a head and prints what each side took
CI / tests (pull_request) Failing after 4m9s
2026-11-21 01:05:50 +01:00
lilleman a8933b9ab3 Sort test_mutate_changes.py's imports by their first binding
CI / tests (pull_request) Successful in 3m54s
2026-11-21 00:42:27 +01:00
lilleman e25dd3c531 Answer stability round 2: 1 🔴, 0 🟡 (0 misread); pin diff.interHunkContext too
CI / tests (pull_request) Failing after 4m18s
2026-11-21 00:19:24 +01:00
lilleman 846d6c6e36 Answer stability round 1: 1 🔴, 2 🟡 (0 misread); pin the git diff settings Gremlins parses, show the mutant total, and a container prefix that runs as root 2026-11-21 00:02:27 +01:00
lilleman e3cc18f04e Test the git settings Gremlins' environment gets
CI / tests (pull_request) Failing after 4m8s
2026-11-20 23:38:39 +01:00
lilleman a430bca9f9 Mutate the Go lines a branch changes with Gremlins in mutate-changes
CI / tests (pull_request) Successful in 3m54s
2026-11-20 23:24:21 +01:00
Lilleman ce0344f703 Answer stability round 1: 0 🔴, 2 🟡 (0 misread); tell mutmut's own frames by their site-packages path, take the error from after the last frame, and fix the module docstring and help 2026-11-20 21:26:22 +01:00
Lilleman 9bd385d9cd Kill the surviving mutants of the file-name import move and the mutmut crash line 2026-11-20 20:04:03 +01:00
Lilleman 91cf86e0cd Run mutate-changes on a script its tests import by file name, and name a crash inside mutmut in one line 2026-11-20 19:12:10 +01:00
lilleman cb3135bc8c Answer principles round 1: 1 🔴, 7 🟡 (0 misread); every effect is handed in as an argument, no test patches a global, and the traces principle scopes tools that run on their user's machine
CI / tests (pull_request) Successful in 3m43s
2026-11-19 12:42:03 +01:00
lilleman 414ecfa2a0 Answer stability round 1: 0 🔴, 2 🟡 (0 misread); name the changelog as the repo spells it, test facts not sentences 2026-11-19 02:57:24 +01:00
lilleman b845d80ac7 Tell an epic chunk's worker how its repo ships a change, and bound the interrupt test's helper shell
CI / tests (pull_request) Failing after 5m1s
2026-11-19 02:17:33 +01:00
lilleman cd2ac5d727 Answer stability round 2: 1 🔴, 2 🟡 (0 misread); run Stryker as @stryker-mutator/core, pass an interrupted tool SIGINT before the kill, test SIGHUP, and print a failed Stryker or Infection run's whole report
CI / tests (pull_request) Successful in 2m24s
2026-11-11 21:59:52 +01:00
lilleman 563e8cdc3c Answer product-owner round 2: 0 🔴, 1 🟡 (0 misread); run Stryker only where a package.json is above a file, and name the files with none in a Not mutated line 2026-11-11 21:50:16 +01:00
lilleman f70bed52fe Kill mutate-changes' surviving mutants: test a deleted file, a mutmut results that cannot start, an interrupt's speed, and a process group already gone 2026-11-11 21:27:53 +01:00
lilleman 581c8721a0 Answer stability round 1: 3 🔴, 5 🟡 (0 misread); run only a Stryker the project installed, tell mutmut's setup fault from no test, pin cargo-mutants' diff prefixes, keep -x, end the tool and report its scratch folder on SIGTERM, and test option-like names; with product-owner's and prose's code fixes 2026-11-11 21:12:08 +01:00
lilleman 63369d5944 Drop mutate-changes' --no-renames, which a diff limited to the changed paths makes moot, and test the reason each of its failures gives
CI / tests (pull_request) Successful in 2m25s
2026-11-11 20:31:28 +01:00
lilleman 11804ac6aa Parse each mutants/ copy once when reporting mutmut's mutants, and kill more survivors with tests of by_folder, the in-diff tools' folder and their start failures 2026-11-11 20:19:02 +01:00
lilleman 4c9bc080bb Kill mutate-changes' surviving mutants with tests of its other tools, its git config, its output and the files it copies, and move its runs to their own test file 2026-11-11 20:01:42 +01:00
lilleman 38c64c9f12 Say in mutate-changes --help that mutmut counts only the code a test runs in its own process 2026-11-11 19:40:13 +01:00
lilleman aa777819e8 Run mutate-changes in-process in its tests, so mutmut sees the code they reach, and kill the mutants of mutmut_setup and mutmut_mutants that change behaviour 2026-11-11 19:39:40 +01:00
lilleman 42a637d718 Leave out the test of each failing subtest, which pytest 9.2 reports only as SUBFAILED<description> <test> 2026-11-11 19:22:10 +01:00
lilleman 79e8ce1368 Have mutmut copy each entry of the folder rather than '.', which copied mutants/ into itself and collected the tests twice 2026-11-11 19:14:49 +01:00
lilleman e99eef43b9 Leave out a failing test file by its absolute path, since pytest 9.2 under mutmut 3.8.1 reports nodeids as mutants/<path> 2026-11-11 19:04:24 +01:00
lilleman a52ebb94bf Run mutation tests on a chunk's changed lines before review with bin/mutate-changes, and hand stability-reviewer the survivors
CI / tests (pull_request) Successful in 2m14s
2026-11-11 18:58:31 +01:00