Testing under bootstrap does not work on x86_64 macOS 10.14
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I tried running this test on 02b1be16c65e5716ade771afde7116ebdfbf9b4a:
uv run --python 3.10 ./x.py test tests/run-make/apple-deployment-target
The compiler builds fine, but the test fails with the following message:
thread 'main' panicked at $WORKSPACE/tests/run-make/apple-deployment-target/rmake.rs:56:9:
failed to get output of finished process: Os { code: 2, kind: NotFound, message: "No such file or directory" }
Which is really weird, because every file it uses is clearly available when I look through the directory.
I'm not yet sure if this is due to something specific to my setup, perhaps bootstrap doesn't like uv? Filing this bug mostly for myself to keep track of.
@rustbot label O-macos
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
Reproduce the failure with uv run --python 3.10 ./x.py test tests/run-make/apple-deployment-target on x86_64 macOS 10.14. Start at tests/run-make/apple-deployment-target/rmake.rs:56 and investigate why the finished process cannot be found despite the files being present. Done means identifying the environment or bootstrap cause and making this test run successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- build-system, operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100