Skip to content
Runtime

A CI/CD check that can no longer finish now fails, with the reason

Before, a check whose runner stopped, or whose job hung, could show "in progress" on GitHub for hours. Now it fails within minutes of the point it can no longer finish, saying why: a job sent nothing for longer than its 30-minute limit, no machine came for its jobs in 45 minutes, no runner has held it for 30 minutes, or it waited an hour to start. Re-run it on GitHub to check the commit again.

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