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

Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/11/05 23:44:27 UTC

[jira] [Commented] (HADOOP-10532) Jenkins test-patch timed out on a large patch touching files in multiple modules.

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

Allen Wittenauer commented on HADOOP-10532:
-------------------------------------------

Closing as a dupe.  test-patch has been replaced by Yetus.

> Jenkins test-patch timed out on a large patch touching files in multiple modules.
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-10532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10532
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: build
>    Affects Versions: 3.0.0
>            Reporter: Chris Nauroth
>            Assignee: Jean-Pierre Matsumoto
>         Attachments: PreCommit-HADOOP-Build-3821-consoleText.txt.gz
>
>
> On HADOOP-10503, I had posted a consolidated patch touching multiple files across all sub-modules: Hadoop, HDFS, YARN and MapReduce.  The Jenkins test-patch runs for these consolidated patches timed out.  I also experimented with a dummy patch that simply added one-line comment changes to files.  This patch also timed out, which seems to indicate a bug in our automation rather than a problem with any patch in particular.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)