You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the issue I posted in neotest-rust . I am not fully sure whether this is a neotest-rust problem or a general neotest problem, but others have had this issue as well.
If I open neovim inside a Rust workspace folder, everything works as expected. However, when I open neovim in a subfolder of that workspace and try to run tests or open the test tree with neotest, neovim crashes. Is this a known issue? I have had trouble to trace this to a single function, I tried reading the crash dumps of neovim, but it does not contain any useful information.
This only occurs on Ubuntu and not on MacOS which makes this issue even more weird.
robamu
changed the title
Possible crash when using neotest with Rust inside a workspace
Crash possibly related to neotest when using it with Rust inside a workspace
Feb 28, 2024
See the issue I posted in neotest-rust . I am not fully sure whether this is a neotest-rust problem or a general neotest problem, but others have had this issue as well.
If I open neovim inside a Rust workspace folder, everything works as expected. However, when I open neovim in a subfolder of that workspace and try to run tests or open the test tree with neotest, neovim crashes. Is this a known issue? I have had trouble to trace this to a single function, I tried reading the crash dumps of neovim, but it does not contain any useful information.
This only occurs on Ubuntu and not on MacOS which makes this issue even more weird.
The error can be reproduced by installing
neotest
andneotest-rust
, opening neovim inside https://github.com/rouge8/neotest-rust/tree/main/tests/data/workspace/with_integration_tests and then either running any test inside that folder or simply opening the summary window. When opening neovim inside the workspace root itself, everything works without any issues.The text was updated successfully, but these errors were encountered: