[
https://issues.apache.org/jira/browse/IMPALA-8676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883369#comment-16883369
]
Joe McDonnell commented on IMPALA-8676:
---------------------------------------
This Jira is an artifact of particular Cloudera testing infrastructure and is
not a general upstream issue. The way that this was fixed for Cloudera is to
shard the tests into multiple jobs. We run FE_TEST, BE_TEST, JDBC_TEST, and
CLUSTER_TEST separately from EE_TEST if the machines are slow. An alternative
fix is to set the TIMEOUT_FOR_RUN_ALL_TESTS_MINS environment variable to a
higher value.
Closing this.
> run-all-tests-timeout-check.sh times out after 20 hours
> --------------------------------------------------------
>
> Key: IMPALA-8676
> URL: https://issues.apache.org/jira/browse/IMPALA-8676
> Project: IMPALA
> Issue Type: Bug
> Reporter: Andrew Sherman
> Assignee: David Knupp
> Priority: Blocker
> Labels: broken-build
>
> An exhaustive test run on Centos6 now takes 22 hours.
> run-all-tests-timeout-check.sh will time out after 20 hours.
> {code}
> 15:39:30 **** Timout Timer Started (pid 20144, ppid 20063) for 72000 s! ****
> {code}
> {code}
> 11:39:30 **** Tests TIMED OUT! ****
> {code}
> Some tests take a long time, we could try to fix that.
> Or we could bump ${TIMEOUT_FOR_RUN_ALL_TESTS_MINS} which is currently 1200
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
