Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stryker fails to connect to vstest.console on Linux

See original GitHub issue

Describe the bug When attempting to run Stryker on a .NET 5 app on Ubuntu 20.04, the process hangs and then errors out when trying to initialise test runners. Stryker runs successfully with this app when targeting .NET Core 3.1 on the same machine.

Logs log-20210120.txt

Expected behavior Stryker should successfully initialise the test runners and proceed to run the tests,

Desktop (please complete the following information):

OS: Linux/Ubuntu 20.04
Type of project [core]
Framework Version [net5.0]
Stryker Version [e.g. beta 0.21.0]

Additional context A colleague ran into the same issues when running Stryker on macOS on the same project. I’ll get the OS version details etc… and attach to the issue in due course.

I can run Stryker successfully under the following conditions:

On Windows 10 20H2 using the dotnet tool from the .NET 5 SDK (5.0.102) on this project while it was targeting net5.0
On Ubuntu 20.04 and Windows 20H2 when using the dotnet tool from the .NET Core 3.1 SDK (3.1.405) on this project when I rolled it back to targeting netcoreapp3.1 (no code changes)

Stryker fails to run (with the error above) under the following conditions:

On Ubuntu 20.04 when using the dotnet tool from the .NET 5 SDK (5.0.102) on this project when targeting either net5.0 or netcoreapp3.1

Issue Analytics

State:
Created 3 years ago
Comments:18 (10 by maintainers)

Top GitHub Comments

1reaction

rouke-broersmacommented, Jan 21, 2021

@Damarus999 thank you for the bug report anyways, it is useful information. And I’m glad you got stryker to work.

If you wish we would appreciate if you could create a new issue with details about the syntax we are mutating wrong (if you can provide a reproduction that would be great). I’ll go ahead and close this one. If you run into this kinda issue again in the future feel free to create a new issue or ping me here to reopen this one.

1reaction

rouke-broersmacommented, Jan 21, 2021

The warnings are not a big issue. They simply mean that we introduced illegal syntax while mutating. Stryker automatically removes the illegal syntax so compilation is successful. We only ask users to create an issue for these kinds of problems so that we can improve our mutation engine and not place the illegal syntax in the first place.