Comments (9)
rouge8
commented on June 3, 2024
I'm not sure, sorry, I haven't really thought about it.
from neotest-rust.
jan-xyz
commented on June 3, 2024
Can you maybe help explain a bit how this all connects though? I wasn't sure if it's a problem of the discovery process and that it just doesn't return any positions when given the root or if it's some other problem.
from neotest-rust.
andy-bell101
commented on June 3, 2024
I think this issue is resolved now with the latest commit. I've just tried running the command in my rust project and it seemed to work. Have you tried it in yours?
from neotest-rust.
jan-xyz
commented on June 3, 2024
When I run it on tests in jan-xyz/adventofcode/2021 I get
Run All Tests
command: require("neotest").run.run(vim.fn.getcwd())
output:
neotest-rust: ...pack/packer/start/neotest-rust/lua/neotest-rust/init.lua:129: attempt to concatenate a nil value
Run Nearest Test
command: require("neotest").run.run() on a test
output:
Error executing vim.schedule lua callback: ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...acker/start/plenary.nvim/lua/plenary/context_manager.lua:47: /var/fol
ders/95/81xzw3_50djfylhvphkc2xhw0000gn/T/nvim.jan/xI2Axp/13.junit.xml: No such file or directory
stack traceback:
[C]: in function 'error'
...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:45: in function <...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:44>
Run All Tests in File
command: require("neotest").run.run(vim.fn.expand("%"))
output:
Error executing vim.schedule lua callback: ...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: The coroutine failed with this message: ...acker/start/plenary.nvim/lua/plenary/context_manager.lua:47: /var/fol
ders/95/81xzw3_50djfylhvphkc2xhw0000gn/T/nvim.jan/xI2Axp/10.junit.xml: No such file or directory
stack traceback:
[C]: in function 'error'
...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:18: in function 'callback_or_next'
...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:45: in function <...ck/packer/start/plenary.nvim/lua/plenary/async/async.lua:44>
from neotest-rust.
andy-bell101
commented on June 3, 2024
That folder isn't a cargo project so I'm not surprised it doesn't work. Running it in the subfolders (the cargo projects) works on my machine
from neotest-rust.
jan-xyz
commented on June 3, 2024
hmmm good point, I'm used to be able to run tests from the root of the repository, but true, it's a bit different for that repo.
However, I get the same errors even when I'm in adventofcode/2021/7/ which is a cargo project root.
from neotest-rust.
andy-bell101
commented on June 3, 2024
I've just tried that folder on my machine and it works on my machine. Does cargo nextest run work on your machine?
from neotest-rust.
jan-xyz
commented on June 3, 2024
🙈🙈🙈🙈🙈 whoops. I reinstalled my machine and forgot to install nextest 💩 it works now. Thank you for your patience.
from neotest-rust.
andy-bell101
commented on June 3, 2024
np
from neotest-rust.
Related Issues (20)
- Feature Request: support diagnostic messages HOT 3
- Not works run tests HOT 1
- Support workspaces
- neotest-rust is getting called instead of neotest-python
- Tests with `#[should_panic]` macro are ignored HOT 1
- Error attempt to get length of field 'testsuite' (a nil value) HOT 1
- Unable to parse the test HOT 4
- No Tests found HOT 4
- Tests are not detected if comment exists after #[test] attribute
- Package name should be read from `Cargo.toml` HOT 4
- Failed to run test after recent upgrade. HOT 10
- Running a single test fails HOT 2
- Running/listing tests in a workspace with a root package fails HOT 3
- Running a single test breaks on fish
- Low performance in a large codebase and multi-crate workspace HOT 3
- Test cases from /target folder are extracted unnecessarily HOT 1
- Debug fails because `file_path` is nil HOT 4
- Running file doesn't work HOT 4
- Investigate using Nextest's experimental machine-readable JSON output instead of junit XML
- Feature request: watch support
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from neotest-rust.