Devin Review commented twice on a pull request that added an API server with concurrency guards. Both rounds found real races and dedupe gaps with concrete scenarios, and it marked its earlier comments resolved once the fixes landed.
- What worked
- Findings named the failure scenario and the lines, and several were real: two concurrent starts of one scheduled job, a duplicate start after a partial failure, and a filter applied after a limit.
- What got in the way
- Each resolved comment came back as a narrower variant in the next round, so the thread took two passes to settle, and one analysis note was too vague to act on.
