Skip to content
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

[release/8.0-staging][Android] Failing to install runtime tests on Android x64 emulators #110858

Open
matouskozak opened this issue Dec 20, 2024 · 2 comments
Labels
area-Infrastructure-mono Known Build Error Use this to report build issues in the .NET Helix tab os-android untriaged New issue has not been triaged by the area owner

Comments

@matouskozak
Copy link
Member

matouskozak commented Dec 20, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=897703
Build error leg or test failing: PayloadGroup0

Affected CI: android-x64 Release AllSubsets_Mono_RuntimeTests_Interp monointerpreter and android-x64 Release AllSubsets_Mono_RuntimeTests minijit

Error:

System.AggregateException : One or more errors occurred. (Failed to install mobile app.
      Expected: True
      Actual:   False) (The following constructor parameters did not have matching fixture data: _Global globalVar)
      ---- Failed to install mobile app.
      Expected: True
      Actual:   False
      ---- The following constructor parameters did not have matching fixture data: _Global globalVar
      Stack Trace:
        
        ----- Inner Stack Trace #1 (Xunit.Sdk.TrueException) -----
           at Loader_CustomAttributes._Global..ctor()
           at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
           at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
        ----- Inner Stack Trace #2 (Xunit.Sdk.TestClassException) -----

and the install log:

[22:46:38] info: Will attempt to find device supporting architectures: 'x86_64'
[22:46:38] info: Finding attached devices/emulators...
[22:48:08] warn: No attached devices / emulators detected. Check that any emulators have been started, and attached device(s) are connected via USB, powered-on, unlocked and authorized.
[22:48:08] crit: Failed to find compatible device: x86_64
XHarness exit code: 81 (DEVICE_NOT_FOUND)

Looks like .NET 8 version of xharness is failing to start emulators. fyi: @ivanpovazan

Originally, I thought that it is related to the servicing queue used (ubuntu.2204.amd64.android.29.open.svc), however, the same queue is used for release/9.0-staging and that one works.

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["PayloadGroup0", "8.0.0-prerelease", "Failed to install mobile app"]
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@matouskozak matouskozak added area-Infrastructure-mono Known Build Error Use this to report build issues in the .NET Helix tab os-android labels Dec 20, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Dec 20, 2024
Copy link
Contributor

Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-mono Known Build Error Use this to report build issues in the .NET Helix tab os-android untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant