CB-15495 TestNg E2E tiemout validation if INTEGRATIONTEST_TIMEOUT_E2E_CHECK set #11974
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
aszegedi
force-pushed
the
test-testngtimeout
branch
2 times, most recently
from
dcfaeb9
to
5aaf83d
Compare
aszegedi
force-pushed
the
test-testngtimeout
branch
from
5aaf83d
to
b883508
Compare
horadla23
approved these changes
Dec 17, 2021
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.
Our E2E tests are running in parallel by 8 threads (with the help of TestNG parallel attribute):
This helps us to reduce the 'execution time' as tests are executed simultaneously in different threads.
Beyond this we applied a 100 minutes timeout for our test cases by default, on this way we can guarantees that none of the threads will block on a stuck test thread forever.
Unfortunately test case's thread is terminated if it takes longer than it's timeout setting. I found some similar issues at TestNG:
For now we can introduce an extra validation in our check-results.sh as a workaround for this.
This PR has precondition at cloudbreak-ansible-playbooks#163