suite::cli_self_upd::as_rustup_setup test failure
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
---- suite::cli_self_upd::as_rustup_setup stdout ----
ran: rustup ["set", "default-host", "aarch64-unknown-linux-gnu"]
inprocess: true
status: Some(0)
duration: 0.019s
stdout:
====
====
stderr:
====
====
ran: rustup ["set", "auto-self-update", "disable"]
inprocess: true
status: Some(0)
duration: 0.005s
stdout:
====
====
stderr:
====
info: auto-self-update mode set to disable
====
thread 'suite::cli_self_upd::as_rustup_setup' (23443) panicked at src/test/clitools.rs:411:18:
Unable to run test command: Os { code: 26, kind: ExecutableFileBusy, message: "Text file busy" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
https://github.com/rust-lang/rustup/actions/runs/23617673180/job/68789195646?pr=4776#step:17:1353
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with suite::cli_self_upd::as_rustup_setup and the panic at src/test/clitools.rs:411; reproduce the failure using the linked CI run as context. Trace the command that returns ExecutableFileBusy and confirm the test completes without that panic when the failure is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100