Skip to content
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

Running Stryker with the new vitest-runner in parallel results in shared data (and false results) #4214

Closed
nicojs opened this issue May 23, 2023 · 0 comments · Fixed by #4217
Labels
🐛 Bug Something isn't working 🔧 Maintenance Maintenance issue
Milestone

Comments

@nicojs
Copy link
Member

nicojs commented May 23, 2023

Summary

When you run 1 instance of the vitest-runner in multiple projects in parallel, you get interference in the results. For example:

cd e2e
npm run test -- vitest-*

This should be a pretty straightforward fix: use the cwd to communicate. We tried that before, but before we did these changes: #4043 (comment). With these changes: using the cwd would probably work.

@nicojs nicojs added 🐛 Bug Something isn't working 🔧 Maintenance Maintenance issue labels May 23, 2023
@nicojs nicojs added this to the 7.0 milestone May 23, 2023
nicojs added a commit that referenced this issue May 23, 2023
Base the communication directory of the vitest runner on the current working directory (cwd) rather than the than the `node_modules/@stryker-mutator/vitest-runner` directory.

Fixes #4214
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working 🔧 Maintenance Maintenance issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant