overview / findings / lodash/lodash
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 | 7,158 | 19.24 | 0/10 | 6 |
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 1f8ea0774696. the test that catches it was written by the same engineer in the same commit and was never touched.
file lodash.js · status reported · 2026-08-01
18 source line(s), 2 test(s) fall, deterministic over three runs. upstream fix 0cec225778d4. the test that catches it was written by the same engineer in the same commit and was never touched.
file lodash.js · status reported · 2026-08-01
15 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix 659e8c019cca. the test that catches it was written by the same engineer in the same commit and was never touched.
file lodash.js · status reported · 2026-08-01
4 source line(s), 10 test(s) fall, deterministic over three runs. upstream fix c84fe82760fb. the test that catches it was written by the same engineer in the same commit and was never touched.
file lodash.js · status reported · 2026-08-01