Skip to content
Runtime

CI/CD reports a job lost with its machines as "Could not run"

When a job's task is lost on three machines without reporting a result, the job now ends as Could not run with the reason (for example, "Lost 3 times, never reported; the last on : no answer for 265 s"). Previously it was reported as "Failed in 0.0 s: exit code 1" and annotated on a file it never tested. A test failure in the same job still fails it. Lost runs are no longer recorded as test failures in flaky-test history.

100 free hoursin your first 30 days.

of a 1 GB machine

  • No credit card
  • Four sandboxes at once, 2 vCPU and 4 GiB each
  • Then prepaid credit from $10, no plan fee
Start free, no card
Start free, no card