Fix loops and test scopes
A node's own view, opened from An item's page, draws the tasks inside the node. This page names the two specialist drawings there: a node with a fix loop and a changed-test-scope task.
A node with a fix loop
A node's own view draws the loop as a dashed arc under the steps, and once the loop has run, the repair and the judge sit on it as tasks of their own: click one to open it.
Picking a round
Beside the zoom, round n of m says which round the canvas shows. It starts on the newest. Open it to pick an earlier round, newest first, with what became of each; the canvas then shows every task as that round ran it, the repair that went on from it and the judge that came after it. latest ↩ goes back. The pick is yours until you leave the node.
A task in a round
A repair or judge that has not run in a round is drawn dashed and faded: the judge never runs before the first repair, so round 1's reads skipped · first repair.
A task's panel in such a node names the round in its subtitle (agent task · round 2 of 3 · running 41s) and shows that round's run, so the attempt n of m ▾ menu appears only when the round itself ran the task more than once.
A changed-test-scope task
A changed-test-scope task (kraft.verify_changed_test_scopes) opens in place
while it, or one of its scopes, is selected: its box becomes a frame with one row
per repository, in the order the task visits them (a workspace's root first, then
its members), and each repository's scopes as chips. A reduced-motion setting skips the move
and crossfades instead.
The frame
- Scopes that run one after another are joined in a line by arrows, and a task
set to
execution: parallelstacks them in a fork. - The frame is as wide as its longest row, and the steps after it move over to make room, so no row scrolls where the scroll wheel pans the canvas.
What a chip says
A chip says how that scope went and how long it took, and reads as the scope's command (an area's setup reads setup · area); hover it for the whole command and the paths it covers.
| You see | It means |
|---|---|
| a dashed waiting chip | a scope the round picked and has not started |
| not reached, with no chips | a repository after the first one that failed |
| new | against the round before it, a scope picked for the first time |
| a dashed not picked chip | a scope that ran last round and is not picked now; it stays in its row. A repository that ran nothing this round shows no chips at all |
A chip's panel
A chip opens the scope's own panel:
- its command and the paths it covers;
- its repository;
- how it went in every other round (passed, failed, running, waiting, not picked, or repo not reached);
- its log.
The open task's own Overview says how many of the round's scopes passed, how many repositories were reached and how its scopes run, with a key to new, not picked and the dashed ring.
Stepping back and closing
Esc steps back one: from a scope to its task, from the open task back to its box, then the panel folds as usual. Picking anything else, clicking the canvas, or the frame's close also folds it.
Related
- An item's page: the chain graph and the inspector that a node's view opens from.
- Fix loop: what a fix loop is, and the repair and the judge in it.