Run list

Runs lists every run of a period, newest first, under the day it started (in your time zone). Runs still in progress stand on top, under Running now. A sharded CI run is one row, however many shards it had.

The lede

A sentence under the title counts the runs the list shows and says what the newest did: “70 runs in the last 30 days. #70 is running. The last 8 runs failed.” With a status filter or a search it only counts.

What a row shows

Column
(status)	the run’s status, as a mark - its name on hover
Run	the run number, and under it the run’s facts
Commit	the commit’s first line; under it the branch, the author, the short SHA, and the CI system when the period has runs from more than one
Results	a thin bar of the run’s tests, and under it the counts that are not zero: “66 passed · 2 failed · 2 skipped”
When	how long the run took, and under it how long ago it started (the exact date and time on hover)

The counts take every test once, however many shards reported it - its final attempt across all of them decides. Passed is a test that passed on the first try, flaky one that passed after a retry; together the four are all of the run’s tests. In a cancelled run, the tests the cancel cut off count nowhere. A count of zero is left out. Beside the bar stands the number of tests; while a run is going and its plan is known, it reads finished of planned - “38/47” - and the tests still to run show as a hatched part of the bar.

The duration runs from the first shard’s start to the last shard’s end. A long branch name is cut short; its full name shows on hover.

The facts under the number

A run with nothing special about it has nothing under its number. Otherwise the facts stand one per line, each a small grey icon and a word, in this order

• job key · Local · PR #n · Re-run of #N · shards. PR #n and Re-run of #N are links:

Fact
Local	a local run
job key	the run’s job key, with a workflow icon - for example firefox - when its job set SQUALLY_CI_JOB_KEY: which job of the CI run this is. See Matrix jobs
PR #n	the pull request the run belongs to. It opens the pull request on GitHub when the project has exactly one repository linked; the pull request’s title shows on hover
Re-run of #N	a re-run on GitHub Actions - it opens run #N, the attempt it re-ran
N shards	a sharded run: “3 shards” when every shard the run waits for reported, “2 of 3 shards” while one is missing. A re-run of failed jobs waits only for the shards it re-ran, so a re-run of two shards out of three reads “2 shards”. When more shards reported than the run waited for, the count stands alone: “4 shards”

Local, the job key (“Job key: firefox”), Re-run of #N and the shards say what they mean on hover. A click on a fact that is not a link opens the run, like the rest of the row.

Statuses

A run’s status is the first of these that applies:

1. Cancelled - a small grey stop square. The run was stopped from outside and said so; for a sharded run, any shard did. See Cancelled runs.
2. Incomplete - a half-filled yellow circle. A shard timed out, was stopped by the monthly result limit, or never reported while the others finished. See Incomplete: waiting or settled.
3. Running - a spinning circle. A shard is still sending results.
4. Failed - a red cross. Every shard finished, and a test’s final attempt failed.
5. Passed - a green check. Every shard finished, and none failed. A run whose flaky tests passed in the end is passed; the Flaky count says how many there were.

The same word stands for the run on its own page, in the comparison and in the read API.

Finding a run

The filters are a sentence over the list - “Showing CI and local runs on all branches from the last 30 days with any result” - and each bold part is a menu:

• Where they ran: CI and local runs, CI runs or local runs. Both is the default, as on every page: a run you just started on your laptop is there without switching. Pick CI runs to see your CI on its own.
• Branch: the branches of the period’s runs.
• Period: 7, 14, 30 or 90 days; 30 by default.
• Result: any result, Passed, Failed, Cancelled, Incomplete or Running, each with how many runs have it with the other filters applied.

Search, at the end of the sentence: a run number, part of a branch name, or pr 7 for a pull request. pr # lists every run of a pull request; pr alone does too, and still finds branches with “pr” in their name. A number finds a sharded run by any of its shards’ numbers.

The period and Show 20 more

A run belongs to the period by the start of its first shard, and the list is ordered by it. The list shows 20 runs; Show 20 more adds the next twenty. Every filter is applied before the list is cut, so a run whose shards started minutes apart is never split.