Lars Volker created IMPALA-6600:
-----------------------------------

             Summary: py.test error "Replacing crashed slave gw1" in 
test_spilling
                 Key: IMPALA-6600
                 URL: https://issues.apache.org/jira/browse/IMPALA-6600
             Project: IMPALA
          Issue Type: Bug
          Components: Infrastructure
    Affects Versions: Impala 3.0, Impala 2.12.0
            Reporter: Lars Volker
            Assignee: David Knupp


I saw a build fail with "Replacing crashed slave gw1". Here's the failing part 
of the log:

{noformat}
12:18:33 [gw0] PASSED 
query_test/test_tablesample.py::TestTableSample::test_tablesample[repeatable: 
False | exec_option: {'batch_size': 0, 'num_nodes': 0, 
'disable_codegen_rows_threshold': 0, 'disable_codegen': False, 
'abort_on_error': 1, 'debug_action': None, 'exec_single_node_rows_threshold': 
0} | table_format: parquet/none] 
12:18:33 [gw1] node down: Not properly terminated
12:18:33 [gw1] FAILED 
query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling[exec_option:
 {'debug_action': None, 'default_spillable_buffer_size': '256k'} | 
table_format: parquet/none] 
12:18:33 Replacing crashed slave gw1
12:18:34 
12:18:34 unittests/test_file_parser.py::TestTestFileParser::test_valid_parse 
{noformat}

Here is the summary:

{noformat}
12:44:14 =================================== FAILURES 
===================================
12:44:14 _________________________ query_test/test_spilling.py 
__________________________
12:44:14 [gw1] linux2 -- Python 2.6.6 
/data/jenkins/workspace/impala-asf-master-core-local/repos/Impala/bin/../infra/python/env/bin/python
12:44:14 Slave 'gw1' crashed while running 
"query_test/test_spilling.py::TestSpillingDebugActionDimensions::()::test_spilling[exec_option:
 {'debug_action': None, 'default_spillable_buffer_size': '256k'} | 
table_format: parquet/none]"
12:44:14 ====== 1 failed, 1494 passed, 404 skipped, 9 xfailed in 10374.68 
seconds =======
{noformat}

[~dknupp] - I’m assigning this to you thinking you might have an idea what’s 
going on here; feel free to find another person or assign back to me if you're 
swamped.

I’ve seen this happen in a private Jenkins run. Please ping me if you would 
like access to the build artifacts.

I've also seen a similar error message in IMPALA-5724 and in [this GRPC issue 
on Github|https://github.com/grpc/grpc/issues/3577].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to