Skip to content
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

Test explorer randomly switches between Cargo workspaces when there's more than one #16875

Closed
svix-jplatte opened this issue Mar 18, 2024 · 1 comment · Fixed by #17056
Closed
Labels
A-test-explorer Issues related to the test explorer lsp extension and vscode test api C-bug Category: bug

Comments

@svix-jplatte
Copy link

svix-jplatte commented Mar 18, 2024

When I use the new test explorer in a repo that has multiple Cargo workspaces, it seems to fight with itself over which workspace to list tests from. Also attempting to run any of the tests fails because it seems to try to run it from the repo root, instead of from the Cargo workspace root or package directory.

rust-analyzer version: 0.4.1884-standalone (b6d1887bc 2024-03-17)
rustc version: 1.76.0 (07dca489a 2024-02-04)
relevant settings: "rust-analyzer.testExplorer": true
repository link: https://github.com/svix/svix-webhooks

@svix-jplatte svix-jplatte added the C-bug Category: bug label Mar 18, 2024
@HKalbasi HKalbasi added the A-test-explorer Issues related to the test explorer lsp extension and vscode test api label Mar 18, 2024
@svix-jplatte
Copy link
Author

It seems like the first issue mentioned in the title is fixed, I now see tests from all workspaces listed. However, running them still fails with error: could not find `Cargo.toml` in `<repository root>` or any parent directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-test-explorer Issues related to the test explorer lsp extension and vscode test api C-bug Category: bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants