Microsoft.Extensions.DependencyModel.Tests Work Item Failing on Android

[runfoapp]

Runfo Tracking Issue: Microsoft.Extensions.DependencyModel.Tests Work Item Failing on Android

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
965935	runtime	PR 47390	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log			runclient.py
965281	runtime	PR 47344	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log			runclient.py

Build Result Summary

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

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: @eerhardt
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runfo Tracking Issue: Microsoft.Extensions.DependencyModel.Tests Work Item Failing on Android

Build	Definition	Kind	Run Name	Console	Core Dump	Test Results	Run Client
965935	runtime	PR 47390	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log			runclient.py
965281	runtime	PR 47344	net6.0-Android-Release-arm64-Mono_Release-Windows.10.Amd64.Android.Open	console.log			runclient.py

Build Result Summary

Day Hit Count	Week Hit Count	Month Hit Count
2	2	2

Author:	runfoapp[bot]
Assignees:	-
Labels:	area-DependencyModel, blocking-clean-ci, untriaged
Milestone:	-

[eerhardt]

The exception is coming from the harness:

 System.NullReferenceException: Object reference not set to an instance of an object.
                    at Microsoft.DotNet.XHarness.CLI.Commands.Android.AndroidTestCommand.<>c__DisplayClass17_0.<GetDeviceToUse>b__0(KeyValuePair`2 kvp) in /_/src/Microsoft.DotNet.XHarness.CLI/Commands/Android/AndroidTestCommand.cs:line 259

cc @MattGal @akoeplinger - as it looks like they have touched this file.

[akoeplinger]

Yeah I reported an xharness bug about that one: dotnet/xharness#430

It's not the real issue though, the underlying problem is an infrastructure issue while getting the architecture of the Android device. I don't think it's actionable/specific to Microsoft.Extensions.DependencyModel.Tests.

[eerhardt]

It's not the real issue though, the underlying problem is an infrastructure issue while getting the architecture of the Android device.

Do we have an issue for the underlying problem? Or are we using this issue to track the underlying problem? If we are using this issue, I'll move it to a different area.

[MattGal]

It's not the real issue though, the underlying problem is an infrastructure issue while getting the architecture of the Android device.

Do we have an issue for the underlying problem? Or are we using this issue to track the underlying problem? If we are using this issue, I'll move it to a different area.

Yes, the underlying problem is described in dotnet/xharness#430, and I should have a fix merged that will cause Helix to properly detect and retry this when the Arcade Helix XHarness SDK is used in the next hour.

[directhex]

dotnet/xharness#430 was closed a couple of weeks ago