Closed Christian-Oleson closed 3 months ago
Looks like we were unable to analyze your project for some reason, resulting in a linq exception. We probably use SingleOrDefault somewhere where we did not expect to not get a result.
Looks like we were unable to analyze your project for some reason, resulting in a linq exception. We probably use SingleOrDefault somewhere where we did not expect to not get a result.
Correct. Ideally, if we can get more information to display to the end-user, that will help troubleshoot. I've not gotten to the point yet where I've figured out what is going on. Even verbose logging is lacking in information.
I think I have a fix for this at least: https://github.com/stryker-mutator/stryker-net/pull/2030
The associated fix has been released. Is the problem still present?
The associated fix has been released. Is the problem still present?
Technically, this is due to an issue with Buildalyzer not finding a valid MSBuild version to run mutation testing. So if Buidalyzer is having issues, it will still fail.
This might behave better with recent changes
Describe the bug Styker is failing in a .NET Framework project. I do not have enough information to understand what the issue is nor to troubleshoot. I followed the docs found here:
Logs
Expected behavior A better handled exception so the user can understand what is occurring. I don't know where to start to troubleshoot based off of the message aside from the Stryker code.
Desktop (please complete the following information):
Additional context N/a