From 6f048cedd91607e52dc3269cca2d605a435a01d8 Mon Sep 17 00:00:00 2001 From: Francesco Gringl-Novy Date: Wed, 29 Apr 2026 10:52:55 +0200 Subject: [PATCH] chore(ci): Do not report flaky test issues if we cannot find a test name 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. --- scripts/report-ci-failures.mjs | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/scripts/report-ci-failures.mjs b/scripts/report-ci-failures.mjs index 5a05e1144bec..b407eac157c0 100644 --- 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