You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/01/30 06:15:00 UTC

[jira] [Updated] (HBASE-19891) Up nightly test run timeout from 6 hours to 8

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

stack updated HBASE-19891:
--------------------------
    Description: Yesterday, a nightly run for hbase2 passed all unit tests against hadoop2. Hadoop3 tests got cut off at the 6 hour mark, our maximum total run time. This is crazy but for now, just up the max time from 6 to 8 hours to see if we can get a good build in. Can work on breaking this down in subsequent issues. To be clear, the nightly 2.0 runs full test suite against hadoop2 and then hadoop3... this is why it takes a while.  (was: Yesterday, a nightly run for hbase2 passed all unit tests against hadoop2. Hadoop3 tests got cut off at the 6 hour mark, our maximum total run time. This is crazy but for now, just up the max time from 6 to 8 hours to see if we can get a good build in. Can work on breaking this down in subsequent issues.)

> Up nightly test run timeout from 6 hours to 8
> ---------------------------------------------
>
>                 Key: HBASE-19891
>                 URL: https://issues.apache.org/jira/browse/HBASE-19891
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Priority: Major
>
> Yesterday, a nightly run for hbase2 passed all unit tests against hadoop2. Hadoop3 tests got cut off at the 6 hour mark, our maximum total run time. This is crazy but for now, just up the max time from 6 to 8 hours to see if we can get a good build in. Can work on breaking this down in subsequent issues. To be clear, the nightly 2.0 runs full test suite against hadoop2 and then hadoop3... this is why it takes a while.



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