Add USan+ASan and UBSan+TSan tests to shadow-memory lit parallelism group.

[delcypher]

Summary

Previously we were running these tests without the "shadow-memory"
lit parallelism group even though we run the ASan and TSan tests in
this group to avoid problems with many processes using shadow memory
in parallel.

On my local machine the UBSan+TSan tests would previously timeout
if I set a 30 second per test limit. With this change I no longer
see individual test timeouts.

This change was made in response to the greendragon build bot reporting
individual test timeouts for these tests. Given that the UBSan+ASan and
UBSan+TSan tests did not have a parallelism group previously it's likely
that some other change has caused the performance degradation. However
I haven't been able to track down the cause so until we do, this change
seems reasonable and is in line with what we already do with ASan and
TSan tests.

rdar://problem/51754620

[yln]

LGTM with 1 nit.
Thanks! I thought I also did this for UBSan+xxx, but apparently I forgot.

compiler-rt/test/ubsan/lit.common.cfg

78 ↗

(On Diff #206549)

if ubsan_lit_test_mode in ['AddressSanitizer', 'MemorySanitizer', 'ThreadSanitizer']:

[delcypher]

compiler-rt/test/ubsan/lit.common.cfg

78 ↗

(On Diff #206549)

Oops I missed this. I'll do this as a follow up commit.

[delcypher]

compiler-rt/test/ubsan/lit.common.cfg

78 ↗

(On Diff #206549)

@yln Landed a follow up fix in r364369.

compiler-rt/trunk/test/ubsan/lit.common.cfg

 
 # Check that the host supports UndefinedBehaviorSanitizer tests
 if config.host_os not in ['Linux', 'Darwin', 'FreeBSD', 'Windows', 'NetBSD', 'SunOS', 'OpenBSD']:
   config.unsupported = True
 
 config.available_features.add('arch=' + config.target_arch)
 
 config.excludes = ['Inputs']
+
+if "ubsan-asan" in config.available_features or "ubsan-tsan" in config.available_features:
+  if not config.parallelism_group:
+    config.parallelism_group = 'shadow-memory'