Agentless_cluster_env system tests timeout changed in order to reduce EC2 requirements #4534
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
pro-akim
changed the title
This was
linked to
issues
Sep 20, 2023
rauldpm
approved these changes
Sep 20, 2023
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
Agentless_cluster_env system tests required extended timeout in its message.yml logs in to be stable in EC2 Ubuntu 22.04.3 LTS t3.large 15GB HD
Updated
Changed test_integrity_sync/data/messages.yml timeout out figures:
Testing performed
Test results are focused in test_integrity_sync where one of the tests had a stable Failure without the timeout changes.