[
https://issues.apache.org/jira/browse/IMPALA-7175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16514316#comment-16514316
]
Vuk Ercegovac commented on IMPALA-7175:
---------------------------------------
I see the following that's due to the ImpalaCluster() call on L325:
MainThread: Found 2 impalad/1 statestored/1 catalogd process(es)
The test is run multiple times and all of the other runs it look like this:
MainThread: Found 1 impalad/1 statestored/1 catalogd process(es)
I see a lot of these types of messages that are likely thrown at L132 when a
listed process is not found:
MainThread: no process found with pid 20961
...
For ee-tests, I assume the cluster nodes are *not* expected to be killed or
die.
> In a local FS build, test_native_functions_race thinks there are 2 impalads
> where there should be 1
> ---------------------------------------------------------------------------------------------------
>
> Key: IMPALA-7175
> URL: https://issues.apache.org/jira/browse/IMPALA-7175
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.1.0
> Reporter: Tianyi Wang
> Assignee: Vuk Ercegovac
> Priority: Critical
> Labels: broken-build
>
> In TestUdfExecution.test_native_functions_race, the test checks the number of
> impalads at the beginning and end of the test. In a local build there should
> be only 1 impalad but somehow the test found 2 at the beginning of the test
> and failed.
> {noformat}
> Stacktrace
> query_test/test_udfs.py:379: in test_native_functions_race
> assert len(cluster.impalads) == exp_num_impalads
> E assert 1 == 2
> E + where 1 = len([<tests.common.impala_cluster.ImpaladProcess object at
> 0xc9ffa90>])
> E + where [<tests.common.impala_cluster.ImpaladProcess object at
> 0xc9ffa90>] = <tests.common.impala_cluster.ImpalaCluster object at
> 0x6a5d510>.impalads
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
