[package testing] Bump status page timeout #107813
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
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to elastic#106749 and elastic#107300
jbudz
added
review
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
jbudz
added
auto-backport
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
spalger
approved these changes
Aug 16, 2021
kibanamachine
added a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 16, 2021
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to elastic#106749 and elastic#107300 Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
kibanamachine
added a commit
that referenced
this pull request
Aug 16, 2021
The socket timeout for testing whether the status page is available or not is currently 30 seconds. This test was disabled for being flaky. Reproducing this locally hasn't been straight forward, but I am seeing an average of ~20 seconds, which is close enough to the timeout that I'd like to rule out machine differences. This gives the status check 120 seconds before dropping the connection. Related to #106749 and #107300 Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Jonathan Budzenski <[email protected]>
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.
The socket timeout for testing whether the status page is available or
not is currently 30 seconds. This test was disabled for being flaky.
Reproducing this locally hasn't been straight forward, but I am seeing
an average of ~20 seconds, which is close enough to the timeout that I'd
like to rule out machine differences. This gives the status check 120
seconds before dropping the connection.
Related to #106749 and #107300