[BUG] Freestanding CI calls rustup after activating the Cargo environment #11

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

Summary

Lib-ipc CI fails in its freestanding checks because it invokes rustup after activating the owned Cargo environment. That environment deliberately exposes the selected build tools without the toolchain installer.

Reproduction

Run the push workflow at 73c8e8236ae70f0864ac0fcde524f5e4fd6b0a11, using Integration helper 74d8e38360864631a7dcfd1203efa340ab1d6ef8. The "Check freestanding libraries" step sources the Cargo environment and then runs rustup target add x86_64-unknown-none.

Expected and actual behavior

CI must install its validation target before entering the owned build environment, then run the freestanding Clippy and release checks with the selected tools.

Instead, the target installation exits 127 with rustup: command not found. Restoring the installer's access inside the build environment would unnecessarily expand its authority.

Environment and identity

  • Lib-ipc: 73c8e8236ae70f0864ac0fcde524f5e4fd6b0a11 on feature/posix-compat.
  • Integration helper: 74d8e38360864631a7dcfd1203efa340ab1d6ef8.
  • Linux rust:latest container; the failing command is workflow script 14, line 4.
  • No guest is involved. A working revision for this workflow ordering has not been established.

Evidence and prior checks

CI 622 retains the complete terminal log. Dependency acquisition and the preceding host checks finish successfully. The workflow places the target installation after sourcing the Cargo environment; the failure is in setup, before freestanding compilation begins.

Tracking

  • Locate the failing command in the complete current-source CI log.
  • Install the required target before preparing the owned Cargo workspace; keep the restricted build environment.
  • Pass current-source CI, including both freestanding libraries.

Related: Cargo dependency migration.

## Summary Lib-ipc CI fails in its freestanding checks because it invokes `rustup` after activating the owned Cargo environment. That environment deliberately exposes the selected build tools without the toolchain installer. ## Reproduction Run the push workflow at `73c8e8236ae70f0864ac0fcde524f5e4fd6b0a11`, using Integration helper `74d8e38360864631a7dcfd1203efa340ab1d6ef8`. The "Check freestanding libraries" step sources the Cargo environment and then runs `rustup target add x86_64-unknown-none`. ## Expected and actual behavior CI must install its validation target before entering the owned build environment, then run the freestanding Clippy and release checks with the selected tools. Instead, the target installation exits 127 with `rustup: command not found`. Restoring the installer's access inside the build environment would unnecessarily expand its authority. ## Environment and identity - Lib-ipc: `73c8e8236ae70f0864ac0fcde524f5e4fd6b0a11` on `feature/posix-compat`. - Integration helper: `74d8e38360864631a7dcfd1203efa340ab1d6ef8`. - Linux `rust:latest` container; the failing command is workflow script 14, line 4. - No guest is involved. A working revision for this workflow ordering has not been established. ## Evidence and prior checks [CI 622](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/622) retains the complete terminal log. Dependency acquisition and the preceding host checks finish successfully. The workflow places the target installation after sourcing the Cargo environment; the failure is in setup, before freestanding compilation begins. ## Tracking - [x] Locate the failing command in the complete current-source CI log. - [x] Install the required target before preparing the owned Cargo workspace; keep the restricted build environment. - [x] Pass current-source CI, including both freestanding libraries. Related: [Cargo dependency migration](https://git.erikinkinen.fi/erix/integration/issues/142).
Author
Owner

Published the setup-order fix in a69fed9c. CI installs its tools and freestanding target before preparing the owned Cargo workspace. The restricted build environment and both libraries' freestanding checks stay intact. Current-source CI remains pending.

Published the setup-order fix in [`a69fed9c`](https://git.erikinkinen.fi/erix/lib-ipc/commit/a69fed9cde63ad63047a9fac2f3161cb7bf8a8ff). CI installs its tools and freestanding target before preparing the owned Cargo workspace. The restricted build environment and both libraries' freestanding checks stay intact. Current-source CI remains pending.
Author
Owner

CI 624 passes both jobs at a69fed9c, including the freestanding Clippy/build checks and strict private Rustdoc. Both complete logs contain no warnings. Closing the setup-ordering fix; the original CI 622 failure remains recorded.

[CI 624](https://git.erikinkinen.fi/erix/lib-ipc/actions/runs/624) passes both jobs at `a69fed9c`, including the freestanding Clippy/build checks and strict private Rustdoc. Both complete logs contain no warnings. Closing the setup-ordering fix; the original CI 622 failure remains recorded.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:47 +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/lib-ipc#11
No description provided.