[
https://issues.apache.org/jira/browse/HADOOP-11495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288332#comment-14288332
]
Hadoop QA commented on HADOOP-11495:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12693990/HADOOP-11495-02.patch
against trunk revision 825923f.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common:
org.apache.hadoop.ha.TestZKFailoverController
The following test timeouts occurred in
hadoop-common-project/hadoop-common:
org.apache.hadoop.ha.TestZKFailoverControllerStress
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5460//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5460//console
This message is automatically generated.
> Convert site documentation from apt to markdown
> -----------------------------------------------
>
> Key: HADOOP-11495
> URL: https://issues.apache.org/jira/browse/HADOOP-11495
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Attachments: HADOOP-11495-02.patch, HADOOP-11496-00.patch,
> HADOOP-11496-01.patch
>
>
> Almost Plain Text (aka APT) lost. Markdown won.
> As a result, there are a ton of tools and online resources for Markdown that
> would make editing and using our documentation much easier. It would be
> extremely beneficial for the community as a whole to move from apt to
> markdown.
> This JIRA proposes to do this migration for the common project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
