This repository has been archived by the owner on Mar 13, 2024. It is now read-only.
Cypress/E2E: Fix time out error on initial Cypress run against remote server #7385
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
josephbaylon
approved these changes
Jan 25, 2021
furqanmlk
approved these changes
Jan 25, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Fix time out error on initial Cypress run against remote server. Note that the time out error is not related to product changes but most likely related to initial access by newly created admin user against newly created remote server in CI. It might be something to do with DNS propagation but will investigate further. For the meantime, the solution here works 100% of the time.
Ticket Link
none, failing on daily Cypress run