hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (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 16:57:03 GMT

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

Hudson commented on HADOOP-11904:
---------------------------------

SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #186 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/186/])
HADOOP-11904. test-patch.sh goes into an infinite loop on non-maven builds (aw) (aw: rev 3ff91e9e9302d94b0d18cccebd02d3815c06ce90)
* hadoop-common-project/hadoop-common/CHANGES.txt
* dev-support/test-patch.sh


> 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
(v6.3.4#6332)

Mime
View raw message