Local test run fails to analyze HardwareIntrinsics test results #78462
Description
After a local crossgen2 tests run, using .\src\tests\run.cmd checked runcrossgen2tests, I hit
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml
Analyzing C:\dev\dotnet\runtime2\artifacts\log\JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml
Traceback (most recent call last):
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1411, in <module>
sys.exit(main(args))
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1399, in main
parse_test_results(args, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1196, in parse_test_results
parse_test_results_xml_file(args, item, item_name, tests, assemblies)
File "C:\dev\dotnet\runtime2\src\tests\run.py", line 1255, in parse_test_results_xml_file
assert tests[test_name] == None
AssertionError
There is a test named JIT.HardwareIntrinsics.Arm::Abs_Vector128_Double (global::JIT.HardwareIntrinsics.Arm._AdvSimd.Arm64.Program.Abs_Vector128_Double()) in both JIT.HardwareIntrinsics.HardwareIntrinsics_r.testRun.xml and JIT.HardwareIntrinsics.HardwareIntrinsics_ro.testRun.xml which causes the assert.
Does the analysis need to disambiguate by the assembly somehow too?
cc @davidwrighton, presumably related to your recent changes here