Queue backlog
Master and pull request jobs ready to run but with no agent
yet, per pool (queue, OS and architecture), kept for 60 days.
Per slot divides by the slots seen in the last 30 days; the
tooltip names pools that share their hosts' slots.
CI time per build
Agent hours each master and pull request build used, from
the start to the end of each of its jobs, by the day the build
started. A pull request build runs for each pushed commit.
Only passed builds are counted, since cancelled and failed
builds stop partway and would hide what a full run costs.
Machine balance
Pools whose agents run on the same machines, with each pool's
jobs running and waiting as a multiple of its slots. Above 1× a
pool has a queue; below it has idle slots. The dashed line puts
every pool's jobs over all the hosts' slots, so a pool above it
is busier than its hosts as a whole.
Loading...
Connected agents
Agents connected at each update, all queues. The build, test,
launch and default queues start one agent per job, so they are
listed per host and a host is flagged after 3 days without a
job. Other agents are flagged when missing from the latest
snapshot.
Loading agent snapshots...
Loading worker history...
The share of agent time taken by each kind of job, from the
master (julia-ci) and pull request (julia-pr) jobs that finished
in the last 7 days, each counted from start to finish. Jobs still
running are left out.
Loading...