Paul Rogers created IMPALA-8025:
-----------------------------------
Summary: End-to-end tests sometimes unhelpfully truncate error
output
Key: IMPALA-8025
URL: https://issues.apache.org/jira/browse/IMPALA-8025
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 3.1.0
Reporter: Paul Rogers
Made a change to the DESCRIBE output per IMPALA-8021. This required adjustment
to {{metadata/test_explain.py}} to account for the change. The test encodes a
"golden" version in a .test file using a specialized syntax.
But, when running the test, the output shows the first few lines (which do
match), then elides the rest:
{noformat}
E row_regex:.*mem-estimate=[0-9.]*[A-Z]*B mem-reservation=[0-9.]*[A-Z]*B
thread-reservation=0 == '| mem-estimate=0B mem-reservation=0B
thread-reservation=0'
E Detailed information truncated (45 more lines), use "-vv" to show
{noformat}
As it turns out, passing "-vv" to {{tests/run-tests.py}} does not seem to pass
it to the test program, so that did not work.
The .xml file for the test contains the same message: output is truncated. Same
in the .log file.
So, the question is, how is a developer to figure out the issue if we can't see
the actual error lines? This is the kind of thing that converts a simple task
into a multi-hour ordeal.
Right now, the only solution is to rerun the tests with {{--update_results}}
flag to {{run-tests.py}}, then hunt down the generated output file.
Better would be to output the n lines before the error, rather than the first n
lines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
