-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Failing tests in the Mono leg doesn't fail the CI #79579
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: @dotnet/runtime-infrastructure Issue DetailsThis leg looks all nice and green: But if you actually drill into the Helix console logs of one of the tests: There is a failure. I'm disabling this particular test in #79578 so this is not going to repro soon.
|
Weird, the test is being flagged as a failure in the "Tests" tab. Wonder why it's showing green? |
Raised this on FR |
Tagging subscribers to this area: @directhex Issue DetailsThis leg looks all nice and green: But if you actually drill into the Helix console logs of one of the tests: There is a failure. I'm disabling this particular test in #79578 so this is not going to repro soon.
|
This leg looks all nice and green:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=109093&view=logs&jobId=f50bdeb8-70f9-5fe0-0c12-4bd43ab59b51&j=55625a83-07ac-525a-fb32-9d705da79581&t=ed547991-520a-5120-9a9a-8b7bdbddb033
But if you actually drill into the Helix console logs of one of the tests:
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-79523-merge-afc22ef01dc2486a9f/System.IO.Pipes.Tests/1/console.ad2ab646.log?helixlogtype=result
There is a failure.
I'm disabling this particular test in #79578 so this is not going to repro soon.
The text was updated successfully, but these errors were encountered: