-
Notifications
You must be signed in to change notification settings - Fork 0
Create CI status issue for compile, smoke, and readiness gates #11
Copy link
Copy link
Open
Labels
area: ci-gatesCI, QEMU gates, regression/readiness/release checks.CI, QEMU gates, regression/readiness/release checks.needs: validationNeeds validation evidence or gate run.Needs validation evidence or gate run.priority: P2-mediumMedium-priority planned work.Medium-priority planned work.type: ciContinuous integration or automation work.Continuous integration or automation work.
Description
Metadata
Metadata
Assignees
Labels
area: ci-gatesCI, QEMU gates, regression/readiness/release checks.CI, QEMU gates, regression/readiness/release checks.needs: validationNeeds validation evidence or gate run.Needs validation evidence or gate run.priority: P2-mediumMedium-priority planned work.Medium-priority planned work.type: ciContinuous integration or automation work.Continuous integration or automation work.
Summary
Track CI status for compile checks, smoke tests, regression, and readiness gates.
Problem / objective
The GitHub Actions workflow runs compile, ABI, smoke, and regression jobs, while readiness/full-RC gates are local. A single tracking issue should summarize what is CI-covered versus manual/local.
Acceptance criteria
Validation
make compile-checkmake qemu-smokemake qemu-regression-suitemake qemu-readiness-gateif local host supports itRelevant files
.github/workflows/ci.ymlMakefilescripts/qemu-smoke.pyscripts/qemu-regression-suite.pyscripts/qemu-readiness-gate.py