[ https://issues.apache.org/jira/browse/IMPALA-8059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738435#comment-16738435 ]
Sahil Takiar edited comment on IMPALA-8059 at 1/9/19 5:00 PM: -------------------------------------------------------------- The issue with IMPALA-7625 is that the query {{select sleep(\?)}} only executes the sleep after it reaches the FINISHED state, which is a bit odd. I assumed {{sleep}} was an Impala function that just caused query to sleep while it was running. was (Author: stakiar): The issue with IMPALA-7625 is that the query {{select sleep(?)}} only executes the sleep after it reaches the FINISHED state, which is a bit odd. I assumed {{sleep}} was an Impala function that just caused query to sleep while it was running. > TestWebPage::test_backend_states is flaky > ----------------------------------------- > > Key: IMPALA-8059 > URL: https://issues.apache.org/jira/browse/IMPALA-8059 > Project: IMPALA > Issue Type: Bug > Reporter: Pooja Nilangekar > Assignee: Sahil Takiar > Priority: Blocker > Labels: broken-build, flaky-test > > test_backend_states is flaky. The query reaches the _"FINISHED"_ state before > it's state is verified by the python test. Here are the relevant log: > {code:java} > 07:33:45 ----------------------------- Captured stderr call > ----------------------------- > 07:33:45 -- executing async: localhost:21000 > 07:33:45 select sleep(10000) from functional.alltypes limit 1; > 07:33:45 > 07:33:45 -- 2019-01-08 07:31:57,952 INFO MainThread: Started query > 7f46f15ed4d6d0f6:4d58cdbc00000000 > 07:33:45 -- getting state for operation: > <tests.common.impala_connection.OperationHandle object at 0x5b3db90> > {code} > This bug was introduced by IMPALA-7625. -- 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