ZEPPELIN-510: setting max waitForParagraph to 60s #549
Conversation
This file contains hidden or 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
Member
|
+1 Let's see if 60 fixes the issue. If not, I think we need to investigate the reason of flakiness (which does not happen on local environments). |
prabhjyotsingh
changed the title
Contributor
Author
|
Sure updated it. thanks. |
prabhjyotsingh
force-pushed
the
zeppelin-510-integration-tests-paragraph-dealy
branch
from
d554d2e to
cfb408c
Compare
Member
|
Looks great to me! Merging in and following the plan from above |
Closed
prabhjyotsingh
deleted the
zeppelin-510-integration-tests-paragraph-dealy
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
setting max waitForParagraph to 60s + poll every 1s