chore(ci): shard e2e components tests #7581
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
No changes to documentation |
⚡️ Editor Performance ReportUpdated Thu, 03 Oct 2024 20:40:22 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
binoy14
force-pushed
the
10-03-chore_ci_shard_e2e_components_tests
branch
2 times, most recently
from
b9b83f1
to
ef6b920
Compare
binoy14
force-pushed
the
10-03-chore_ci_shard_e2e_components_tests
branch
from
ef6b920
to
adf8874
Compare
|
Component Testing Report Updated Oct 3, 2024 8:31 PM (UTC) ✅ All Tests Passed -- expand for details
|
ricokahler
approved these changes
Oct 4, 2024
ricokahler
pushed a commit
that referenced
this pull request
Oct 4, 2024
### Description <!-- What changes are introduced? Why are these changes introduced? What issue(s) does this solve? (with link, if possible) --> This PR shards e2e components tests so they run on 2 shards per browser. This should significantly speed up the test run. ### What to review <!-- What steps should the reviewer take in order to review? What parts/flows of the application/packages/tooling is affected? --> Changes makes sense and the tests pass ### Testing <!-- Did you add sufficient testing for this change? If not, please explain how you tested this change and why it was not possible/practical for writing an automated test --> N/A ### Notes for release <!-- Engineers do not need to worry about the final copy, but they must provide the docs team with enough context on: * What changed * How does one use it (code snippets, etc) * Are there limitations we should be aware of If this is PR is a partial implementation of a feature and is not enabled by default or if this PR does not contain changes that needs mention in the release notes (tooling chores etc), please call this out explicitly by writing "Part of feature X" or "Not required" in this section. --> N/A
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR shards e2e components tests so they run on 2 shards per browser. This should significantly speed up the test run.
What to review
Changes makes sense and the tests pass
Testing
N/A
Notes for release
N/A