-
Notifications
You must be signed in to change notification settings - Fork 1.8k
VSCode Test Explorer regularly requires a full rebuild #17149
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
Comments
The json output format of cargo test is unstable, so we use |
As a brand-new Rust / VS Code user, I am also affected by this painful issue. My
I don't know if this is the optimal configuration, but it definitely helps. I also set the I really don't have other interest in using nightly features, and don't want to accidentally start using them in my code, so hopefully this extension will soon be able to avoid the use of this environment variable. The status quo is not the best out-of-box experience. |
The tracking issue for stablizing it in compiler is rust-lang/testing-devex-team#1 Note that you won't accidentally use unstable features since they are gated behind #[feature] or --Zunstable, though your dependencies can intentionally use unstable features without you being noticed. |
+1 - this basically makes the test explorer unusable by default on medium - large projects. Until I found the RUSTC_BOOTSTRAP workaround I had to do a full rebuild every time I rebooted my machine. |
workaround to reduce cli full rebuild / conflict with rust-analyzer (see [VSCode Test Explorer regularly requires a full rebuild · Issue #17149 · rust-lang/rust-analyzer](rust-lang/rust-analyzer#17149))
workaround to reduce cli full rebuild / conflict with rust-analyzer (see [VSCode Test Explorer regularly requires a full rebuild · Issue #17149 · rust-lang/rust-analyzer](rust-lang/rust-analyzer#17149))
workaround to reduce cli full rebuild / conflict with rust-analyzer (see [VSCode Test Explorer regularly requires a full rebuild · Issue #17149 · rust-lang/rust-analyzer](rust-lang/rust-analyzer#17149))
Uh oh!
There was an error while loading. Please reload this page.
rust-analyzer version: rust-analyzer version: 0.3.1932-standalone (47a901b 2024-04-21)
rustc version: 1.77.2
editor or extension: VSCode Insiders with RA 0.3.1932
It's pretty common for running tests via the Test Explorer to require a full rebuild of all dependencies. Seems like build results are getting trampled and lost when check runs. That is, the common
test - fix/save file - test - fix/save file
loop seems to require a rebuild of everything at every step.Seems to happen regardless of
rust-analyzer.cargo.targetDir
being set to true or not. However,"rust-analyzer.check.extraArgs": ["--target-dir", "rust-analyzer-check"]
seems to mitigate it, but runningcargo test
from the CLI requires and forces a full rebuild.The text was updated successfully, but these errors were encountered: