[CI] Make cypress reporting more resilient (elastic#184397)

## Summary cypress reporter will occasionally get an empty result object - it draws attention from other error messages in the stream, and allows misleading conclusions let's not fail reporting because of that, and hope that the real error will also surface. See: https://buildkite.com/elastic/kibana-pull-request/builds/212655#018fc04b-e385-4760-87db-41b65f86fb40 --------- Co-authored-by: Patryk Kopycinski <[email protected]>
kapral18 · May 29, 2024 · 8bbba60 · 8bbba60
1 parent d39739e
commit 8bbba60
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/x-pack/plugins/security_solution/scripts/run_cypress/parallel.ts b/x-pack/plugins/security_solution/scripts/run_cypress/parallel.ts
@@ -493,10 +493,15 @@ ${JSON.stringify(cyCustomEnv, null, 2)}
               (runResult) => !failedSpecFilePaths.includes(runResult.spec.absolute)
             )
         ),
-        ...retryResults,
+        ..._.filter(retryResults, (retryResult) => !!retryResult),
       ] as CypressCommandLine.CypressRunResult[];
 
-      renderSummaryTable(finalResults);
+      try {
+        renderSummaryTable(finalResults);
+      } catch (e) {
+        log.error('Failed to render summary table');
+        log.error(e);
+      }
 
       const hasFailedTests = (
         runResults: Array<