Skip to content
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

Merged
merged 6 commits into from
May 24, 2024

Conversation

gauthierpetetin
Copy link
Contributor

@gauthierpetetin gauthierpetetin commented Apr 4, 2024

Description

Related issues

  • Fixes: None

Manual testing steps

  1. Go to this test repo which inlcudes the same changes as this PR
  2. Create a new issue with empty description
  3. Wait for 30s until the template check Github action is executed
  4. Issue shall automatically labeled with INVALID-ISSUE-TEMPLATE
  5. Label the issue with flaky tests label
  6. Edit the issue's description (for example by adding a random character in it), to re-trigger the template check Github action
  7. Wait for 30s until the template check Github action is executed
  8. INVALID-ISSUE-TEMPLATE label shall automatically be removed from issue

Screenshots/Recordings

  • None

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • I've completed the PR template to the best of my ability
  • I’ve included tests if applicable
  • I’ve documented my code using JSDoc format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Flaky tests issues do not match our issues templates. Their description just includes a link to cricleci.
Copy link
Contributor

github-actions bot commented Apr 4, 2024

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.

@metamaskbot metamaskbot added the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label Apr 4, 2024
Copy link

codecov bot commented Apr 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.02%. Comparing base (9e21127) to head (dbf1ffb).
Report is 143 commits behind head on develop.

❗ Current head dbf1ffb differs from pull request most recent head 723ca33. Consider uploading reports for the commit 723ca33 to get more accurate results

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.
📢 Have feedback on the report? Share it here.

@metamaskbot
Copy link
Collaborator

Builds ready [dbf1ffb]
Page Load Metrics (872 ± 517 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint713871407838
domContentLoaded105827157
load5627428721077517
domInteractive105827157
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@chloeYue
Copy link
Contributor

Test OK with gauthierpetetin-test/repo_test#177

chloeYue
chloeYue previously approved these changes Apr 17, 2024
Copy link
Contributor

@chloeYue chloeYue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test OK

@davidmurdoch davidmurdoch changed the title Fix/flaky tests issues template skip ci: skip template check for flaky tests issues Apr 17, 2024
// 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.`);
Copy link
Contributor

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?

Copy link
Contributor Author

@gauthierpetetin gauthierpetetin Apr 17, 2024

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

@metamaskbot
Copy link
Collaborator

Builds ready [723ca33]
Page Load Metrics (414 ± 382 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint723901086732
domContentLoaded105222105
load592423414796382
domInteractive105222105
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

Copy link
Contributor

@chloeYue chloeYue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test OK !

@seaona
Copy link
Contributor

seaona commented May 24, 2024

hi @gauthierpetetin , could you add the flaky-tests label to this issue?
This will help me finishing with the testing flow of the PR 🙇‍♀️ thank you v much!!

gauthierpetetin-test/repo_test#178

Copy link
Contributor

@seaona seaona left a 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 👍

gauthierpetetin-test/repo_test#178

@metamaskbot
Copy link
Collaborator

Builds ready [7683d9b]
Page Load Metrics (911 ± 559 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint6114186209
domContentLoaded9421584
load5029799111165559
domInteractive9421584
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 0 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@gauthierpetetin gauthierpetetin merged commit 9b06ab4 into develop May 24, 2024
71 of 72 checks passed
@gauthierpetetin gauthierpetetin deleted the fix/flaky-tests-issues-template-skip branch May 24, 2024 13:55
@github-actions github-actions bot locked and limited conversation to collaborators May 24, 2024
@github-actions github-actions bot removed the needs-dev-review PR needs reviews from other engineers (in order to receive required approvals) label May 24, 2024
@gauthierpetetin gauthierpetetin added the release-12.0.0 Issue or pull request that will be included in release 12.0.0 label Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-12.0.0 Issue or pull request that will be included in release 12.0.0 team-extension-platform
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants