Hack to work around microsoft/vscode#178241

.github/workflows/test.yml

@@ -40,8 +40,10 @@ jobs:
       - run: pnpm --color --filter '!cursorless-org' --filter '!cursorless-org-*' build
       - run: xvfb-run -a pnpm --color test
         if: runner.os == 'Linux'
+      - run: bash scripts/ci-test-windows.sh
+        if: runner.os == 'Windows'
       - run: pnpm --color test
-        if: runner.os != 'Linux'
+        if: runner.os == 'macOS'
       - name: Create vscode dist that can be installed locally
         run: pnpm -F @cursorless/cursorless-vscode populate-dist --local-install
         if: runner.os == 'Linux' && matrix.vscode_version == 'stable'

scripts/ci-test-windows.sh

@@ -0,0 +1,29 @@
+# This script is run by GitHub Actions on Windows
+# We need this script to work around a bug in the Windows GitHub Actions
+# environment where VSCode sometimes becomes unresponsive during the tests.
+# See https://github.com/microsoft/vscode/issues/178241
+set -euo pipefail
+
+test_output_path="test-output.txt"
+
+ret=0
+script --flush --quiet --return "$test_output_path" --command "pnpm --color test" || ret=$?
+
+# If the test failed, but contains the string "CodeWindow: detected unresponsive",
+# then it is https://github.com/microsoft/vscode/issues/178241; try 2 more times
+
+for i in {1..2}; do
+  if [[ $ret -ne 0 ]]; then
+    if grep -q "CodeWindow: detected unresponsive" "$test_output_path"; then
+      echo "Detected unresponsive VSCode window; retrying"
+      script --flush --quiet --return "$test_output_path" --command "pnpm --color test" || ret=$?
+    else
+      break
+    fi
+  fi
+done
+
+if [[ $ret -ne 0 ]]; then
+  echo "Test failed"
+  exit $ret
+fi