[ 
https://issues.apache.org/jira/browse/HBASE-22505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852691#comment-16852691
 ] 

stack commented on HBASE-22505:
-------------------------------

Will look in morning but this is taking a long time....

{code}
15:28:55  [htmlpublisher] Archiving HTML reports...
15:28:55  [htmlpublisher] Archiving at BUILD level 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.1-S5GA5UYEBNAEMXMEVWGCXQO7HNXNX47M5KZBXWNNXMFDW4LAP27Q@2/output-jdk8-hadoop3
 to /x1/jenkins/jenkins-home/jobs/HBase 
Nightly/branches/branch-2-1.nhtl1j/builds/1213/htmlreports/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
Cancelling nested steps due to timeout
18:41:46  Sending interrupt signal to process
18:41:47  Sending interrupt signal to process
18:41:47  script returned exit code 2
{code}

Here is a random build before the hadoop upgrade:

{code}
05:46:56  [htmlpublisher] Archiving HTML reports...
05:46:56  [htmlpublisher] Archiving at BUILD level 
/home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.1-S5GA5UYEBNAEMXMEVWGCXQO7HNXNX47M5KZBXWNNXMFDW4LAP27Q/output-general
 to /x1/jenkins/jenkins-home/jobs/HBase 
Nightly/branches/branch-2-1.nhtl1j/builds/1200/htmlreports/General_20Nightly_20Build_20Report
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
07:02:22  Elapsed: 182m 58s
{code}

70odd minutes vs ~200. More html generated now? Will look in morning.

> Nightly jobs for branch-2.1+ are always timeout
> -----------------------------------------------
>
>                 Key: HBASE-22505
>                 URL: https://issues.apache.org/jira/browse/HBASE-22505
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Duo Zhang
>            Priority: Major
>
> Need to find out why, and the first thing maybe increasing the timeout value?



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

Reply via email to