ci: call cargo_env after sourcing build_lib.sh so cargo is on PATH #3

Closed

mik-tf wants to merge 3 commits from development_mik into development

mik-tf commented

2026-04-28 01:13:06 +00:00

Owner

Fixes the silent CI red on development: every run bails immediately at the first make call with cargo: No such file or directory. The shell exec context for each step does not auto-source ~/.cargo/env. Same fix already proven on hero_archipelagos and other green repos.

No behavioural change on hosts where cargo is already on PATH.

Signed-off-by: mik-tf

Fixes the silent CI red on `development`: every run bails immediately at the first `make` call with `cargo: No such file or directory`. The shell exec context for each step does not auto-source `~/.cargo/env`. Same fix already proven on hero_archipelagos and other green repos. No behavioural change on hosts where cargo is already on PATH. Signed-off-by: mik-tf

mik-tf added 1 commit

2026-04-28 01:13:06 +00:00

ci: call cargo_env after sourcing build_lib.sh so cargo is on PATH

Build and Test / build (pull_request) Failing after 0s

Details

c2af269a54

CI on `development` was failing every run with
`make: cargo: No such file or directory`. Sourcing build_lib.sh only
defines its functions — it does NOT auto-prepend cargo/rustup to
PATH. The required helper `cargo_env` is defined right there in
build_lib.sh; the workflow just wasn't calling it after the source.

Same minimal fix as the working-CI repos. No behavioural change
on hosts where cargo is already on PATH (cargo_env is idempotent).

Signed-off-by: mik-tf

mik-tf added 1 commit

2026-04-28 01:21:49 +00:00

ci: retrigger after Docker network pool exhaustion

Build and Test / build (pull_request) Failing after 43s

Details

72918fc2fe