What needs to be done
Run the validation suite in CI (GitHub Actions) as a non-blocking job so we
can watch conformance evolve without red-gating active development.
The job should:
- Run on a Linux runner with the kernel features the runtime needs (namespaces,
cgroups v2). Note runner limitations (e.g. user-namespace / rootless constraints).
- Build
box and run make validation.
- Be marked non-required /
continue-on-error so a partially-red suite doesn't
block merges during this epic.
- Upload the suite output (TAP / summary) as a build artifact for inspection.
Acceptance criteria
Parent / tracking issue
Part of the OCI runtime validation epic.
Blocked by
- Add a local
make validation target to run the suite against box
Rough size
M — a day or two
What needs to be done
Run the validation suite in CI (GitHub Actions) as a non-blocking job so we
can watch conformance evolve without red-gating active development.
The job should:
cgroups v2). Note runner limitations (e.g. user-namespace / rootless constraints).
boxand runmake validation.continue-on-errorso a partially-red suite doesn'tblock merges during this epic.
Acceptance criteria
continue-on-erroror not a required check)Parent / tracking issue
Part of the OCI runtime validation epic.
Blocked by
make validationtarget to run the suite againstboxRough size
M — a day or two