From 2f9d7c8f79d9fd924b6bbc8993c9cb23211420c5 Mon Sep 17 00:00:00 2001
From: Ankit Jain <radical@gmail.com>
Date: Sun, 30 Jul 2023 21:57:58 -0400
Subject: [PATCH] [wasm][debugger] Set VSTEST_TESTHOST_SHUTDOWN_TIMEOUT to 2s

The tests have been getting randomly aborted with:
`The active test run was aborted. Reason: Test host process crashed`

This might be due to the shutdown taking too long. The default timeout
is 100ms. Increasing that to 2000ms.

Issue: https://github.com/dotnet/runtime/issues/89409
---
 .../Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj            | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/tests/BuildWasmApps/Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj b/src/tests/BuildWasmApps/Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj
index 19fbd1aa03698d..ea0a203d48ea68 100644
--- a/src/tests/BuildWasmApps/Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj
+++ b/src/tests/BuildWasmApps/Wasm.Debugger.Tests/Wasm.Debugger.Tests.csproj
@@ -35,6 +35,10 @@
     <ItemGroup>
       <RunScriptCommands Condition="'$(OS)' != 'Windows_NT'" Include="export DEBUGGER_TEST_PATH=$PWD/debugger-test" />
       <RunScriptCommands Condition="'$(OS)' == 'Windows_NT'" Include="set DEBUGGER_TEST_PATH=%25cd%25/debugger-test" />
+
+      <!-- See https://github.com/dotnet/runtime/issues/89409 and https://github.com/microsoft/vstest/issues/2952 -->
+      <RunScriptCommands Condition="'$(OS)' != 'Windows_NT'" Include="export VSTEST_TESTHOST_SHUTDOWN_TIMEOUT=2000" />
+      <RunScriptCommands Condition="'$(OS)' == 'Windows_NT'" Include="set VSTEST_TESTHOST_SHUTDOWN_TIMEOUT=2000" />
     </ItemGroup>
 
     <ItemGroup Condition="'$(ContinuousIntegrationBuild)' == 'true' and '$(DebuggerHost)' == 'chrome'">