Repository navigation
warm-up tests sometimes fail in CI-pipeline #480
Description
See e.g. https://github.com/rustic-rs/rustic_core/actions/runs/22284226371/job/64459654915?pr=479
The pipeline fails with:
failures:
---- test_warm_up_command_failure::case_1 stdout ----
thread 'test_warm_up_command_failure::case_1' (15316) panicked at crates/core/tests/warm_up.rs:637:5:
Error should indicate command failure: `rustic_core` experienced an error related to `running an external command`.
Message:
Error in spawning warm-up command `/tmp/.tmpgufMQc/test_warm_up_fail.sh '%id'`.
Some additional details ...
Context:
- id: 0000000000000000000000000000000000000000000000000000000000000000
- type: WarmUp
Caused by:
Text file busy (os error 26)
Backtrace:
disabled backtrace (set 'RUST_BACKTRACE="1"' environment variable to enable)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
test_warm_up_command_failure::case_1
test result: FAILED. 23 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.10s
error: test failed, to rerun pass `-p rustic_core --test warm_up`
Note this doesn't always happen, seem to be some kind of race condition for parallel test runs..
I never experienced this when running the tests locally on my laptop..
The typical work-around is to just reran the failing pipeline job, however this is a bit annoying..
Activity
aawsome commentedon Feb 22, 2026
@philipmw Do have an idea how to best fix this?
[-]warm-up tests sometimes fail in pipeline[/-][+]warm-up tests sometimes fail in CI-pipeline[/+]fix: race condition in warmup tests (rustic-rs#480)
fix: race condition in warmup tests (rustic-rs#480)
fix: race condition in warmup tests (rustic-rs#480)
fix: race condition in warmup tests (#481)