docs: close runtime quality review with consolidated lesson
Intrepid/Prometeu/Runtime/pipeline/pr-master There was a failure building this commit

This commit is contained in:
2026-10-14 14:24:14 +01:00
parent 3f9d235546
commit 39468740c3
11 changed files with 1168 additions and 210 deletions
+34 -31
View File
@@ -155,11 +155,17 @@ steps inside one gate cannot protect against an independent process.
### Prerequisites and reports
Both pipelines use `bash scripts/provision-quality-gate.sh`. A Debian/Ubuntu
agent needs root or sudo for apt provisioning, and an existing Rust/rustup
installation. GitHub installs stable Rust first; Jenkins must supply a supported
Rust toolchain and rustup in CARGO_HOME/bin. The script installs rustfmt, Clippy,
llvm-tools-preview and pinned cargo-llvm-cov 0.8.5 (`--locked`).
Jenkins uses `bash scripts/check-quality-gate-prerequisites.sh` to validate an
already provisioned agent. The job does not install system packages, Rust
components or Cargo tools and does not require root or sudo. The agent image
must supply a supported Rust toolchain and rustup in CARGO_HOME/bin, rustfmt,
Clippy, llvm-tools-preview and pinned cargo-llvm-cov 0.8.5.
Provision the Jenkins agent before running jobs. The standalone
`bash scripts/provision-quality-gate.sh` helper requires root or sudo on
Debian/Ubuntu and an existing Rust/rustup installation; run it during agent
setup, with Rust tools installed for the job user. GitHub's disposable hosted
runner still uses this helper after installing stable Rust.
Linux packages include build-essential, pkg-config, libasound2-dev, libudev-dev,
libxkbcommon-dev, libwayland-dev, libx11-dev, libxrandr-dev, libxi-dev, Python 3,
@@ -176,10 +182,10 @@ status; the log preserves underlying Cargo diagnostics. Three regression cases
check failure logs/identity, fresh success evidence and partial-report retention
when a later gate fails.
Both pipelines discard old generated report directories before provisioning and
Both pipelines discard old generated report directories before environment checks or setup and
publish current artifacts even after gate failure. An early failed gate has
metadata/logs but no old coverage report. Failure after generation preserves the
partial current reports. Provisioning failure can leave no report at all and
partial current reports. Prerequisite or setup failure can leave no report at all and
still fails CI. Reports are archived from `target/quality-gate/**` and
`target/llvm-cov/**`; Jenkins also publishes current HTML when present. Artifact
publication does not turn a failed gate into success.
@@ -271,42 +277,39 @@ The full local `make ci-domains` validation passed with 939 tests passed and
in verification; its final floor uses the lower measurement. All gates were
rechecked against the verification report after that final adjustment.
## Ownership-repair measurement
## Current coverage measurement
The [ownership-repair evidence](COVERAGE_DOMAINS_CURRENT.json) records the repaired
module-tree ownership, fixed floors, normalized source paths, actual line
counts and source/config/report fingerprints. Both historical JSON records
above remain unchanged. The measurement uses the implementation working tree
identified by its base HEAD and content fingerprints.
The [current evidence](COVERAGE_DOMAINS_CURRENT.json) identifies the committed
source by HEAD and content fingerprints, records the strict shared gate and
retains the earlier ownership-repair measurement as historical evidence.
Both original historical JSON records above remain unchanged. The latest
measurement uses the repaired module-tree map with all 15 fixed floors.
| Domain | Covered / total lines | Measured lines | Fixed floor | Margin (points) |
| --- | ---: | ---: | ---: | ---: |
| system/os | 1410 / 1711 | 82.40% | 77.24% | 5.16 |
| system/runtime | 2762 / 3309 | 83.46% | 76.19% | 7.27 |
| system/fs | 1944 / 2469 | 78.73% | 76.08% | 2.65 |
| system/runtime | 2757 / 3309 | 83.31% | 76.19% | 7.12 |
| system/fs | 1946 / 2469 | 78.81% | 76.08% | 2.73 |
| system/programs | 556 / 567 | 98.05% | 93.05% | 5.00 |
| asset/bank | 3096 / 3420 | 90.52% | 86.76% | 3.76 |
| asset/bank | 3176 / 3434 | 92.48% | 86.76% | 5.72 |
| firmware | 1990 / 2314 | 85.99% | 83.20% | 2.79 |
| host-dependent | 1196 / 2059 | 58.08% | 40.05% | 18.03 |
| host-dependent | 1531 / 2393 | 63.97% | 40.05% | 23.92 |
| host/headless | 739 / 855 | 86.43% | 83.39% | 3.04 |
| vm/core | 8308 / 9294 | 89.39% | 84.29% | 5.10 |
| vm/core | 8522 / 9526 | 89.46% | 84.29% | 5.17 |
| bytecode | 3085 / 3303 | 93.39% | 88.26% | 5.13 |
| hal/core | 2093 / 2369 | 88.34% | 83.56% | 4.78 |
| drivers/core | 2728 / 3059 | 89.17% | 79.51% | 9.66 |
| drivers/core | 2775 / 3107 | 89.31% | 79.51% | 9.80 |
| system/core | 1353 / 1444 | 93.69% | 87.71% | 5.98 |
| tooling | 396 / 612 | 64.70% | 59.75% | 4.95 |
| dev/test-support | 99 / 115 | 86.08% | 80.96% | 5.12 |
The fresh macOS/aarch64 `make ci-domains` run passed all 15 coverage gates
with 1,021 tests passed and 11 ignored. The 10 focused ownership/evidence
tests and strict package Clippy also passed. No floor reduction or additional
runtime behavior test was needed to pass the repaired map.
At the time of that ownership measurement the target used non-strict workspace
Clippy, and a separate strict invocation failed on VM `useless_vec`,
`cloned_ref_to_slice_refs` and `items_after_test_module` diagnostics. That historical
record qualifies the repaired coverage map, not the later strict gate. The lint
sources have since been corrected without blanket suppression or floor changes.
The fresh macOS/aarch64 `make ci-domains` run passed all 15 domain gates,
1,060 ordinary tests (13 ignored), five explicit socket tests and three
runner regression tests. The fresh coverage replay also passed 1,060 tests;
it is not an additional set of unique behavioral tests. All ten focused
ownership/evidence tests passed again on the committed source. No floor
was lowered. The retained ownership-repair measurement used the earlier
non-strict gate; the current measurement passes strict workspace Clippy.
Platform-specific compilation and host scenarios can change report totals.
Local evidence does not certify an unexecuted Linux or Intel Mac run; evaluate
@@ -315,10 +318,10 @@ those runs against the configured floors and investigate differences.
## Strict shared-gate qualification
On 2026-10-14, macOS/aarch64 with rustc 1.98.1, the shared target passed strict
workspace/all-target/all-feature Clippy, all 1,039 ordinary tests (13 ignored),
workspace/all-target/all-feature Clippy, all 1,060 ordinary tests (13 ignored),
the five explicitly selected socket tests, three gate-runner regression tests,
and all 15 fixed coverage domain gates. The separate fresh coverage execution
also passed 1,039 tests with 13 ignored. Those repeated runs are not distinct
also passed 1,060 tests with 13 ignored. Those repeated runs are not distinct
behavioral tests and must not be added into a unique-test count.
The baseline strict invocation failed on the concrete VM lint sources above;