chore(ci): extend smoketests timeouts to account for slow windows machines COMPASS-9464 #7031
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
gribnoysup
added
no-title-validation
gribnoysup
changed the title
lerouxb
approved these changes
Jun 17, 2025
Collaborator
Author
|
Smokes passed (although none of them hit previous timeout), merging |
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.
Seems like the common reason for smoketests to fail on window is that the GHA windows runners take an unexpectedly long time during npm install, leaving basically no time for the actual e2e tests to run before the task timeout is hit. This patch changes the timeout to try to account for that