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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @fjtirado
I see the point, but are we saying that this single test could hang two minutes before failing ?
Is it not a code-smell of some underlying issue ?
And if a similar problem arise on other tests, are we going to raise the timeout in the same way, getting to a never-ending build ?
My questions are not related to this PR in particular, for which I've not a strong opinion; but we are keeping increasing timeouts, lately, so maybe we should start looking at the issue at its root.
@baldimir any opinion on that ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gitgabrio Jenkins is slow and downloading the keycloak image and deploying it takes more than the 60s default.
It has nothing to be with our codebase. See Apache list for more information on that. There I already complanined about our test strategy, but this one has to go in or the nightly is going to unnecesarily be flaky @pibizza