Test gates

The stages a v3 task passes before it merges, in order. Each stage cites the station on the map that describes it. The figures are measured from the gate runs in the snapshot and are not estimates.

Stages

  1. Fresh containerEach round runs as a new job in a fresh container. Only the diff comes out.Source: map part sandbox, v3
  2. Clean rerunStops leftover processes, removes gitignored files the job made, reruns setup, then the checks.Source: reference/draft-map.html, v3 Rerun on a clean tree
  3. ChecksScoped checks while the coder works; the full matrix once at the gate.Source: reference/draft-map.html, v2 Scoped checks, v3 Rerun on a clean tree
  4. ReviewA separate reviewer job judges scope and quality. Any must-fix sends the task back, even under an approve verdict.Source: map part review, v3
  5. Host tests and mergeRebases on main and runs the host tests. With --auto-merge it fast-forwards main and pushes; without it the run stops at ready to merge. If main moved after the tests, it tests again.Source: map part merge, v3

Figures

Snapshot date: not measured

FigureValueTasksSource
Median gate time, serialnot measured0gate-snapshot, not measured
Median gate time, parallelnot measured0gate-snapshot, not measured
Overhead of removal, median per tasknot measured0gate-snapshot, not measured
Repair rounds, median per tasknot measured0gate-snapshot, not measured
Container removal step, mediannot measured—gate-snapshot, not measured

Per-task figures are medians over the snapshot's per-task medians. The container removal step is the median of every successful removal step in the gate logs, so it has no task count. Parallel and repair rounds are not in the instrument output yet.