Files
MetaCrate/docs/ci-runtime-evidence.md
Chili Palmer a213353011
Some checks failed
CI / required (push) Failing after 3m18s
Consolidate required CI gate (#115)
2026-08-12 20:53:49 +00:00

26 lines
1.4 KiB
Markdown

# Required CI runtime evidence
This record is populated from the consolidated `CI / required` Gitea job. A
qualifying sample consists of one deliberate cold native/dependency cache run
and four normal warm-cache runs on `aarch64-unknown-linux-gnu`. Each uploaded
`required-gate.json` contains per-stage elapsed time, Rust host/target, cache
hit state, available peak-memory evidence, and the Skia binary outcome.
The pre-consolidation Gitea baseline was 13 automatic workflows and 333 runs.
Successful maxima included 22.9 minutes for the native workspace, 32.0 minutes
for Skia, 66.6 minutes for artifact audit, and 86.0 minutes for the release
matrix. Native code generation had a 13.2-minute median and 18.5-minute maximum;
even this one concern could exceed the new complete-gate budget.
| Run | Cache | Elapsed | Result | Evidence |
| --- | --- | ---: | --- | --- |
| pending first consolidated run | cold | pending | pending | pending |
| pending second consolidated run | warm | pending | pending | pending |
| pending third consolidated run | warm | pending | pending | pending |
| pending fourth consolidated run | warm | pending | pending | pending |
| pending fifth consolidated run | warm | pending | pending | pending |
Branch protection must require only `CI / required` after all five rows are
green and at or below 15:00. Until then, this file deliberately records that
runtime parity and branch-protection migration are not yet proven.