You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Peter Somogyi (Jira)" <ji...@apache.org> on 2019/10/05 16:05:00 UTC

[jira] [Resolved] (HBASE-18917) branch-1.4 nightly jdk7 checks timing out at 6 hours

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

Peter Somogyi resolved HBASE-18917.
-----------------------------------
    Resolution: Cannot Reproduce

No timeout on nightlies recently on branch-1 line.

> branch-1.4 nightly jdk7 checks timing out at 6 hours
> ----------------------------------------------------
>
>                 Key: HBASE-18917
>                 URL: https://issues.apache.org/jira/browse/HBASE-18917
>             Project: HBase
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.0
>            Reporter: Sean Busbey
>            Priority: Critical
>
> build trend:
> https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/buildTimeTrend
> recent failed build:
> https://builds.apache.org/job/HBase%20Nightly/job/branch-1.4/74/
> final step with elapsed time:
> {code}
> 00:57:37.903 ============================================================================
> 00:57:37.903 ============================================================================
> 00:57:37.903                             Running unit tests
> 00:57:37.903 ============================================================================
> 00:57:37.903 ============================================================================
> 00:57:37.903 
> 00:57:37.903 
> 00:57:37.903 cd /testptch/hbase
> 00:57:37.903 mvn -DHBasePatchProcess clean test -fae > /testptch/patchprocess/patch-unit-root.txt 2>&1
> Cancelling nested steps due to timeout
> 06:00:11.878 Sending interrupt signal to process
> Post stage
> 06:00:18.964 Terminated
> 06:00:19.722 Recording test results
> {code}
> Maybe we just need a bit more time? maybe something is v bad, but we should try to figure out what's going on.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)