Google 论文介绍部署在内部 CI 中的 FlowAgent,它捕获测试失败后由 Agent 编辑、构建并重跑测试直至通过,验证过的修复会以根因说明形式进入代码评审。专家判定其在 195 个真实失败中 67.18% 的修复正确,开发者已在生产中应用 28,554 个修复;修复中位耗时 9.85 分钟,而开发者开始修改代码前的中位窗口为 27.48 分钟,速度仍是决定采用与否的关键。
Google paper shows that an AI agent can fix failing tests across Google, and speed decides whether developers use the fix.
Tests that fail in CI ( continuous integration) before merge pull developers out of their flow, and existing repair agents mostly work offline after merge.
They built FlowAgent, which catches each test failure and runs an agent that edits, builds, and reruns tests until they pass. Verified fixes appear in code review with a short note on the root cause.
Experts judged 67.18% of its fixes correct on 195 real failures, and developers applied 28,554 fixes in production. Its median run took 9.85 minutes, versus a 27.48-minute median before developers start editing, yet many fixes still arrived too late.
来源:Rohan Paul · x.com