-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: skip template check for flaky tests issues #23857
ci: skip template check for flaky tests issues #23857
Conversation
Flaky tests issues do not match our issues templates. Their description just includes a link to cricleci.
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #23857 +/- ##
========================================
Coverage 69.02% 69.02%
========================================
Files 1164 1164
Lines 44513 44513
Branches 11890 11890
========================================
Hits 30721 30721
Misses 13792 13792 ☔ View full report in Codecov by Sentry. |
Builds ready [dbf1ffb]
Page Load Metrics (872 ± 517 ms)
Bundle size diffs
|
Test OK with gauthierpetetin-test/repo_test#177 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test OK
// If labelable is a flaky test report, no template is needed (we just add a link to circle.ci in the description), we skip the template checks | ||
const flakyTestsLabelFound = findLabel(labelable, flakyTestsLabel); | ||
if (flakyTestsLabelFound?.id) { | ||
console.log(`Issue ${labelable?.number} was created to report a flaky test. No template is needed in that case: we just add a link to circle.ci in the description. Skip template checks.`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where does the link get added?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You made me realise this sentence wasn't very clear. I updated it in this commit.
The idea is that flaky test issue's description is just a link redirecting to circle.ci which is why we don't expect issue's description to match issue template. Example flaky test issue: #22702
Builds ready [723ca33]
Page Load Metrics (414 ± 382 ms)
Bundle size diffs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test OK !
hi @gauthierpetetin , could you add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you @gauthierpetetin the changes look good to me and the manual testing works as expected 👍
Builds ready [7683d9b]
Page Load Metrics (911 ± 559 ms)
Bundle size diffs
|
Description
flaky tests
, we avoid them being automatically labeled withINVALID-ISSUE-TEMPLATE
.Related issues
Manual testing steps
INVALID-ISSUE-TEMPLATE
flaky tests
labelINVALID-ISSUE-TEMPLATE
label shall automatically be removed from issueScreenshots/Recordings
Pre-merge author checklist
Pre-merge reviewer checklist