[Do not merge] - Isolate flaky tests related to Linodes/Firewalls #10580
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
jdamore-linode
requested review from
AzureLatte,
mjac0bs and
jaalah-akamai
and removed request for
a team
|
Coverage Report: ✅ |
12 tasks
|
Going to close this since it'll probably be a while before I can revisit this -- will reopen if I need to. |
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 📝
Adding Firewalls to our Linodes seems to have increased our test flakiness because the API is responding with 400s in situations where it's unexpected.
This PR is meant to isolate the affected tests for exploration/reproduction. It also modifies the
yarn cy:runcommand to only run the affected tests.(We do not want to merge this)