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

Stryker hangs when using the multi test project feature #1136

Closed
richardwerkman opened this issue Jul 9, 2020 · 6 comments
Closed

Stryker hangs when using the multi test project feature #1136

richardwerkman opened this issue Jul 9, 2020 · 6 comments
Assignees
Labels
🐛 Bug Something isn't working

Comments

@richardwerkman
Copy link
Member

Describe the bug
When using stryker with 2 or more testprojects the run seems to stop (without exiting) during the testing mutant phase.

Logs
Will add soon

Expected behavior
The run should continue without any interuption.

Desktop (please complete the following information):

  • OS: Windows
  • Type of project: Core
  • Framework Version Core 2.1
  • Stryker Version 0.18

Additional context
The problem does not always occur, so this could prove hard to debug

@richardwerkman richardwerkman added the 🐛 Bug Something isn't working label Jul 9, 2020
@richardwerkman
Copy link
Member Author

After further investigation it looks like the vstest runners crash one by one. After the last one has crashed stryker keeps waiting forever.

It's not clear why the vstest runners crash. The last output in the logs contain:

2020-07-09T21:06:07.0150805+02:00  [DBG] Runner 1: Each mutant's fate has been established, we can stop. (b49f87dc)
2020-07-09T21:06:07.0373632+02:00  [VRB] Runner 1: [Error] Cancelling the operation as requested. (3478123c)
2020-07-09T21:06:07.0374326+02:00  [VRB] Runner 1: [Error] Cancelling the operation as requested. (3478123c)

This is the same for each runner.

@ohoward2001
Copy link

Any update on when this issue might be sorted? Thanks

@richardwerkman
Copy link
Member Author

I'm sorry I don't know. This is not in our hands. We addressed this issue @ vstest almost two years ago. Currently a fix is ready to be merged but I'm not in the position to know when this release will take place. I hope soon. Once vstest releases the fix we will update stryker immediately

@psfinaki
Copy link
Contributor

Small insider update: this is hoped to be deliver along with VS2022 17.2. When is that - I don't know :D But now it's 17.0.5 so maybe not so long from now.

@rouke-broersma
Copy link
Member

That's awesome :) Hopefully by then we can update since we're currently blocked on #1870 due to microsoft/vstest#3144 :D

@dupdob
Copy link
Member

dupdob commented Apr 21, 2022

I think this is worth retrying with V 1.51, or the release after that one.
I assumed the problem is fixed

@dupdob dupdob closed this as completed Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants