-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
System.Net.NameResolution.Tests.GetHostAddressesTest_Cancellation.DnsGetHostAddresses_PostCancelledToken_Throws failing in CI #78909
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFailure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=94183&view=ms.vss-test-web.build-test-results-tab This has failed before: #69993. Back then it was disabled in jitstress (in #70089), but note that no stress modes are set in the scenario that failed.
|
There's 2 failures in innerloop within the past 3 weeks: https://runfo.azurewebsites.net/search/timelines/?q=started%3A%7E21+definition%3Aruntime+message%3ADnsGetHostAddresses_PostCancelledToken_Throws 8 failures if you include libraries-jitstress, most often under tailcallstress: https://runfo.azurewebsites.net/search/timelines/?q=started%3A%7E21+message%3ADnsGetHostAddresses_PostCancelledToken_Throws |
@rzikm @wfurt @antonfirsov If the flakiness cannot be fixed, can we add some kind of retry mechanism in the test, so that we only fail if e.g. 5/5 tries fail? |
There is global retry mechanism for all networking tests, the CI fails the test if it fails 3 times in a row. |
We should kick it to |
Triage: All tests touching external host should be moved to outerloop. We should have a look in 8.0 timeframe |
I'm seeing this test fail in 6.0. @antonfirsov can you please disable the test in the servicing branches? Unfortunately the original issue has very old links which are already gone, so I can't tell for sure if the failure was the same. The failure I am seeing in 6.0 is weird, because only the build output shows up, but is no test result link being generated.
|
Failure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=94183&view=ms.vss-test-web.build-test-results-tab
Console log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-78879-merge-4f7487e318c446cc92/System.Net.NameResolution.Functional.Tests/3/console.b90e962b.log?helixlogtype=result
This has failed before: #69993. Back then it was disabled in jitstress (in #70089), but note that no stress modes are set in the scenario that failed.
The text was updated successfully, but these errors were encountered: