chore(ci): Do not report flaky test issues if we cannot find a test name (#20589)

mydea · web-flow · commit c4e3902c9297 · 2026-04-29T11:09:54.000+02:00
Today, we got a bunch of flaky CI issues for e.g. failing cache or playwright installation. While these are also kind of flakes, the issues are not super actionable and it gets a bit noisy. I'd opt to not create an issue if we cannot identify a concrete test that is flaking. We miss out on some things being auto-reported here but that's also OK I'd say. Closes #20319 Closes #20557 Closes #20493 Closes #20492 Closes #20469 Closes #20470
diff --git a/scripts/report-ci-failures.mjs b/scripts/report-ci-failures.mjs
@@ -68,9 +68,10 @@ export default async function run({ github, context, core }) {
       core.info(`Could not fetch annotations for ${jobName}: ${e.message}`);
     }
 
-    // If no test names found, fall back to one issue per job
+    // If no test names found, abort - this could mean something else, e.g. cache restoration or similar fails
+    // and also the issue is not super helpful in this case
     if (testNames.length === 0) {
-      testNames = ['Unknown test'];
+      continue;
     }
 
     // Create one issue per failing test for proper deduplication

Original file line number	Diff line number	Diff line change
`@@ -68,9 +68,10 @@ export default async function run({ github, context, core }) {`
`68`	`68`	core.info(`Could not fetch annotations for ${jobName}: ${e.message}`);
`69`	`69`	`}`
`70`	`70`
`71`		`- // If no test names found, fall back to one issue per job`
	`71`	`+ // If no test names found, abort - this could mean something else, e.g. cache restoration or similar fails`
	`72`	`+ // and also the issue is not super helpful in this case`
`72`	`73`	`if (testNames.length === 0) {`
`73`		`- testNames = ['Unknown test'];`
	`74`	`+ continue;`
`74`	`75`	`}`
`75`	`76`
`76`	`77`	`// Create one issue per failing test for proper deduplication`