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

Hadoop QA commented on HADOOP-12479:
------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  16m 44s | Pre-patch trunk compilation is 
healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear 
to include any new or modified tests.  Please justify why no new tests are 
needed for this patch. Also please list what manual steps were performed to 
verify this patch. |
| {color:green}+1{color} | javac |   8m  1s | There were no new javac warning 
messages. |
| {color:green}+1{color} | javadoc |  10m 32s | There were no new javadoc 
warning messages. |
| {color:red}-1{color} | release audit |   0m 17s | The applied patch generated 
1 release audit warnings. |
| {color:green}+1{color} | checkstyle |   0m 17s | There were no new checkstyle 
issues. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that 
end in whitespace. |
| {color:green}+1{color} | install |   1m 32s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 34s | The patch built with 
eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   0m 41s | The patch does not introduce 
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | maven tests |   0m 13s | Tests passed in 
hadoop-maven-plugins. |
| | |  38m 55s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12766669/HADOOP-12479.001.patch 
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / be7a0ad |
| Release Audit | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7815/artifact/patchprocess/patchReleaseAuditProblems.txt
 |
| hadoop-maven-plugins test log | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7815/artifact/patchprocess/testrun_hadoop-maven-plugins.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7815/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf904.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/7815/console |


This message was automatically generated.

> ProtocMojo does not log the reason for a protoc compilation failure.
> --------------------------------------------------------------------
>
>                 Key: HADOOP-12479
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12479
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Minor
>         Attachments: HADOOP-12479.001.patch
>
>
> If protoc fails with a compilation error in the proto files, our Maven plugin 
> won't print the details.  The only way to figure it out is to repeat running 
> the {{protoc}} command manually from outside the Hadoop build.  This is 
> because our {{ProtocMojo}} only captures stdout from the {{protoc}} command, 
> and compilation errors get written to {{stderr}}.



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

Reply via email to