-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[WIP] Retry e2e tests on beefier runners 🐄 #31953
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## master #31953 +/- ##
=======================================
Coverage 74.18% 74.19%
=======================================
Files 2905 2905
Lines 103334 103328 -6
Branches 12830 12831 +1
=======================================
- Hits 76663 76660 -3
+ Misses 20862 20857 -5
- Partials 5809 5811 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
b47ddbb
to
7932b6f
Compare
Current Cypress Test Results Summary✅ 69 Passing - ❌ 1 Failing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 06/28/2023 06:41:31pm UTC) Run DetailsRunning Workflow E2E Tests on Github Actions Commit: 78b2fb91713ef88205e29868bd967d68a783f118 Started: 06/28/2023 06:18:14pm UTC ❌ Failures📄 e2e/test/scenarios/models/models.cy.spec.js • 1 FailureTest Case Results
|
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
issue 29951 should allow to run the model query after changing custom columns (#29951)
Retry 3 • Retry 2 • Retry 1 • Initial Attempt |
16% (80)80 / 500 runsfailed over last 7 days |
11.40% (57)57 / 500 runsflaked over last 7 days |
Description
We've been seeing more and more e2e failures caused by things like slow api requests. This detects if an e2e job is a re-run and runs it on a 4vcpu runner.
You can't put conditionals in
runs-on
, so you have to add a separate step and use the output