Skip to content

Conversation

@Rutherther
Copy link

For me the tests were always being ran when Clicking on "Debug" button on a test in a rust file. I have gone over the logic and I am pretty confident that the condition here is wrong as it seems to me it should append --no-run only if it's not already present. This is to prevent having two --no-run flags that lead to an error error: the argument '--no-run' cannot be used multiple times.

Change the logic of lsp-rust-analyzer-debug to append --no-run when it's not already in cargo-args, not the other way round. The result is used only for obtaining the compiler-artifact, no need to run the tests to obtain it.

@github-actions github-actions bot added rust documentation client One or more of lsp-mode language clients labels Nov 9, 2025
Change the logic of lsp-rust-analyzer-debug to append
--no-run when it's not already in cargo-args, not the
other way round. The result is used only for obtaining
the compiler-artifact, no need to run the tests to
obtain it.
@Rutherther Rutherther force-pushed the fix/lsp-rust-test-no-run branch from 0aa6ede to dbda7ad Compare November 9, 2025 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

client One or more of lsp-mode language clients documentation rust

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants