hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10532) Jenkins test-patch timed out on a large patch touching files in multiple modules.
Date Wed, 29 Apr 2015 01:59:06 GMT

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

Allen Wittenauer commented on HADOOP-10532:

This is pretty much Working As Designed.  Jenkins has a setting for how long a given patch
run should be.  If it goes over that value, it thinks the job is hung and kills it.

The problem we've got is that hadoop-hdfs unit tests runs for an extremely long time.  It
would probably be well worth the effort to break it up from a single module to multiple modules,
similarly to how yarn is currently designed.  This would limit the possibility of running
over that time for the vast majority of patches.   We probably still couldn't run ALL of the
unit tests, but those types of patches are extremely rare and/or can be broken up into multiple

> 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: Bug
>          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

View raw message