Reports
Single guest
Single VM report
One gen-vm guest with NVMe attached, built and inspected on a GitHub-hosted runner.
GPU guest
rocjitsu report
rocjitsu guest inspection plus the current GEMM and hipFile benchmark outputs.
Two guests
ernic report
The ernic stack, with VM 1 at the top-level page and VM 2 nested underneath.
fio lane
hipFile fio report
The fio libhipfile benchmark lane, published independently from the rocjitsu report.
Lane summary
| Lane | Schedule / trigger | Output |
|---|---|---|
report-for-vm-basic |
Push to main, daily 01:00 MST, manual dispatch |
/1vm/ |
report-for-vm-rocjitsu |
Path-filtered push to main, daily 01:00 MST, manual dispatch |
/rocjitsu/ |
report-for-vm-ernic |
Path-filtered push to main, daily 01:00 MST, manual dispatch |
/ernic/ and /ernic/vm2/ (ernic VM 1 / VM 2) |
report-for-hipfile-fio |
Path-filtered push to main, daily 01:00 MST, manual dispatch |
/hipfile-fio/ |
Why the reports stay separate
Each lane uploads a named artifact and stops. The Pages publisher assembles the latest artifact from each lane so one run cannot erase another lane’s content. That keeps the site complete even when a lane has not run for days. The four crons now fire together, so the publisher sees four completions in quick succession; it never cancels a run in progress, so they queue and the site settles once the last one drains.