Closed petertiedemann closed 2 months ago
I've encountered this behaviour as well now. But I've seen it only once so it seems flaky behaviour. Was yours also flaky or did you encounter this on every run?
OS: MacOS Framework Version net6.0 Stryker Version 3.7.1
Not much of substance to add, but I've also encountered this error.
Solution is not that large, ~30 projects. Stryker.Net runs fine on the solution on my developer's machine (win). But in the Azure pipelines it keeps throwing the above mentioned errors on one of the build agents. Yet on another build agent it runs fine, and unfortunately I don't really know how the "bad" agent is different.
@JustineSondore are they the same vm type?
@richardwerkman It always failed for me, but in slightly different ways each time if I recall correctly.
The underlying Buildalyzer have been closed, fix has been delivered and Stryker integrated it. Closing it as fixed
Describe the bug Running stryker against a large sln file ( 278 projects) on a 5950x (16c/32t) CPU leads to multiple "Could not find build environment" errors.
Logs I couldn't figure out how to output the log when running from a configuration file, but a snippet is included here, please see additional context below.
Expected behavior No failures
Desktop (please complete the following information):
Additional context The underlying issue appears to be from Buildalyzer, where I have reported this: https://github.com/daveaglick/Buildalyzer/issues/227
I suspect it could also be worked around from stryker by limiting the concurrency (for example using the value of -c CLI flag here as well)?