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

Hadoop QA commented on HADOOP-11933:
------------------------------------

\\
\\
| (/) *{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 16s | The applied patch does 
not increase the total number of release audit warnings. |
| {color:green}+1{color} | shellcheck |   0m  9s | There were no new shellcheck 
(v0.3.7) issues. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that 
end in whitespace. |
| | |   0m 28s | |
\\
\\
|| Subsystem || Report/Notes ||
| Java | 1.7.0_80 |
| uname | Linux 29d8e3040b6d 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 |
| Docker | Enabled |
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12732117/HADOOP-11933.02.patch |
| Optional Tests | shellcheck |
| git revision | trunk / 3d28611 |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/6620/console |


This message was automatically generated.

> run test-patch.sh in a docker container under Jenkins
> -----------------------------------------------------
>
>                 Key: HADOOP-11933
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11933
>             Project: Hadoop Common
>          Issue Type: Test
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-11933.00.patch, HADOOP-11933.01.patch, 
> HADOOP-11933.02.patch
>
>
> because of how hard it is to control the content of the Jenkins environment, 
> it would be beneficial to run it in a docker container so that we can have 
> tight control of the environment



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to