New Issue: "Play" button in Chapel Codespaces runs previous binary on failed compilation

29619, "bradcray", ""Play" button in Chapel Codespaces runs previous binary on failed compilation", "2026-10-29T18:30:47Z"

While using Chapel in a GitHub Codespace today, I found that if I did the following actions:

  • launch a codespace
  • use the "Play" button to compile and run a correct program
  • introduce a bug into the program (e.g., syntax error or unused variable)
  • use the "Play" button a second time

The compilation would fail as expected, but the binary from the previous compile would be executed, making it appear as though perhaps it actually worked (assuming the binary's behavior wasn't expected to change).

I'm hoping this could be improved by checking for error codes from the compilation step and not running the binary if there's a failure.