[cypress] Treat "Timed out waiting for the browser" as test-independent

Author: ramosbugs

packages/cypress-plugin/test/integration/src/verify-output.ts

@@ -1345,9 +1345,9 @@ export const verifyOutput = (
     ).toStrictEqual(expectedSpecs);
 
     // Make sure there are no unexpected specs.
-    expect(expectedSpecs).toStrictEqual(
+    expect(
       parsedOutput.specOutputs.map((spec) => spec.filename).sort()
-    );
+    ).toStrictEqual(expectedSpecs);
 
     verifySpecOutputs(params, parsedOutput.specOutputs);
   }

packages/cypress-plugin/test/integration/unflakable.js

@@ -9,5 +9,11 @@ module.exports = {
     /attempting to close the browser tab(?:(?!resetting server state).)*$/s,
     /Still waiting to connect to Edge, retrying in 1 second.*(?:Error: Test timed out after|All promises were rejected)/s,
     /There was an error reconnecting to the Chrome DevTools protocol\. Please restart the browser\./,
+    // When this error occurs, Cypress ends up printing the "Running: <spec>" header multiple times,
+    // which the integration test parses as if that spec were in fact invoked multiple times. We
+    // don't want the test itself to ignore multiple spec invocations since that could indicate a
+    // bug. Instead, we treat it as a test independent failure iff this error message is in the
+    // output. Otherwise, we'll still treat it as a true failure.
+    /Timed out waiting for the browser to connect. Retrying\.\.\./,
   ],
 };