[
https://issues.apache.org/jira/browse/IMPALA-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-7405.
-----------------------------------
Fix Version/s: Impala 3.2.0
Resolution: Fixed
We added code to timeout tests before the Jenkins job timeout and dump
debugging information. Initial change here:
[https://github.com/apache/impala/commit/11c90c3d7d18ec81ae66d7cf1e6d71ac2be4eec2]
There were subsequent changes that expanded what got dumped. There may be more
to do, but it can be tracked in a separate JIRA.
> Save jenkins artifacts when aborted by a timeout
> ------------------------------------------------
>
> Key: IMPALA-7405
> URL: https://issues.apache.org/jira/browse/IMPALA-7405
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 3.1.0
> Reporter: Vuk Ercegovac
> Priority: Major
> Labels: flaky-build
> Fix For: Impala 3.2.0
>
>
> Occasionally, builds abort due to timeouts. See:
> [https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/2882] for an
> example. At the end of the run, there's a large time gap:
> {noformat}
> ...
> 20:08:21 [gw12] PASSED
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_naaj[exec_option:
> {'debug_action': None, 'default_spillable_buffer_size': '256k'} |
> table_format: parquet/none]
> 20:08:21
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_naaj[exec_option:
> {'debug_action': '-1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0',
> 'default_spillable_buffer_size': '256k'} | table_format: parquet/none]
> 20:09:51 [gw12] PASSED
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_naaj[exec_option:
> {'debug_action': '-1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0',
> 'default_spillable_buffer_size': '256k'} | table_format: parquet/none]
> 20:09:51
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_regression_exhaustive[exec_option:
> {'debug_action': None, 'default_spillable_buffer_size': '256k'} |
> table_format: parquet/none]
> 20:09:51 [gw12] SKIPPED
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_regression_exhaustive[exec_option:
> {'debug_action': None, 'default_spillable_buffer_size': '256k'} |
> table_format: parquet/none]
> 20:09:51
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_regression_exhaustive[exec_option:
> {'debug_action': '-1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0',
> 'default_spillable_buffer_size': '256k'} | table_format: parquet/none]
> 20:09:51 [gw12] SKIPPED
> query_test/test_spilling.py::TestSpillingDebugActionDimensions::test_spilling_regression_exhaustive[exec_option:
> {'debug_action': '-1:OPEN:SET_DENY_RESERVATION_PROBABILITY@1.0',
> 'default_spillable_buffer_size': '256k'} | table_format: parquet/none] Set
> build name.
> 03:38:00 New build name is '#2882 master'
> 03:38:00 Build was aborted
> 03:38:00 Calling Pipeline was cancelled
> 03:38:00 Archiving artifacts
> 03:38:00 Recording test results
> 03:38:01 None of the test reports contained any result
> 03:38:01 Finished: ABORTED
> {noformat}
> However, no artifacts were saved so we can't see what was going on during
> that 7 hour gap. Similar issues have hindered debugging other cases that
> timeout once in a while: https://issues.apache.org/jira/browse/IMPALA-6352
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
