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
1060474	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116283
1060274	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116166
1058535	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116291
1057857	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116259
1056263	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#114862
1055211	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116152
1054509	dotnet/runtime	System.Runtime.Tests.WorkItemExecution
1054044	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115609
1052729	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#116057
1051621	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115959
1046982	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115583
1041937	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115583
1041064	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115531
1039922	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	#115436

Summary

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

[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?