[
https://issues.apache.org/jira/browse/KUDU-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2112:
------------------------------
Issue Type: Improvement (was: Bug)
> Python tests don't retain server logs
> -------------------------------------
>
> Key: KUDU-2112
> URL: https://issues.apache.org/jira/browse/KUDU-2112
> Project: Kudu
> Issue Type: Improvement
> Components: python, test
> Affects Versions: 1.4.0
> Reporter: Mike Percy
> Assignee: Jordan Birdsell
> Priority: Major
> Labels: newbie
>
> The python tests don't retain the server logs. According to
> https://github.com/apache/kudu/blob/master/python/kudu/tests/common.py it
> looks like we are sending the logs to stderr but then we throw away the
> output. The output doesn't end up in the python3_client.log, even though
> build-and-test.sh has this:
> {code}
> # Run the Python tests.
> if ! python setup.py test \
> --addopts="kudu --junit-xml=$TEST_LOGDIR/python3_client.xml" \
> 2> $TEST_LOGDIR/python3_client.log ; then
> EXIT_STATUS=1
> FAILURES="$FAILURES"$'Python 3 tests failed\n'
> fi
> {code}
> This lack of logs makes it hard to debug python test failures, especially
> when they happen on pre-commit builds in Jenkins.
> I also wonder if we are buffering stderr and if it's too large for the buffer
> then the daemon can block. There was a hang on one of the python tests and I
> don't know why; this is just speculation. It could have also been some kind
> of server or client deadlock.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
