chore(ci): Do not report flaky test issues if we cannot find a test name#20589
Merged
chore(ci): Do not report flaky test issues if we cannot find a test name#20589
Conversation
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.
chargome
approved these changes
Apr 29, 2026
JPeer264
approved these changes
Apr 29, 2026
Contributor
size-limit report 📦
|
nicohrubec
approved these changes
Apr 29, 2026
47 tasks
This was referenced Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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