System.Runtime.Tests.WorkItemExecution "crash" on tvOS

[CarnaViire]

The whole Helix WorkItem shows as "crashed", but there's actually just a failed test (System.Tests.DecimalTests+BigIntegerAdd.Test) which is already tracked in #106256. It is impossible to see which test is failing in the available CI logs though, I can only see that in Test Results page in AzDO.

The actual Known Issue is properly linked to the PR, but the Build Analysis is red, as the "crash" is considered to be a separate issue. cc @JulieLeeMSFT FYI

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=773271
Build error leg or test failing: System.Runtime.Tests.WorkItemExecution
Pull request: #106269

Error Message

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

{
  "ErrorMessage": ["--target tvos-device", "System.Runtime.Tests", "XHarness exit code: 1 (TESTS_FAILED)"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=773271
Error message validated: [--target tvos-device System.Runtime.Tests XHarness exit code: 1 (TESTS_FAILED)]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/13/2024 12:41:45 PM UTC

Report

Build	Definition	Test	Pull Request
1026152	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115009
1025849	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114148
1024667	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114972
1023896	dotnet/runtime	System.Runtime.Tests.WorkItemExecution
1021098	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#100729
1019446	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114776
1018393	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114060
1017283	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114644
1017008	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114644
1016506	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114644
1015909	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114644
1014775	dotnet/runtime	System.Runtime.Tests.WorkItemExecution
1014535	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#113306
1013754	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114163
1011122	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114194
1009484	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114387
1008792	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114137
1007936	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114148
1007460	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#111791
1005854	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114194
1005698	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#100729
1004520	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114164
1004490	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114080
1004288	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114173
1000226	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114086

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	4	25

[dotnet-policy-service]

Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @ivanpovazan, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

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

[dotnet-policy-service]

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

[matouskozak]

The failing test can be found thru the net.dot... log file in the artifacts tab like this @CarnaViire:

I don't understand why it required this PR to get the BuildAnalysis to green because the PR got correctly matched to the original tracking issue #106256

My guess is that it considered the System.Tests.DecimalTests+BigIntegerAdd.Test as a separate test from the System.Runtime.Tests even though the BigInteger is a part of the System.Runtime.Tests suit. @missymessa do you know if this is expected behavior of BA?