[Bug] Build status reports success for failed builds

Resolved 💬 3 comments Opened Apr 19, 2026 by devsparx Closed Apr 22, 2026

Whatever changed in the last day or so had made Claude much worse.

Bug Description
lied about succesfull builds, which failed

Environment Info

  • Platform: linux
  • Terminal: vscode
  • Version: 2.1.114
  • Feedback ID: f35b2cac-4ccf-4564-954b-53605fec1d0e

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/matthew/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n    at od$ (/$bunfs/root/src/entrypoints/cli.js:2753:2177)\n    at PH6 (/$bunfs/root/src/entrypoints/cli.js:2753:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T03:25:42.297Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/home/matthew/Dev/jibo/aura-admin/amplify'\n    at c_H (/$bunfs/root/src/entrypoints/cli.js:1567:144)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T03:27:34.350Z"},{"error":"Error: EISDIR: illegal operation on a directory, read '/home/matthew/Dev/jibo/aura-admin/.amplify'\n    at c_H (/$bunfs/root/src/entrypoints/cli.js:1567:144)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T03:27:35.058Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗