hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11904) test-patch.sh goes into an infinite loop on non-maven builds
Date Wed, 06 May 2015 15:52:00 GMT

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

Sean Busbey commented on HADOOP-11904:

Ugh. This totally broke my reuse efforts over on NIFI-577. I was relying on the plugin system
to move into the correct sub-directory to get to poms. I'll file a ticket to add plugin points
instead of overriding post checkout?

> test-patch.sh goes into an infinite loop on non-maven builds
> ------------------------------------------------------------
>                 Key: HADOOP-11904
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11904
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: test
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Critical
>             Fix For: 2.8.0
>         Attachments: HADOOP-11904.patch
> If post HADOOP-11746 test patch is given a non-maven-based build, it goes into an infinite
loop looking for modules pom.xml.  There should be an escape clause after switching branches
to see if it is maven based. If it is not maven based, then test-patch should either abort
or re-exec using that version's test-patch script.

This message was sent by Atlassian JIRA

View raw message