-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
NameResolutionPalTest failing intermittently on Linux Arm64 #27622
Comments
@karelz broke CI again Can we please make it outer loop or disable for ARM until someone has time to robustify it? |
It doesn't appear to be failing at all in the daily runs, but it is failing regularly on PRs. It's failing ten to fifteen times a day, so we should fix it or move it to outerloop ASAP. |
note that OSX has similar issues. For one, when OS returns EAGAIN do not retry. |
@rmkerr can you please "move it to outerloop ASAP." 😺 |
Yep, I'll do that now. |
* add instrumentation for #32797 * actually retry the lookup * use PlatformID.Unix
@wfurt we re-enabled these tests on ARM in dotnet/corefx#34962, unfortunately this and another failed again there.
same for |
yes, I know. I've been trying to work out with @ulisesh to make some infrastructure changes. I was hoping we can get it done quickly to avoid another disable/enable cycle. |
Is it possible to make them outer loop so they don't break CI jobs? Unless you have a reason for them to be inner loop. You can still request outer loop in CI for testing, of course... |
Changes to container configuration was made. Last failure was at 2019-02-06 04:18:16 (~2days ago) |
After 5 day passes it failed again today for pr/dotnet/corefx/refs/pull/34931/merge Are we sure we updated all machines @ulisesh ? |
Right now, Ubuntu.1604.Arm64.Open doesn't run on containers, it runs on Centriq servers. We will move Ubuntu.1604.Arm64.Open to run on containers early next week |
I did not see failure for almost month after infrastructure changes. Closing for now. |
That's because the test is disabled. |
Seems like test issue, no need to have it in 3.0. cc @wfurt |
https://mc.dot.net/#/user/weshaggard/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/fdfc526a83091617be7978de875969f48d2666bf/workItem/System.Net.NameResolution.Pal.Tests/analysis/xunit/System.Net.NameResolution.PalTests.NameResolutionPalTests~2FTryGetAddrInfo_HostName
https://mc.dot.net/#/user/weshaggard/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/fdfc526a83091617be7978de875969f48d2666bf/workItem/System.Net.NameResolution.Pal.Tests/analysis/xunit/System.Net.NameResolution.PalTests.NameResolutionPalTests~2FTryGetAddrInfo_HostName_TryGetNameInfo
The text was updated successfully, but these errors were encountered: