👷 timeout e2e-bs ci job after 30 minutes #2999
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
cy-moi
approved these changes
Sep 16, 2024
BenoitZugmeyer
approved these changes
Sep 17, 2024
thomas-lebeau
deleted the
thomas.lebeau/gitlab-e2e-bs-timeout-30-min
branch
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.
Motivation
Sometime the e2e-bs job is losing connection to Browserstack (example), this result is the job not doing anything until it times out, after 1 hour.
In the past month, no successful job has taken more that 30 minutes (query, except one, but seems like a fluke)
Reducing the timeout for this job to 30 minutes will reduce the unnecessary waiting time
Changes
Testing
I have gone over the contributing documentation.