[jira] [Resolved] (IMPALA-8554) The timeout in run-all-tests-timeout-check.sh is triggered in exhaustive test runs on CentOS 6

["Joe McDonnell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell resolved IMPALA-8554.
-----------------------------------
    Fix Version/s: Impala 3.3.0
       Resolution: Workaround

The workaround is to split the test execution into multiple steps (each with its own timeout). There should be further effort to reduce the test matrix for exhaustive, but that can happen in a different JIRA. I think we can close this issue for now.

> 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
>             Fix For: Impala 3.3.0
>
>
> 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
(v8.3.4#803005)