overview / findings / tj/commander.js
Each entry is a real fix from the project's own history. Apply its patch and run the project's own suite, and the tests written in that same upstream commit fall.
| language | tests | green run, s | flaky runs | test files locked |
|---|---|---|---|---|
| node | 1,373 | 5.06 | 0/10 | 123 |
One of the pinned external suites the repair arbiter was run against, as listed on the benchmarks page (fixed values in site/build.py).
6 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix 68199e64b318. the test that catches it was written by the same engineer in the same commit and was never touched.
file lib/command.js · status reported · 2026-08-01
6 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix 672e3806c684. the test that catches it was written by the same engineer in the same commit and was never touched.
file lib/help.js · status reported · 2026-08-01
7 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix f4c7349a78a5. the test that catches it was written by the same engineer in the same commit and was never touched.
file lib/option.js · status reported · 2026-08-01
16 source line(s), 3 test(s) fall, deterministic over three runs. upstream fix 5aaca0d66627. the test that catches it was written by the same engineer in the same commit and was never touched.
file lib/command.js · status reported · 2026-08-01