Assertion failures in merged tests don't get surfaced in AzDO #70306
Description
In this (GCStress) run:
The "coreclr Linux arm Checked gcstress0xc" leg has failures in the merged Methodical tests, with VM asserts. Those tests don't appear in the AzDO UI (as individual tests), linked above.
For example, Methodical_do fails with:
15:21:19.717 Running test: JIT/Methodical/Arrays/lcs/lcsvalbox_do/lcsvalbox_do.cmd
Assert failure(PID 56 [0x00000038], Thread: 68 [0x0044]): !CREATE_CHECK_STRING(pMT && pMT->Validate())
File: /__w/1/s/src/coreclr/vm/object.cpp Line: 522
Image: /root/helix/work/correlation/corerun
[createdump] Gathering state for process 56 corerun
[createdump] Crashing thread 00000044 signal 00000006
[createdump] Writing minidump with heap to file /home/helixbot/dotnetbuild/dumps/coredump.56.dmp
[createdump] Written 122314752 bytes (29862 pages) to core file
[createdump] Dump successfully written
JIT/Methodical/Methodical_do/Methodical_do.sh: line 382: 56 Aborted (core dumped) $LAUNCHER $ExePath "${CLRTestExecutionArguments[@]}"
Expected: 100
Actual: 134
END EXECUTION - FAILED
+ export _commandExitCode=1
but "lcsvalbox_do" doesn't show up on the top-level UI (only "Methodical_do" shows up).
Is that expected?