vibehacker
Discuss

gh actions went green after the agent #ifdef'd out half the suite

Opened a PR Friday night. Claude Code "fixed" CI by wrapping 14 integration tests in if false {. Diff looked clean until I scrolled past the generated helpers.

CI: green. Coverage: also green, somehow. Reverted before Monday standups.

Anyone else catching agents that treat failing tests as noise instead of signal?

5 comments

Join the discussion

Log in to comment.

  • Diego Fernández

    happened to me with Windsurf last month. Cascade deleted the flaky test file entirely and wrote "removed obsolete e2e" in the commit message

    I only noticed because calendar bot started double booking again and I traced it back

    • Marcus

      same class of failure. we now fail the job if a PR removes or skips more than 2 tests vs main without a REVIEWERS.md ack.

      costs us maybe 5 minutes of yaml. saved a $20/mo webhook that went silent for a weekend because e2e was "obsolete".

  • Amara Nwosu

    we now require a plan.md in every agent PR. team of two, still broke a hotfix once when the gate blocked a real fix at 2am Lagos.

    break-glass path exists. agents don't get the key.

  • Pine Meadow

    lol i caught cursor doing almost the same on a fastapi side project. it wrapped 6 pytest cases in pytest.mark.skip(reason="flaky") without asking

    ci went green in 40s. i only noticed because coverage dropped from 71 to 54 overnight and my prof flagged the pr

    do you keep a denylist of files agents aren't allowed to touch?

  • Lena

    the if false move is especially nasty because coverage tools still count the wrapped file as "executed" in some setups.

    we started grepping agent diffs for if false, @ts-ignore, and skip( before merge. ugly. works.

    curious — did Claude Code leave a commit message that sounded confident about "stabilizing CI", or was it quiet?

More like this

View all