KAFKA-10822 Force some stdout from system tests for Travis#9712
KAFKA-10822 Force some stdout from system tests for Travis#9712chia7712 wants to merge 1 commit intoapache:trunkfrom
Conversation
chia7712
changed the title
abbccdda
left a comment
abbccdda
left a comment
There was a problem hiding this comment.
Looks like the build is still in error?
Thanks for your reviews. The main purpose of this PR is to avoid timeout from downgrade_test.py/upgrade_test.py. I browse the test results and the timeout does not happen on downgrade_test.py/upgrade_test.py again. After fixing the timeout issue, I will go back to dead with the true failure of system tests. |
chia7712
force-pushed
the
KAFKA-10822
branch
2 times, most recently
from
d71fb3f to
28600af
Compare
chia7712
changed the title
chia7712
force-pushed
the
KAFKA-10822
branch
from
28600af to
4c07e54
Compare
chia7712
changed the title
chia7712
force-pushed
the
KAFKA-10822
branch
from
4c07e54 to
7fa43b4
Compare
|
The timeout of "no output" is caused by only |
| self.await_startup() | ||
|
|
||
| self.logger.info("First pass bounce - rolling upgrade") | ||
| print("First pass bounce - rolling upgrade", flush=True) # Force some stdout for Travis |
There was a problem hiding this comment.
This seems weird. If we want to force stdout, we should configure the logger to do so, right?
There was a problem hiding this comment.
I tried to configure ducktape to force more output but ducktape supports only --debug. It is too noisy to me.
Another way is to make a patch to ducktape for INFO level support. WDYT?
There was a problem hiding this comment.
3 participants
issue: https://issues.apache.org/jira/browse/KAFKA-10822
downgrade_test.py/upgrade_test.py does upgrade/downgrade for each tests. the upgrade/downgrade tasks take 10+ mins in Travis env so we ought to print something in order to avoid timeout caused by Travis.
Committer Checklist (excluded from commit message)