Disable tests on Debug CoreClr that are already disabled on Checked CoreClr

[danmoseley]

A number of tests are disabled for Checked runtime. I assume these intended to also disable for Debug runtime, which is even slower.

Also increased timeout when not on a release runtime for some Process tests that are timing out on a debug runtime.

[ghost]

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

Issue Details

---

A number of tests are disabled for Checked runtime. I assume these intended to also disable for Debug runtime, which is even slower.

Author:	danmoseley
Assignees:	-
Labels:	area-Meta
Milestone:	-

[jkotas]

a debug runtime.

The debug runtime is super slow. We never run tests on it.

If we want to be hardening the tests for super slow modes of execution (GCStress is another example of that), we should introduce a concept timeout multiplier and apply it to all hardcoded timeouts.

[jkotas]

Is this intentional change? Looks like it is causing the test failures.

[danmoseley]

Downloading 'https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh'
2022-02-11T16:35:37.2873610Z curl: (6) Couldn't resolve host 'dotnet.microsoft.com'
2022-02-11T16:35:37.2883817Z Curl failed; dumping some information about dotnet.microsoft.com for later investigation
2022-02-11T16:35:57.3091275Z 140549514965440:error:2008F002:BIO routines:BIO_lookup_ex:system lib:../crypto/bio/b_addr.c:704:Temporary failure in name resolution
2022-02-11T16:35:57.3093479Z connect:errno=11
2022-02-11T16:35:57.3310648Z ##[error]Bash exited with code '1'.

@dotnet/dnceng do you know who might want the tracing info above?

[danmoseley]

Oh never mind - probably this is from curl itself

[danmoseley]

Build failure is not connecting to microsoft.com. Happened twice -- negligible risk merging given all other builds passed