overview / findings / pallets/jinja
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 |
|---|---|---|---|---|
| python | 911 | 6.67 | 0/10 | 26 |
One of the pinned external suites the repair arbiter was run against, as listed on the benchmarks page (fixed values in site/build.py).
33 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix 065334d1ee5b. the test that catches it was written by the same engineer in the same commit and was never touched.
file src/jinja2/filters.py · status reported · 2026-08-01
7 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix 56a724644b1a. the test that catches it was written by the same engineer in the same commit and was never touched.
file src/jinja2/compiler.py · status reported · 2026-08-01
9 source line(s), 7 test(s) fall, deterministic over three runs. upstream fix 7232b8246200. the test that catches it was written by the same engineer in the same commit and was never touched.
file src/jinja2/utils.py · status reported · 2026-08-01
2 source line(s), 1 test(s) fall, deterministic over three runs. upstream fix d05bd3858c3f. the test that catches it was written by the same engineer in the same commit and was never touched.
file src/jinja2/filters.py · status reported · 2026-08-01
Also found in pallets/jinja: a source module named tests.py sits inside the package.