-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: avoid inserting duplicate dylib_path_envvar
when calling cargo run
recursively
#14464
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weihanglo marked this conversation as resolved.
Show resolved
Hide resolved
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason this approach didn't work is pretty much due to #10358. When Cargo computes fingerprint for a
Unit
of work, it asksenv::var
which doesn't containLIBRARY_PATH
orPATH
because that is set by Cargo.rerun-if-env-changed
only captures environment variables set by users via shell likeMY_VAR=1 cargo build
. Variables added by Cargo only available when consulting theCommand
struct of the build script execution viaCommand::get_envs
(like what has done in f91dc78).As a consequence, if you open the fingerprint JSON file of the build script execution (normally at
target/debug/.fingerprint/foo-559e30894cda9925/run-build-script-build-script-build.json
), you'll seewhich shows that Cargo failed to capture the initial library search path set by itself.
There is another way to observe this bug: set the
LEVEL
env var in the test to a higher number like 5. Any subsequent Cargo invocation after the first one should be fresh. Before doing this verification you need to changestd::env!("LEVEL")
tostd::env::var!("LEVEL")
because the former will be captured by rustc dep-info, which trigger a rebuild.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't expect such a difference.
I decide to to get the
"LEVEL"
from the command line argument.