runtime: [Mono][Android][x64] JIT.HardwareIntrinsics.X86.*/Jit.Methodical.* tests failed

The JIT.HardwareIntrinsics.X86.*/Jit.Methodical.* tests failed on the Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open CI job (Build)

An error message from the parsed output:

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

Occurrences 5/16-6/16:

Date Run Failures Details
6/16 PM 1829491 142 failures + 64 non-JIT failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
6/15 AM 1825935 ~191 failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
6/13 AM 1820913 ~15 failures
6/12 PM 1820505 ~159 failures
6/12 AM 1820087 ~204 failures
6/11 AM 1819219 ~204 failures
6/7 AM 1810649 ~244 failures
6/6 PM 1809660 ~376 failures
6/5 PM 1808009 ~148 failures
6/5 AM 1807614 ~146 failures
6/4 AM 1806758 ~175 failures
6/3 PM 1805934 ~297 failures
6/1 PM 1801263 ~572 failures
5/31 AM 1797399 ~56 failures
5/29 PM 1795815 ~133 failures
5/27 PM 1793879 4 failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
5/25 PM 1789813 ~108 failures
5/25 AM 1788542 ~368 failures
5/20 PM 1782101 ~236 failures
5/19 PM 1780395 ~78 failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
5/19 AM 1779269 ~54 failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
5/18 PM 1778170 ~113 failures Mono Android x64 Release @ Ubuntu.1804.Amd64.Android.29.Open
5/17 PM 1776043 6 failures
5/16 PM 1774196 ~39 failures
5/16 AM 1772864 ~21 failures

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 22 (22 by maintainers)

Most upvoted comments

As @premun mentioned, the recent spike of Android failures were caused by an infrastructure issue due to recent python upgrade, which was fixed by https://github.com/dotnet/arcade/pull/9663. It should go away as the change being merged into dotnet/runtime.

We had a look at this with @fanyang-mono yesterday and:

  • One fix is waiting for 4 days here https://github.com/dotnet/runtime/pull/70662 - this should bring retries back as there was a regression with older python version
  • One fix will happen on the side of the CoreCLR to improve the logs to make it more clear what’s actually going on

Can we do something about this? Perhaps even disable the entire test suite until we understand more?

@fanyang-mono I’ll defer to you here.