-
Notifications
You must be signed in to change notification settings - Fork 9.3k
chore: workflow to check for flaky e2e changes #20435
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
base: main
Are you sure you want to change the base?
Conversation
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (03/28/25)1 reviewer was added to this PR based on Keith Williams's automation. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
How does this differ from the HTML reports we already generate? |
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.
I'm not a fan of dedicating workflow jsut to detect flakyness. I would rather incorportae this into our actual testing runs and maybe ping on slack if a flakyness is detected.
This PR is being marked as stale due to inactivity. |
What does this PR do?
Added a new workflow to check for flaky e2e changes inside a PR
This pull request introduces a new workflow to detect and report flaky end-to-end (E2E) tests. The most important changes include the creation of a new GitHub Actions workflow file and the integration of this workflow into the existing pull request workflow.
New workflow for flaky E2E tests:
.github/workflows/flaky-e2e-check.yml
: Added a new workflow to detect flaky E2E tests. This workflow checks for changed E2E test files, runs them multiple times, calculates their flakiness, and uploads a report.Integration into existing workflows:
.github/workflows/pr.yml
: Integrated the new flaky E2E check workflow into the existing pull request workflow, ensuring it runs when specific conditions are met.