Closed feuerschatten closed 2 weeks ago
A project analysis failed, and as it was a Net framework project, Stryker tried a Nuget restore before another attempt. Which repeatedly failed (3 times), leading to an early termination from Stryker.
The nuget restore
operation should have succeeded. It failed either because Stryker (1) failed to set it up properly or (2), because nuget
installation is somehow corrupted.
Successful logs (shared via Stryker's slack) showed that earlier Stryker versions made no nuget
restore attempts.
Stryker V4.1 introduced an improved project analysis logic which increased the overall reliability of projects analysis. One of the changes is that Stryker do a nuget restore
when an analysis failed.
Since there have been no significant change in how this is requested (by Stryker), one can assume earlier Stryker version would face the same error when trying a nuget restore
.
nuget restore
which does not properly handle situation where several SDK's are installed.--dev-mode
option would provide a detailed log of the failure1) in the short term, there is no clear workaround. The best way to address this locally would be to see why project analysis failed (via --dev-mode
option) and try to fix it.
2) nuget
discovery and use logic needs to be improved and secured
I opened a PR (#3072) that will fix this: it will use a retry logic if the first nuget restore attempt fails, and will not consider nuget failure as fatal. Note that you may still have missing results afterward if the nuget restore step was mandatory to successfully build on or more projects.
Describe the bug
we´ve updated our stryker vorm V4.06 to V4.3.0 but now I get the following error while mutating a project. We are using .net-framework 4.6.1. so far I can tell msbuild version 15 is installed. Could you please review the error and lead to a solution?
Logs
Expected behavior The new version should work like the previouse.
Desktop (please complete the following information):