-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test on Mono are failing on lots of PRs with fail fasts #49569
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @CoffeeFlux Issue DetailsHere's a PR that makes no changes:
|
This predates #47333 by a few hours so it's not that, but I don't see anything else in the past couple of days that seems like a good candidate? Weird... cc: @lambdageek |
@CoffeeFlux I think it's quite likely that #47333 triggered this as it happens on Windows only in multi -threaded environment. As that's not the configuration we care a lot about at this point we could move it to staging until the issue is resolved |
Moving Windows to staging temporarily seems reasonable. The timeline doesn't add up for #47333 - this issue was opened a few hours before you merged that PR. I would not assume it's the root cause here. |
I'm seeing this everywhere—we really need to get this moved to staging asap or disable a huge portion of test suites. |
@directhex Please skip the failing test suites and move the pipeline to staging. |
Here's a PR that makes no changes:
https://dev.azure.com/dnceng/public/_build/results?buildId=1037402&view=ms.vss-test-web.build-test-results-tab&runId=32167204&paneView=debug
e.g.
The text was updated successfully, but these errors were encountered: