Skip to content

Commit 6f048ce

Browse files
committed
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.
1 parent c0005cd commit 6f048ce

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

scripts/report-ci-failures.mjs

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,10 @@ export default async function run({ github, context, core }) {
6868
core.info(`Could not fetch annotations for ${jobName}: ${e.message}`);
6969
}
7070

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
7273
if (testNames.length === 0) {
73-
testNames = ['Unknown test'];
74+
continue;
7475
}
7576

7677
// Create one issue per failing test for proper deduplication

0 commit comments

Comments
 (0)