-
Notifications
You must be signed in to change notification settings - Fork 15
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
Ultest not passing anything as parameters for rust #100
Comments
Please paste the log as described in the issue template. Inside the log you'll also find the commands run for the tests, you may spot the issue there as I've no experience with rust |
The logs are basically this for each test in the file:
I don't know if its relevant but every time I open my project I'm seeing this in the messages:
This happens without executing anything |
Yep that's a problem though it's odd that you can do anything after. You have to run The logs you pasted don't tell me anything useful. I understand there might be sensitive info in them so can you either make a dummy project to run and provide them from that or check them yourself for the command being run, you should see lines beginning with
along with the command being run, cwd and extra env variables |
Yes. I've installed like this:
Also tried running manually. The error still shows in the messages.
I don't see any of this in the logs. |
Very strange, not really sure what the issue is there, could be a race condition related to neovim/pynvim#341
You have to run the tests to see the logs |
If you mean calling |
Can you paste the entire log file for the sample project? |
|
Okay... I could see the command from this log now and it is missing to get the module and test name to pass as parameter. Since it is passing the |
I don't seem to be seeing any issues with rust tests, could you share the sample project you're using? |
same issue |
@y1rn Can you provide a sample project or point to an open source repo which I can use to reproduce locally? |
it works when double check this issue, without change any configuration and plugin update. |
Hi, Here's an example project. |
Ah I see now the issue. This is a vim-test bug, not vim-ultest. If you run |
Closing as the fix has now been merged |
I've just ran
:Ultest
and it marked as running. In the end all were green but i noticed in the float window that it actually didn't test anything:When I run
:TestFile
it runs normally the file.The text was updated successfully, but these errors were encountered: