Repository navigation
fix(ci): limit setup for golden checks and benchmark reports - #2031
Conversation
Golden label checks need just and ORAS. Benchmark reports need Rust. These jobs avoid the LLVM installer and its unsupported Ubuntu fallback. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: cshung <3410332+cshung@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are reported for the scoped workflow setup changes.
No open issues 🎉
What changed in this PR
Limits setup in the golden-label and benchmark-report jobs to their required tools, avoiding unnecessary LLVM installation and hypervisor setup. Build and test jobs retain their existing setup.
Changes:
- Golden-label checks use pinned
setup-justalongside the existing ORAS setup. - Benchmark reporting uses Rust-only setup with caching and diagnostic matching disabled.
| File | Description |
|---|---|
.github/workflows/ValidatePullRequest.yml |
Narrows tool setup for golden-label checks and benchmark reports. |
Review effort: Balanced
Benchmark ResultsMeasured commit: kvm / amd (Linux) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
kvm / intel (Linux) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
mshv3 / amd (Linux) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
mshv3 / intel (Linux) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
hyperv-ws2025 / amd (Windows) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
hyperv-ws2025 / intel (Windows) (➖ stable)No benchmark improved or regressed. Benchmark Resultsfunction_call_codec
payload_allocation
sandboxes
slot_pool
snapshot_files
virtq_readonly
virtq_readwrite
Reported by |
ludfjig
left a comment
There was a problem hiding this comment.
I fixed this recently in hyperlgiht-wasm by downgrading ubuntu-latest back to 24.04 hyperlight-dev/hyperlight-wasm#568
Summary
The golden-label check uses just and ORAS. Benchmark reporting uses Rust. Neither job needs LLVM or hypervisor setup.
The shared setup can stall installing LLVM 18, then fall back to an unsupported Ubuntu resolute repository. Build and test jobs retain their existing setup.
Related to #1985. The earlier archive-install fix is hyperlight-dev/ci-setup-workflow#25.
Failing run: https://github.com/hyperlight-dev/hyperlight/actions/runs/42074355074
Validation