Job Results (Web)
Job detail page
After submitting a job, you land on the job detail page. The header shows:
- Status badge (queued, running, completed, failed, etc.)
- Job ID, creation time, and total duration
- Action buttons: Cancel (if running), Retry, Clone
Tabs
Timeline
Shows the winning run’s pipeline steps (synth, pnr, bitstream) with start/end times and durations. Visible once a winner is selected.
Logs
Real-time log output streamed via WebSocket. The first lines contain a Build Environment block showing worker hostname, container ID, OS version, worker version, run/job/seed context, target info, and toolchain versions (yosys, ghdl, nextpnr, icepack, ecppack). This metadata aids reproducibility and debugging. Synthesis, place-and-route, and bitstream generation output follows. After the job completes, full logs remain available.
QoR (Quality of Results)
Summary metrics for the winning run:
- Timing: Fmax (maximum frequency achieved)
- Area: LUT utilization, register count
- Critical path details
Also shows a download command for the build archive.
Seeds
Visible when the job has multiple seeds. Shows a table comparing all runs: seed number, status, Fmax, LUT count, and whether it’s the winner.
Artifacts
- Download Build Archive button — downloads the full archive (
.tar.gzor.zip) - Artifact table: lists individual files (bitstream, netlist, logs, reports) with type, filename, size, and SHA-256 checksum
Job actions
Cancel
Stops all in-flight runs. Available while the job is queued or running.
Retry
Re-runs failed seeds (or all seeds). Creates new runs under the same job.
- Failed only — retry seeds that failed or were terminated
- All — retry every seed
Clone
Creates a new job with the same source and parameters. You can override seeds, parallelism, priority, strategy, or target.