Handle process not found error in e2e tests (#2154)

Author: Kamil Sobol

.changeset/polite-bats-wait.md

@@ -0,0 +1,2 @@
+---
+---

packages/integration-tests/src/process-controller/execa_process_killer.ts

@@ -14,8 +14,18 @@ export const killExecaProcess = async (processInstance: ExecaChildProcess) => {
     // turns out killing child process on Windows is a huge PITA
     // https://stackoverflow.com/questions/23706055/why-can-i-not-kill-my-child-process-in-nodejs-on-windows
     // https://github.com/sindresorhus/execa#killsignal-options
-    // eslint-disable-next-line spellcheck/spell-checker
-    await execa('taskkill', ['/pid', `${processInstance.pid}`, '/f', '/t']);
+    try {
+      // eslint-disable-next-line spellcheck/spell-checker
+      await execa('taskkill', ['/pid', `${processInstance.pid}`, '/f', '/t']);
+    } catch (e) {
+      // if process doesn't exist it means that it managed to exit gracefully by now.
+      // so don't fail in that case.
+      const isProcessNotFoundError =
+        e instanceof Error && e.message.includes('not found');
+      if (!isProcessNotFoundError) {
+        throw e;
+      }
+    }
   } else {
     processInstance.kill('SIGINT');
   }