hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-20122) Up timeout on nightlies to 9 hours from 8 on branch-2 and master
Date Sat, 03 Mar 2018 15:37:00 GMT

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

stack resolved HBASE-20122.
---------------------------
    Resolution: Fixed
      Assignee: stack

I pushed the below...


commit 2b1b2c849051b6ba033988fccd74a2285bd1f474
Author: Michael Stack <stack@apache.org>
Date:   Sat Mar 3 07:33:25 2018 -0800

    HBASE-20122 Up timeout on nightlies to 9 hours from 8 on branch-2 and
    master

diff --git a/dev-support/Jenkinsfile b/dev-support/Jenkinsfile
index fa7c8ba6cd..f74ab91e5d 100644
--- a/dev-support/Jenkinsfile
+++ b/dev-support/Jenkinsfile
@@ -21,7 +21,7 @@ pipeline {
   }
   options {
     buildDiscarder(logRotator(numToKeepStr: '30'))
-    timeout (time: 8, unit: 'HOURS')
+    timeout (time: 9, unit: 'HOURS')
     timestamps()
     skipDefaultCheckout()
   }

> Up timeout on nightlies to 9 hours from 8 on branch-2 and master
> ----------------------------------------------------------------
>
>                 Key: HBASE-20122
>                 URL: https://issues.apache.org/jira/browse/HBASE-20122
>             Project: HBase
>          Issue Type: Task
>          Components: build
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>
> I know its ridiculous and we need to profile the test run to cut down the time taken,
but for now am going to up the timeout from 8 to 9 hours.... Last night tests failed because
they took > 8 hours: https://builds.apache.org/job/HBase%20Nightly/job/branch-2/ Looks
like they'd even made through all the unit testing and were just doing findbugs and tarball
making.... 



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

Mime
View raw message