[
https://issues.apache.org/jira/browse/HADOOP-11904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528938#comment-14528938
]
Hadoop QA commented on HADOOP-11904:
------------------------------------
\\
\\
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | reexec | 0m 0s | dev-support patch detected. |
| {color:blue}0{color} | pre-patch | 0m 0s | Pre-patch trunk compilation is
healthy. |
| {color:blue}0{color} | @author | 0m 0s | Skipping @author checks as
test-patch has been patched. |
| {color:green}+1{color} | release audit | 0m 15s | The applied patch does
not increase the total number of release audit warnings. |
| {color:blue}0{color} | shellcheck | 0m 15s | Shellcheck was not available. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| | | 0m 23s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12730046/HADOOP-11904.patch |
| Optional Tests | shellcheck |
| git revision | trunk / fcd4cb7 |
| Java | 1.7.0_55 |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6486/console |
This message was automatically generated.
> 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
> 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)
