diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-02 11:30:46 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-02 11:30:46 -0400 |
| commit | 4467eb66a4c8a776e35e9644960eba699dc85e6f (patch) | |
| tree | e75a53992746a902ba035d7b4ae76a5a401150e9 /debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md | |
| parent | faabc48f6d9b2d531b5b7a7e1320ccd1e030e85c (diff) | |
| download | open-iov-4467eb66a4c8a776e35e9644960eba699dc85e6f.tar.gz open-iov-4467eb66a4c8a776e35e9644960eba699dc85e6f.zip | |
debug: green-eye porting automation - new-device and driver-version port scripts, simulator packaging, porting docs; control-discovery fix
Diffstat (limited to 'debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md')
| -rw-r--r-- | debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md b/debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md index d687cca..aa71b54 100644 --- a/debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md +++ b/debug/risc-v-gsp-rm-vm/docs/21-CI-RELEASE-PIPELINE.md @@ -249,11 +249,13 @@ the docs/14 §6 pack; the docs/23 §4 step 7 expected-artifact list maps 1:1. * runs `python3 -m unittest discover -s tests -t .` from the tool root (QEMU integration tests run; if QEMU were absent they skip cleanly). -The intended release gates this workflow covers are the fast inventory smoke -from docs/19 §6 (`control_discovery --max-id 32 --patterns zero`), the harness -suites, and the docs/21 dry-run. A full `ci_release` run against real firmware -is driven manually/agentically because it needs the versioned inputs and -symbol DBs; CI-adjacent automation should call it with `--dry-run` first. +The release gates this workflow reaches are the harness suites: the docs/19 §6 +fast inventory smoke runs inside `tests/test_discovery.py`, and the docs/21 +dry-run is covered by `tests/test_version_diff.py`. The workflow does not run +`control_discovery` or `ci_release` as standalone steps. A full `ci_release` +run against real firmware is driven manually/agentically because it needs the +versioned inputs and symbol DBs; CI-adjacent automation should call it with +`--dry-run` first. --- @@ -318,3 +320,7 @@ or the demo ELF is absent. | **V1 — metrics/golden data** | deterministic self-diff and stable JSON reports support golden comparisons | | **docs/23 C5/C7** | release pipeline implemented and exercisable; dry-run rehearsal path | | **H7 — agentic harness** | self-describing bundle + docs/20 MCP tools for monitored runs | + +<!-- change (2026-10-02): state exactly which release gates the CI workflow +runs (unit suites) instead of implying standalone control_discovery/ci_release +steps; scope: §5 only; benefit: no false claim about CI coverage. --> |