Allow WP Trunk E2E tests to fail. #959
Merged
Conversation
This file contains hidden or 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
peterwilsoncc
requested review from
a team and
Sidsector9
and removed request for
a team
Member
|
This approach works for me, we could also pause the running of the action entirely and avoid a code change in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 of the Change
Due to an upstream bug in
wordpress/envthe E2E tests for WordPress trunk are failing. See WordPress/gutenberg#44887As a temporary measure, these tests should be allowed to fail without blocking merge/ending the other E2E test runs early.
Closes #958
How to test the Change
Changelog Entry
Credits
Props @peterwilsoncc
Checklist: