STUPID-2026-0014 Severity 5.8/10 — MEDIUM Verified

Devin CI workflow caused 836-comment spam storm on single PR

Agent: devin Language: yaml Domain: infra
Failure Mode
Infinite Loop
Root Cause
Tool Misuse
Task Type
Configuration
Reproducible
No

Quick Answer

Devin caused a medium-severity (5.8/10) infinite loop failure: Devin CI workflow caused 836-comment spam storm on single PR. The root cause was tool misuse. 836 comments of noise on a single PR.

Description

A Devin PR to migrate a project to GitHub Container Registry on arnaudlh/rover generated 836 comments — overwhelmingly automated CI feedback loops and Devin auto-responses. The PR was never merged. The volume of comments suggests the agent was caught in a CI feedback loop where each fix triggered new CI comments, which triggered new Devin responses, which triggered new fixes.

Instruction Given

Migrate to GitHub Container Registry and add version management

Expected Behavior

Submit a clean migration PR that passes CI

Actual Behavior

836 comments generated on a single PR. PR never merged. Evidence of CI/agent feedback loop where automated responses kept triggering each other.

Impact / Damage

836 comments of noise on a single PR. GitHub notification spam for all repo watchers. PR abandoned.

Share this incident

Help others know about this AI agent failure

Source: Github Pr View source Reported March 21, 2026

Frequently Asked Questions

What happened in incident STUPID-2026-0014?

A Devin PR to migrate a project to GitHub Container Registry on arnaudlh/rover generated 836 comments — overwhelmingly automated CI feedback loops and Devin auto-responses. The PR was never merged. The volume of comments suggests the agent was caught in a CI feedback loop where each fix triggered new CI comments, which triggered new Devin responses, which triggered new fixes.

Which AI agent caused this failure?

Devin was responsible for this infinite loop incident, documented as STUPID-2026-0014 in the StupidLLM AI agent incident database.

How severe was this AI agent failure?

It is rated 5.8/10 (medium) on StupidLLM's CVSS-style severity scale for AI agent failures, based on damage type, reversibility, and scope.

What was the root cause?

The root cause was classified as tool misuse. Submit a clean migration PR that passes CI

What was the impact or damage?

836 comments of noise on a single PR. GitHub notification spam for all repo watchers. PR abandoned.