[
https://issues.apache.org/jira/browse/HADOOP-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537034#comment-14537034
]
Hadoop QA commented on HADOOP-11951:
------------------------------------
\\
\\
| (/) *{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 14s | The applied patch does
not increase the total number of release audit warnings. |
| {color:green}+1{color} | shellcheck | 0m 6s | There were no new shellcheck
(v0.3.3) issues. |
| {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/12731773/HADOOP-11951.1.patch |
| Optional Tests | shellcheck |
| git revision | trunk / a60f78e |
| Java | 1.7.0_55 |
| uname | Linux asf906.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/6575/console |
This message was automatically generated.
> test-patch should give better info about failures to handle dev-support
> updates without resetrepo option
> --------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11951
> URL: https://issues.apache.org/jira/browse/HADOOP-11951
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Minor
> Attachments: HADOOP-11951.1.patch, HADOOP-11951.1.patch
>
>
> Right now, reexecuting for dev-support changes fails if test-patch can't
> reset the local working directory (either via --reset-repo or implicitly via
> --jenkins). It fails with a message about having a dirty workspace. If you
> clean things up and rerun with the "allow dirty workspace" option, it then
> fails because the patch can't be reapplied.
> Instead just give a good message about not being able to reexec and leave a
> warning in jira feedback.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
