[Tests] Disable inproc crash reporter for intentional crashing tests

[mdh1418]

The test intentionally expects an unhandled exception to occur. The helix test wrapper enables crash reporting in

runtime/eng/testing/RunnerTemplate.sh

Lines 118 to 119 in d75c1ca

	export DOTNET_DbgEnableMiniDump=1
	export DOTNET_EnableCrashReport=1

, but this test specifically disables DOTNET_DbgEnableMiniDump to disable the only crash reporter at the time, createdump.

With the in-proc crashreporter supported on macOS and Linux, there are now two crash reporting mechanisms, with the in-proc crash reporter being enabled should DOTNET_EnableCrashReport/DOTNET_EnableCrashReportOnly be set while DOTNET_DbgEnableMiniDump is unset. As a result, this test unintentionally began crash reporting after inducing unhandled exception scenarios.

Originally

Test process unhandled.dll with argument main exited
"Unhandled exception. System.Exception: Test"
"   at TestUnhandledException.Program.Main(String[] args)"
Test process exited with expected error code and produced expected output

InProc CrashReporter enabled

Test process unhandled.dll with argument main exited
"Unhandled exception. System.Exception: Test"
"   at TestUnhandledException.Program.Main(String[] args)"
"*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** "
".NET Crash Report v1.0.0"
"Build: 42.42.42.42424 @Commit: c1b4860a92c508c5cd043776fe1362455d2f75d8"
"ABI: arm64"
"Cmdline: corerun"
"pid: 4263"
"signal 6 (SIGABRT)"
""
"--- thread 0x164f8f (crashed) ---"
"  managed exception: System.Exception (0x80131500)"
"  #00 [0] TestUnhandledException.Program.Main + 0x1e (token=0x6000009)"
"  #01 [1] System.Environment.CallEntryPoint + 0x1c (token=0x60004a1)"
""
"--- thread 0x164f95 ---"
"  (no managed frames)"
""
"modules:"
"  [0] unhandled {5818b8c6-ff2f-4925-82a6-4ed6871d1d16}"
"  [1] System.Private.CoreLib {9fdb0c05-8392-43fe-8a44-1df8a41aaf06}"
" *** *** *** *** *** *** *** *** *** *** *** *** *** *** "
""
Test process exited with expected error code and produced expected output

This PR cleans the test output by removing DOTNET_EnableCrashReport, thereby disabling the inproc crash reporter.
It applies the same changes for similarly crash-expecting tests

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

Updates the unhandled-exception test harness to avoid emitting crash-report artifacts/log noise when the child process is expected to terminate abnormally, by explicitly clearing crash-report-related environment variables for the spawned process.

Changes:

• Update the comment to reflect disabling broader crash diagnostics (not just dump generation).
• Remove DOTNET_EnableCrashReport from the child process environment in addition to DOTNET_DbgEnableMiniDump.

[janvorli]

There is actually another test that needs this change:
src/tests/baseservices/exceptions/stackoverflow/stackoverflowtester.cs
It is likely needed for src/tests/baseservices/exceptions/OutOfMemoryException/OutOfMemoryException.cs too.
And it wouldn't hurt to do it for the src/tests/baseservices/exceptions/simple/ParallelCrashTester.cs and

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

[janvorli]

LGTM, thank you for fixing it.