aboutsummaryrefslogtreecommitdiff
path: root/crates/syntax/test_data/reparse/fuzz-failures
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-05-14 18:15:21 +0100
committerGitHub <noreply@github.com>2021-05-14 18:15:21 +0100
commite7b8e6fbca483edbf723105c5b7ede94f1caebe8 (patch)
treee5466afadb494c691ebb9b28208b57409ecc4de6 /crates/syntax/test_data/reparse/fuzz-failures
parent6c0f20d79f8e5da57bd907aa1c3324fb92344b9a (diff)
parentc4664609ed0f8b430285de99b4f7a8cc0ae655f5 (diff)
Merge #8819
8819: Use package root as `cargo check` working directory r=matklad a=bcully Cargo commands are affected by the `.cargo/config` files above their working directory. If cargo is invoked from above the directory holding `Cargo.toml`, it may not pick up important settings like registry replacements, causing it to behave differently or even fail. Most cargo invocations are currently setting their working directories to the directory containing `Cargo.toml`, but a couple of paths remain in which cargo is invoked from the default workspace root instead. This change fixes that, resolving some cargo check failures that I experienced in a multi-root workspace in which packages used different registries. Co-authored-by: Brendan Cully <brendan@cully.org>
Diffstat (limited to 'crates/syntax/test_data/reparse/fuzz-failures')
0 files changed, 0 insertions, 0 deletions