[
https://issues.apache.org/jira/browse/HADOOP-8810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456041#comment-13456041
]
Hadoop QA commented on HADOOP-8810:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545196/HADOOP-8810.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
-1 javac. The patch appears to cause the build to fail.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1460//console
This message is automatically generated.
> when building with documentation build stops waiting for ENTER on terminal
> --------------------------------------------------------------------------
>
> Key: HADOOP-8810
> URL: https://issues.apache.org/jira/browse/HADOOP-8810
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 2.0.3-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 2.0.3-alpha
>
> Attachments: HADOOP-8810.patch
>
>
> When building the docs {{mvn clean package -Pdocs -DskipTests site site:stage
> -DstagingDirectory=/tmp/hadoop-site}}, in OSX (and I've seen it a few times
> in Ubuntu as well), the build stops, if you press ENTER it continues. It
> happens twice.
> I've traced this down to the exec-maven-plugin invocation of protoc for
> hadoop-yarn-api module (and other YARN module I don't recall at the moment).
> jstacking the Maven process it seems the exec-maven-plugin has some locking
> issues consuming the STDOUT/STDERR of the process being executed.
> I've converted the protoc invocation in the hadoop-yarn-api to use the antrun
> plugin instead and then another module running protoc using exec-maven-puglin
> hang.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
