Skip to content

Run test / debug cannot find Cargo.toml VSCode #13434

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

Closed
Sytten opened this issue Oct 18, 2022 · 2 comments · Fixed by #13447
Closed

Run test / debug cannot find Cargo.toml VSCode #13434

Sytten opened this issue Oct 18, 2022 · 2 comments · Fixed by #13447
Assignees

Comments

@Sytten
Copy link

Sytten commented Oct 18, 2022

The VSCode Run test button is broken with the following error:

error: could not find `Cargo.toml` in `/` or any parent directory

 *  The terminal process "cargo 'test', '--', 'dashboard_tests::sometest', '--exact', '--nocapture'" failed to launch (exit code: 101). 
 *  Terminal will be reused by tasks, press any key to close it.

This is in workspace environment. It's working on v0.4.1247.

rust-analyzer version: v0.4.1249

rustc version: rustc 1.61.0 (fe5b13d68 2022-05-18)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTUP_HOME or CARGO_HOME)

@Geobert
Copy link
Contributor

Geobert commented Oct 20, 2022

I have this as well using v0.4.1252

@Veykril
Copy link
Member

Veykril commented Oct 20, 2022

I believe #13428 broke this, I'll look into it.

@Veykril Veykril self-assigned this Oct 20, 2022
bors added a commit that referenced this issue Oct 20, 2022
fix: Fix DidSaveDocument requests blocking the server on startup

Follow up to #13428
Fixes #13434
bors added a commit that referenced this issue Oct 20, 2022
fix: Fix DidSaveDocument requests blocking the server on startup

Follow up to #13428
Fixes #13434
@bors bors closed this as completed in 2481721 Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants