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
Root Workspace causes coverage to throw no results error #372
Labels
p5-urgent
Fix build-breaking bugs affecting most users, should be released ASAP (priority)
Comments
This is basically a duplicate of #339, which was closed due to lack of reproduction. |
@ffMathy Sorry about that. I promise I looked, but somehow missed this :( |
Oh, don't apologize! The issue was never solved, and I didn't close it, so it's good to re-open. It was just for some context. |
sheremet-va
added
p5-urgent
Fix build-breaking bugs affecting most users, should be released ASAP (priority)
and removed
pending triage
labels
May 6, 2024
Thank you, I can reproduce it with a |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I've experienced this in our work project but I decided to start fresh and also utilize a sample project to determine if it was just a setup problem I introduced. Upon opening a a PNPM monorepo project with a Vitest workspace defined at the root I am able to see all the tests and run the entire suite, run a single test, and run tests continuously. The issue arises when attempting to leverage the coverage feature. After adding v8 as a dependency and then attempting to run the coverage through the extension, I receive an error regarding VSCode being unable to read
results
ofnull
. After digging in a bit, it seems as though the merge coverage feature isn't receiving any output and its then throwing an error.I did validate that the coverage feature works as intended if the workspace file is deleted.
Reproduction
I was able to repro this behaviour in the current version of
main
in the repo using the following sample: https://github.com/vitest-dev/vscode/tree/main/samples/monorepo-vitest-workspaceOutput
The text was updated successfully, but these errors were encountered: