Skip to content

Usage, Alerts and Troubleshooting

Cloud → CI runners shows usage for the current month for each pool: the number of jobs, the job minutes, and the 95th percentile queue wait.

The queue wait is the time between GitHub queueing a job and the job starting. A 95th percentile of a few seconds means that almost every job found a free slot on a running machine. A value of about a minute usually means jobs often arrive when the pool is idle. A higher value means jobs wait for other jobs to finish.

The price of a pool is fixed for the month and does not depend on these numbers. A pool that exists for part of a month is charged for that part.

Quant shows an alert on the pool and emails the members of your organisation who can manage pools in these cases. An alert emails at most once in 24 hours.

Alert Meaning What to do
Jobs are waiting for a free runner Jobs have waited longer than usual because every slot was busy Wait, or move the pool to a larger tier
The pool is at capacity The pool has been full for much of your working week Move the pool to a larger tier
The pool has an error Quant could not start machines for the pool Quant is alerted as well. Contact support if it does not clear

Check these in order:

  1. The labels. The runs-on line must have self-hosted, quant, the exact pool name and an architecture the pool offers.
  2. The connection. The pool must show Connected to your GitHub organisation.
  3. Repository access. Choose Manage access on GitHub and check that the app can see the repository.
  4. A public repository. Quant runners refuse jobs from public repositories.
  5. A full pool. If other jobs are running, the job starts when a slot is free.

The pool’s machines stop after the idle timeout. The next job waits about a minute for a machine. Turn on Keep one VM warm in business hours, or raise the idle timeout.

The runner image does not carry every tool that ubuntu-latest has. Add a setup action or an install step to the job. See Install the tools a job needs.

  • The job must run on a Quant runner. Jobs on GitHub-hosted runners do not receive Quant values.
  • Check the scope. A value for one repository must name the repository as owner/name.
  • Check the branch list. A value with a branch list does not reach pull request jobs or jobs on other branches.
  • A job for a pull request from a fork receives no Quant values.
  • The value must have been saved before the job started.

The pool shows “Disconnected from GitHub”

Section titled “The pool shows “Disconnected from GitHub””

The app was removed from your GitHub organisation, or its access was suspended. Choose Connect it to your GitHub organisation on the pool to install it again.

Quant could not deliver the job’s secrets and stopped the job so that it would not run without them. Run the job again. If it fails again, contact support with the link to the run.