You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Lars Volker (JIRA)" <ji...@apache.org> on 2019/06/11 04:36:00 UTC
[jira] [Assigned] (IMPALA-8554) The timeout in
run-all-tests-timeout-check.sh is triggered in exhaustive test runs on
CentOS 6
[ https://issues.apache.org/jira/browse/IMPALA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Volker reassigned IMPALA-8554:
-----------------------------------
Assignee: Laszlo Gaal
> The timeout in run-all-tests-timeout-check.sh is triggered in exhaustive test runs on CentOS 6
> ----------------------------------------------------------------------------------------------
>
> Key: IMPALA-8554
> URL: https://issues.apache.org/jira/browse/IMPALA-8554
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 3.3.0
> Environment: CentOS 6, exhaustive mode
> Reporter: Laszlo Gaal
> Assignee: Laszlo Gaal
> Priority: Blocker
> Labels: broken-build
>
> Exhaustive test runs on CentOS 6 can take around 20-22 hours even in the normal case.
> run-all-tests-timeout-check.sh installs a timeout guard of 72000 s, i.e. 20 hours, which includes only the tests, but excludes build and dataload time.
> On recent runs some of the spilling tests ran slowly but successfully, which made the timeout fire during the last items of custom_cluster_tests, cutting the test run short.
> I think the timeout should be made longer for CentOS 6 based tests until we find ways to run those faster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org