[
https://issues.apache.org/jira/browse/HADOOP-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532512
]
Hadoop QA commented on HADOOP-1990:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12367099/patch.txt
against trunk revision r581745.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/886/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/886/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/886/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/886/console
This message is automatically generated.
> [hbase] Nightlies #258 and #259 failed
> --------------------------------------
>
> Key: HADOOP-1990
> URL: https://issues.apache.org/jira/browse/HADOOP-1990
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.15.0
> Reporter: stack
> Assignee: Jim Kellerman
> Fix For: 0.15.0
>
> Attachments: patch.txt, patch.txt, patch.txt, patch.txt
>
>
> Looking at the failures in the last two nightlies.
> Looking at #258, the test that failed was same as reported in HADOOP-1964 but
> mode is this time different. The ROOT scanner keeps running but the META has
> disappeared with a log emission. Its probably hung. A misreported missing
> filesystem LOG info (bug) gives wrong impression that the FS has gone. Jim's
> HADOOP-1966 has changed how things work significantly enough that am going to
> pass on further analysis of this failure.
> On #259, Jim has handle on two of the three failed tests. I'm looking at the
> TestDFSAbort...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
