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

Hadoop QA commented on HADOOP-12160:
------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m  5s | Pre-patch trunk compilation is 
healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:green}+1{color} | tests included |   0m  0s | The patch appears to 
include 10 new or modified test files. |
| {color:green}+1{color} | javac |   7m 46s | There were no new javac warning 
messages. |
| {color:green}+1{color} | release audit |   0m 20s | The applied patch does 
not increase the total number of release audit warnings. |
| {color:green}+1{color} | site |   2m 55s | Site still builds. |
| {color:green}+1{color} | checkstyle |   2m 47s | 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 24s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with 
eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   5m 47s | The patch does not introduce 
any new Findbugs (version 3.0.0) warnings. |
| {color:red}-1{color} | common tests |  22m 11s | Tests failed in 
hadoop-common. |
| {color:green}+1{color} | tools/hadoop tests |   0m 13s | Tests passed in 
hadoop-aws. |
| {color:green}+1{color} | tools/hadoop tests |   0m 13s | Tests passed in 
hadoop-openstack. |
| {color:red}-1{color} | hdfs tests | 172m 32s | Tests failed in hadoop-hdfs. |
| | | 230m 48s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.net.TestNetUtils |
|   | hadoop.ha.TestZKFailoverController |
| Timed out tests | org.apache.hadoop.cli.TestHDFSCLI |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12749521/HADOOP-12160.003.patch 
|
| Optional Tests | site javac unit findbugs checkstyle |
| git revision | trunk / 8f73bdd |
| hadoop-common test log | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7429/artifact/patchprocess/testrun_hadoop-common.txt
 |
| hadoop-aws test log | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7429/artifact/patchprocess/testrun_hadoop-aws.txt
 |
| hadoop-openstack test log | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7429/artifact/patchprocess/testrun_hadoop-openstack.txt
 |
| hadoop-hdfs test log | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7429/artifact/patchprocess/testrun_hadoop-hdfs.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/7429/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.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/7429/console |


This message was automatically generated.

> Add snapshot APIs to the FileSystem specification
> -------------------------------------------------
>
>                 Key: HADOOP-12160
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12160
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: documentation
>    Affects Versions: 2.7.1
>            Reporter: Arpit Agarwal
>            Assignee: Masatake Iwasaki
>         Attachments: HADOOP-12160.002.patch, HADOOP-12160.003.patch
>
>
> The following snapshot APIs should be documented in the [FileSystem 
> specification|https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/filesystem.html].
> # createSnapshot(Path path)
> # createSnapshot(Path path, String snapshotName)
> # renameSnapshot(Path path, String snapshotOldName, String snapshotNewName)
> # deleteSnapshot(Path path, String snapshotName)



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

Reply via email to