[BUG] Component CI requires an absent Rust toolchain file #147

Open
opened 2026-10-17 02:01:06 +02:00 by erikinkinen · 1 comment
Owner

Summary

Component CI stops before Cargo when a repository has no rust-toolchain.toml. Seventeen current jobs show the same failure, including Lib-crc, Lib-ipc and Launchd.

Reproduction

Run the Cargo preparation step from Lib-crc CI at 9bb4bcc76b7c24d2b18c07e0ef68754d7cbefd5f, using Integration helper a30b1e0efaf30aa6a254e4e128f7173838b47115 in the maintained rust:latest container.

Expected and actual behavior

A repository without a toolchain file must be able to use its installed Rust toolchain. Preparation must retain exact executable identities and must not install another toolchain implicitly.

Actual output is error: [Errno 2] No such file or directory: 'rust-toolchain.toml', followed by exit 2.

Environment and identity

  • Component: Lib-crc 9bb4bcc76b7c24d2b18c07e0ef68754d7cbefd5f.
  • Shared helper: Integration a30b1e0efaf30aa6a254e4e128f7173838b47115.
  • Host: x86_64 Linux, maintained Rust CI container; Python 3.13.5 in the original log.
  • No guest or image is involved. The previous helper did not require this file.

Evidence and prior checks

The original Lib-crc log passes dependency policy, then fails during tool selection before compilation. The selector reads the toolchain file whenever Cargo resolves through Rustup, even when the repository does not declare one. Seventeen retained terminal logs contain that missing-file error; other fleet failures are being investigated separately.

Tracking

  • Select and retain existing installed Rust executables without requiring a toolchain file.
  • Preserve explicit tool selections, maintained channel selection, failure handling and disabled automatic installation.
  • Cover repositories with and without a toolchain file in regression tests.
  • Publish helper adoption and pass the affected component CI jobs.

Related: dependency migration.

## Summary Component CI stops before Cargo when a repository has no `rust-toolchain.toml`. Seventeen current jobs show the same failure, including Lib-crc, Lib-ipc and Launchd. ## Reproduction Run the Cargo preparation step from Lib-crc CI at `9bb4bcc76b7c24d2b18c07e0ef68754d7cbefd5f`, using Integration helper `a30b1e0efaf30aa6a254e4e128f7173838b47115` in the maintained `rust:latest` container. ## Expected and actual behavior A repository without a toolchain file must be able to use its installed Rust toolchain. Preparation must retain exact executable identities and must not install another toolchain implicitly. Actual output is `error: [Errno 2] No such file or directory: 'rust-toolchain.toml'`, followed by exit 2. ## Environment and identity - Component: Lib-crc `9bb4bcc76b7c24d2b18c07e0ef68754d7cbefd5f`. - Shared helper: Integration `a30b1e0efaf30aa6a254e4e128f7173838b47115`. - Host: x86_64 Linux, maintained Rust CI container; Python 3.13.5 in the original log. - No guest or image is involved. The previous helper did not require this file. ## Evidence and prior checks The original Lib-crc log passes dependency policy, then fails during tool selection before compilation. The selector reads the toolchain file whenever Cargo resolves through Rustup, even when the repository does not declare one. Seventeen retained terminal logs contain that missing-file error; other fleet failures are being investigated separately. ## Tracking - [x] Select and retain existing installed Rust executables without requiring a toolchain file. - [x] Preserve explicit tool selections, maintained channel selection, failure handling and disabled automatic installation. - [x] Cover repositories with and without a toolchain file in regression tests. - [ ] Publish helper adoption and pass the affected component CI jobs. Related: [dependency migration](https://git.erikinkinen.fi/erix/integration/issues/142).
Author
Owner

Fixed in 4ebc6af1. Tool selection supports explicit executables, project channels and the installed Rustup default, including hardlinked and copied proxies. Queries remain bounded and automatic installation stays disabled.

All 15 regression tests pass, and a real installed Rustup selection succeeds without a project file. The original failure is visible in Lib-crc CI 36. Component workflows are being updated to the repaired helper; affected CI acceptance remains open.

Fixed in [4ebc6af1](https://git.erikinkinen.fi/erix/integration/commit/4ebc6af150d8648470ad1041993b4c2ebc30146c). Tool selection supports explicit executables, project channels and the installed Rustup default, including hardlinked and copied proxies. Queries remain bounded and automatic installation stays disabled. All 15 regression tests pass, and a real installed Rustup selection succeeds without a project file. The original failure is visible in [Lib-crc CI 36](https://git.erikinkinen.fi/erix/lib-crc/actions/runs/36). Component workflows are being updated to the repaired helper; affected CI acceptance remains open.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:18 +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#147
No description provided.