[BUG] Timed CI resolves tools after activating the owned Cargo environment #151

Closed
opened 2026-10-17 03:40:00 +02:00 by erikinkinen · 2 comments
Owner

Summary

The Timed legacy-clock CI step resolves rustc and rustdoc through rustup after activating the owned Cargo environment. Its restricted PATH intentionally excludes the installer, so tool selection belongs before activation.

Reproduction

In Integration 74d8e38360864631a7dcfd1203efa340ab1d6ef8, inspect the "Check the original Timed legacy clock contract" step. It sources Timed's generated Cargo environment before evaluating $(rustup which rustc) and $(rustup which rustdoc).

Expected and actual behavior

Select the compiler and rustdoc paths during CI setup and pass them explicitly to the existing clock-contract checker. Preserve the owned build environment and the original contract limits.

The current ordering performs both installer lookups inside that restricted environment. This is a source-inspection finding; a current CI failure at this step has not been captured.

Environment and identity

  • Integration: 74d8e38360864631a7dcfd1203efa340ab1d6ef8 on feature/posix-compat.
  • Linux integration CI, Timed legacy-clock host contract.
  • The generated environment selects explicit Cargo/rustc paths and an owned PATH; it does not export rustdoc or expose rustup.
  • No guest or newly executed clock-contract failure is claimed.

Evidence and prior checks

The workflow contains the post-activation lookups. The environment writer establishes the restricted PATH. Lib-ipc's captured failure demonstrates the same installer-lookup error in another caller.

Tracking

  • Identify the late tool lookups and the environment boundary they cross.
  • Select both tools before activation and retain the original clock-contract checks.
  • Pass the current-source Timed clock-contract CI step.
## Summary The Timed legacy-clock CI step resolves `rustc` and `rustdoc` through `rustup` after activating the owned Cargo environment. Its restricted PATH intentionally excludes the installer, so tool selection belongs before activation. ## Reproduction In Integration `74d8e38360864631a7dcfd1203efa340ab1d6ef8`, inspect the "Check the original Timed legacy clock contract" step. It sources Timed's generated Cargo environment before evaluating `$(rustup which rustc)` and `$(rustup which rustdoc)`. ## Expected and actual behavior Select the compiler and rustdoc paths during CI setup and pass them explicitly to the existing clock-contract checker. Preserve the owned build environment and the original contract limits. The current ordering performs both installer lookups inside that restricted environment. This is a source-inspection finding; a current CI failure at this step has not been captured. ## Environment and identity - Integration: `74d8e38360864631a7dcfd1203efa340ab1d6ef8` on `feature/posix-compat`. - Linux integration CI, Timed legacy-clock host contract. - The generated environment selects explicit Cargo/rustc paths and an owned PATH; it does not export rustdoc or expose rustup. - No guest or newly executed clock-contract failure is claimed. ## Evidence and prior checks The [workflow](https://git.erikinkinen.fi/erix/integration/src/commit/74d8e38360864631a7dcfd1203efa340ab1d6ef8/.github/workflows/ci.yml#L314) contains the post-activation lookups. The [environment writer](https://git.erikinkinen.fi/erix/integration/src/commit/74d8e38360864631a7dcfd1203efa340ab1d6ef8/scripts/cargo_ci_gateway.py#L297) establishes the restricted PATH. [Lib-ipc's captured failure](https://git.erikinkinen.fi/erix/lib-ipc/issues/11) demonstrates the same installer-lookup error in another caller. ## Tracking - [x] Identify the late tool lookups and the environment boundary they cross. - [x] Select both tools before activation and retain the original clock-contract checks. - [x] Pass the current-source Timed clock-contract CI step.
Author
Owner

Published the tool-order correction in b59c6cbc. The CI step resolves both tool paths before activating the owned environment and keeps the original clock-contract arguments and limits. The current-source Timed CI step remains pending.

Published the tool-order correction in [`b59c6cbc`](https://git.erikinkinen.fi/erix/integration/commit/b59c6cbc1afa337bf93ed6275b390c44435d7867). The CI step resolves both tool paths before activating the owned environment and keeps the original clock-contract arguments and limits. The current-source Timed CI step remains pending.
Author
Owner

The Timed clock-contract step passes on published 213ce6a8 in CI 2777: formatting, strict Clippy, all 65 tests and rustdoc complete without warnings. The complete VM job log then continues to later gates. All three criteria here are met.

That job remains failed because the component documentation gate rejects non-Cargo repositories; this separate failure is tracked in #155.

The Timed clock-contract step passes on published `213ce6a8` in [CI 2777](https://git.erikinkinen.fi/erix/integration/actions/runs/2777): formatting, strict Clippy, all 65 tests and rustdoc complete without warnings. The complete VM job log then continues to later gates. All three criteria here are met. That job remains failed because the component documentation gate rejects non-Cargo repositories; this separate failure is tracked in [#155](https://git.erikinkinen.fi/erix/integration/issues/155).
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#151
No description provided.