nameresolutionpaltests.trygetaddrinfo_externalhost failing on Android

[runfoapp]

Runfo Tracking Issue: nameresolutionpaltests.trygetaddrinfo_externalhost failing on Android

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
1080402	runtime	PR 50668	net6.0-windows-Debug-x64-CoreCLR_release-(Windows.Nano.1809.Amd64.Open)windows.10.amd64.serverrs5.open@mcr.microsoft.com/dotnet-buildtools/prereqs:nanoserver-1809-helix-amd64-08e8e40-20200107182504
1017675	runtime	Rolling	net6.0-Linux-Release-x64-CoreCLR_checked-(Alpine.312.Amd64.Open)ubuntu.1604.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-20200602002622-e06dc59
971988	runtime	PR 47598	net6.0-Linux-Debug-x64-CoreCLR_release-(Alpine.312.Amd64.Open)ubuntu.1604.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-20200602002622-e06dc59
971988	runtime	PR 47598	net6.0-Linux-Debug-x64-CoreCLR_release-(Alpine.312.Amd64.Open)ubuntu.1604.amd64.open@mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-20200602002622-e06dc59
969479	runtime	Rolling	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
965989	runtime	PR 47339	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
964635	runtime	PR 47417	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
964385	runtime	Rolling	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
963649	runtime	PR 47366	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
963029	runtime	PR 45022	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
960119	runtime	PR 47207	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
959934	runtime	Rolling	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
959894	runtime	PR 47229	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
0	1	1

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runfo Creating Tracking Issue (data being generated)

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-Infrastructure-mono, untriaged
Milestone:	-

[hoyosjs]

Query reports more issues: https://runfo.azurewebsites.net/search/tests/?bq=definition%3Aruntime+started%3A%7E7&tq=name%3ASystem.Net.NameResolution.PalTests.NameResolutionPalTests.TryGetAddrInfo_ExternalHost

[ghost]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runfo Tracking Issue: nameresolutionpaltests.trygetaddrinfo_externalhost failing on Android

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
969479	runtime	Rolling	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
965989	runtime	PR 47339	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
964635	runtime	PR 47417	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py
964385	runtime	Rolling	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log		test results	runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
1	4	4

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-System.Net, blocking-clean-ci, os-android
Milestone:	-

[akoeplinger]

Looks like all of these happened on the device attached to DNCENGWIN-010.

@MattGal this machine is part of the machines to be investigated as part of https://github.com/dotnet/core-eng/issues/11290 so should be disabled, do you know why it was reactivated?

[MattGal]

I actually had forgotten about that issue, I was only aware of the three in https://github.com/dotnet/core-eng/issues/11891 . I'll get it offline now and put a comment on that issue saying I did.

[akoeplinger]

@MattGal thanks but that doesn't explain why that machine was suddenly part of the pool again, it was disabled when that issue was created months ago.

[MattGal]

I'll see if I can find out why

[MattGal]

@ilyas1974 can give us details why he put it online then.

[ilyas1974]

Apologies - my comments from yesterday didn't save. The reason they system was put back online was the issue that was linked in the notes for why was the system was offline was closed.

[akoeplinger]

@ilyas1974 which issue was closed? https://github.com/dotnet/core-eng/issues/11290 is still open and I can't find another issue mentioning the machine :)

[ilyas1974]

I can't seem to find the issue I saw. Either way, it's sounds like it was a mistake for the system to have been put back into rotation. I apologize for any additional work this may have caused.

[akoeplinger]

No worries, I was just wondering if I missed something :)

[akoeplinger]

Closing this issue since the offending machine was disabled and we're tracking the DNS issue with https://github.com/dotnet/core-eng/issues/11290 already.