-
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
DnsGetHostEntry_LocalHost_ReturnsFqdnAndLoopbackIPs failed in CI #34317
Comments
This is now regularly blocking CI @karelz Builds
Configurations
Helix Logs
|
@MihaZupan can you please take a look at this new failure? |
Builds
Configurations
Helix Logs
|
This is causing roughly a 3% failure rate at this point. Do we have an ETA for when this will be disabled? |
Sorry for that, I thought @MihaZupan had chance to do it over night. |
From console logs here I am seeing the following tests failing
Which looks like the 4 mentioned in #1488 + now |
This may be misconfigured machine. Also SLES12 uses systemd and that resolver can synthesize response. I think we should collect more system info on failure. If we have helper diag functions, that may be helpful for other DNS test failures. |
@wfurt I think you are right because the test always fails when it's run on an sles.12.amd64.open agent with machine name 'localhost' which looks weird. |
The failures were caused by a Helix infra issue which was resolved yesterday. |
@alnikola did we re-enable the tests? |
Reopening to re-enable the tests ... runtime/src/libraries/System.Net.NameResolution/tests/FunctionalTests/GetHostEntryTest.cs Line 189 in d818d33
|
What Helix issue was this? I'm looking for an issue in core-eng or arcade to link to. If they didn't create on for this problem we should push them to do so. Issues are the primary way we track reliability between our services. If there is a bug in Helix, Azure, etc ... that impacted our reliability we should push to make sure that there is an issue tracking that. Always feel free to include me in the convo to help with this if needed. |
The issue was closed without enabling the affected test by mistake. Will do it shortly. |
Test is enabled because the failures were caused by Helix infra issue (a misconfigured agent) which was fixed a couple of days ago. Fixes #34317
Where is the Helix issue that describes the bug that they fixed? That is what I'm interested in. If they're not filing bugs then it's issues we're not tracking. That means we can't track improvements. |
@jaredpar I reported the issue with a strange agent name ('localhost') to the engineering services team and they said it's a known issue which has been already fixed. So, I don't have a link. Will ping you offline for the details. |
Console Log Summary
Builds
Configurations
Helix Logs
Only seen one failure so far but also suspicious that this showed up in CI
The text was updated successfully, but these errors were encountered: