[BUG] Component documentation gate rejects non-Cargo repositories #155

Closed
opened 2026-10-17 06:24:48 +02:00 by erikinkinen · 3 comments
Owner

Summary

The component documentation gate rejects repositories without Cargo packages, stopping Integration CI before the guest scenarios.

Reproduction

Run the component gate at Integration 213ce6a86d2e242527cf0ac33adcd520a1b1bd53:

python3 -B -Werror scripts/check-rustdoc-policy.py --components components.toml --cargo-catalog cargo-repos.toml

CI 2777 reproduces the failure.

Expected and actual behavior

Repositories without Cargo manifests should have their original source checked without creating or exempting a Cargo lock. Cargo repositories must retain their metadata and documentation checks.

The generated-workspace verifier instead requires a nonempty manifest selection for every root and exits with select exact original manifests for generated root-lock ownership.

Environment and identity

Integration 213ce6a8, Linux VM CI job 48622, attempt 1. The failure occurs in the host documentation gate after the Timed clock check and source-size gate pass. No guest scenario result is implied.

Evidence and prior checks

The complete terminal log records source-size coverage of 76 repositories and 7,544 tracked files, followed by this error and exit status 1. GeneratedCiCargo._inputs calls the generated-lock verifier even when its original manifest selection is empty; that verifier correctly refuses an empty exemption request.

Tracking

  • Verify non-Cargo source strictly without granting a generated-lock exemption.
  • Cover no-manifest repositories, original and added locks, and continued Cargo checks.
  • Publish the repair and pass the component documentation gate in CI.

Related: Integration review.

## Summary The component documentation gate rejects repositories without Cargo packages, stopping Integration CI before the guest scenarios. ## Reproduction Run the component gate at Integration `213ce6a86d2e242527cf0ac33adcd520a1b1bd53`: ```sh python3 -B -Werror scripts/check-rustdoc-policy.py --components components.toml --cargo-catalog cargo-repos.toml ``` [CI 2777](https://git.erikinkinen.fi/erix/integration/actions/runs/2777) reproduces the failure. ## Expected and actual behavior Repositories without Cargo manifests should have their original source checked without creating or exempting a Cargo lock. Cargo repositories must retain their metadata and documentation checks. The generated-workspace verifier instead requires a nonempty manifest selection for every root and exits with `select exact original manifests for generated root-lock ownership`. ## Environment and identity Integration `213ce6a8`, Linux VM CI job 48622, attempt 1. The failure occurs in the host documentation gate after the Timed clock check and source-size gate pass. No guest scenario result is implied. ## Evidence and prior checks The complete terminal log records source-size coverage of 76 repositories and 7,544 tracked files, followed by this error and exit status 1. `GeneratedCiCargo._inputs` calls the generated-lock verifier even when its original manifest selection is empty; that verifier correctly refuses an empty exemption request. ## Tracking - [x] Verify non-Cargo source strictly without granting a generated-lock exemption. - [x] Cover no-manifest repositories, original and added locks, and continued Cargo checks. - [x] Publish the repair and pass the component documentation gate in CI. Related: [Integration review](https://git.erikinkinen.fi/erix/integration/pulls/12).
Author
Owner

Published 1428cb5b sends roots without Cargo manifests through complete original-file and directory verification. The lock-specific verifier still requires an explicit nonempty manifest selection. Four new regressions cover no-Cargo roots, unchanged tracked locks, added locks and a subsequent real Cargo component.

Published [`1428cb5b`](https://git.erikinkinen.fi/erix/integration/commit/1428cb5b1a0a88eaeae70d3c25890267004c5dbb) sends roots without Cargo manifests through complete original-file and directory verification. The lock-specific verifier still requires an explicit nonempty manifest selection. Four new regressions cover no-Cargo roots, unchanged tracked locks, added locks and a subsequent real Cargo component.
Author
Owner

All 13 tests in the generated-Cargo module pass on published 1428cb5b, including the four new original-source and lock regressions. CI 2780 passes Rust and Markdown; its VM job is still running. The final component-gate criterion remains open.

All 13 tests in the generated-Cargo module pass on published `1428cb5b`, including the four new original-source and lock regressions. [CI 2780](https://git.erikinkinen.fi/erix/integration/actions/runs/2780) passes Rust and Markdown; its VM job is still running. The final component-gate criterion remains open.
Author
Owner

The repair in 1428cb5b passes the component documentation gate in CI2780: 76 repositories, 76 manifests, 269 crate roots and 4,046 authored Rust files. All three criteria are complete.

The VM job later fails while starting the bootloader build because it cannot find cargo-repos. That separate path-selection failure occurs before guest scenarios and remains under investigation; this closure covers the documentation gate.

The repair in `1428cb5b` passes the component documentation gate in [CI2780](https://git.erikinkinen.fi/erix/integration/actions/runs/2780): 76 repositories, 76 manifests, 269 crate roots and 4,046 authored Rust files. All three criteria are complete. The VM job later fails while starting the bootloader build because it cannot find `cargo-repos`. That separate path-selection failure occurs before guest scenarios and remains under investigation; this closure covers the documentation gate.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:19 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#155
No description provided.