-
Notifications
You must be signed in to change notification settings - Fork 8.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
chore: Reducing E2E test sharding #15192
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Ignored Deployments
|
Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link. |
Current Playwright Test Results Summary✅ 324 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 05/27/2024 01:23:03am UTC) Run DetailsRunning Workflow All checks on Github Actions Commit: 1e600be Started: 05/27/2024 01:20:30am UTC
|
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
hash my url generate url hash
Retry 1 • Initial Attempt |
3.55% (6)6 / 169 runsfailed over last 7 days |
26.04% (44)44 / 169 runsflaked over last 7 days |
📄 apps/web/playwright/event-types.e2e.ts • 1 Flake
Test Case Results
Test Case | Last 7 days Failures | Last 7 days Flakes |
---|---|---|
Event Types tests -- future user Different Locations Tests can select 'display on booking page' option when multiple organizer input type are present
Retry 1 • Initial Attempt |
0% (0)0 / 174 runsfailed over last 7 days |
9.20% (16)16 / 174 runsflaked over last 7 days |
@@ -195,7 +195,11 @@ function getThemeProviderProps(props: { | |||
|
|||
const isBookingPageThemeSupportRequired = themeSupport === ThemeSupport.Booking; | |||
|
|||
if ((isBookingPageThemeSupportRequired || props.isEmbedMode) && !props.themeBasis) { | |||
if ( | |||
!process.env.NEXT_PUBLIC_IS_E2E && |
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.
This gets rid of hundreds of instances of this message when the E2E suite runs.
@@ -215,7 +215,7 @@ function getThemeProviderProps({ | |||
const isBookingPageThemeSupportRequired = themeSupport === ThemeSupport.Booking; | |||
const themeBasis = props.themeBasis; | |||
|
|||
if ((isBookingPageThemeSupportRequired || isEmbedMode) && !themeBasis) { | |||
if (!process.env.NEXT_PUBLIC_IS_E2E && (isBookingPageThemeSupportRequired || isEmbedMode) && !themeBasis) { |
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.
This gets rid of hundreds of instances of this message when the E2E suite runs.
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.
🚀
* chore: Removing E2E test sharding * Added back 4 shards for main E2E * Bump build machines to use 8vCPUs * Downgrading builds to 2 vCPUs to see time difference * Reduced shards to 2 to see if flakes are reduced * Increased E2E vCPUs * Put builds back to 4 vCPUs since they need it * Updated E2E suite to use 16 vCPUs and no sharding * Not running in parallel just to test * Put back the parallelism * Get rid of themeBasis warning in test suite * Skipping another flaky test * 2 shards * Update e2e.yml
What does this PR do?
Removes unnecessary sharding for the smaller E2E test suites. It seems that sharding and parallelism is adding to the flaky problem. Also, having those jobs sharded does nothing for the speed of the test suite.
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?