[ 
https://issues.apache.org/jira/browse/IMPALA-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526353#comment-17526353
 ] 

Tamas Mate commented on IMPALA-10111:
-------------------------------------

This recurred 5 times this year, checked the logs of the latest failure but 
nothing suspicious, the queries finished quite fast ~0.3 seconds. I think we 
could print the json in case of a failure to better understand whether the 
queries were in another state or aged out of the log. Created a CR for this:
[https://gerrit.cloudera.org/#/c/18442/]

> TestWebPage::test_query_stmt is flaky
> -------------------------------------
>
>                 Key: IMPALA-10111
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10111
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Quanlong Huang
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: broken-build, flaky
>
> Found in an unrelated patch: 
> https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/3032/testReport/junit/webserver.test_web_pages/TestWebPage/test_query_stmt/
> {code:java}
> webserver/test_web_pages.py:418: in test_query_stmt
>     assert check_if_contains, "No matching statement found in the jsons."
> E   AssertionError: No matching statement found in the jsons.
> E   assert False {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to