Old `executable-path` relies on internals of Cargo and will break with existing / upcoming features
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Tests assumes the location of build artifacts
- This isn't the case when a user sets
build.build-dir(added as of Cargo 1.91) - This isn't the case if we approve the new
build-dirlayout (https://github.com/rust-lang/cargo/issues/15010) - This isn't the case if we change the
build.build-dirdefault (https://github.com/rust-lang/cargo/issues/16147)
You can reproduce this by running either:
$ cargo +nightly test -Zbuild-dir-new-layout
$ CARGO_BUILD_BUILD_DIR=build cargo test
Upgrade to the latest version of executable-path for it to work (https://github.com/casey/executable-path/issues/2).
This problem was identified by the following crater run: https://github.com/rust-lang/rust/pull/149852
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 by running the two reproduction commands in the issue to confirm the executable-path failure under alternate Cargo build directories. Inspect the Cargo dependency configuration and update executable-path to the latest version referenced by the issue; done means both commands pass their tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100