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

Jonathan Hsieh commented on HBASE-7290:
---------------------------------------

Here's a branch I'm working on currently.
https://github.com/jmhsieh/hbase/commits/snapshot-work-0204

I'm down to this one on the small/medium 

{code}
Running org.apache.hadoop.hbase.client.TestMultiParallel
09:25:53  Tests run: 11, Failures: 2, Errors: 1, Skipped: 0, Time elapsed: 
63.74 sec <<< FAILURE!
{code}

but a whole bunch, many of which seem unrelated, of the large unit tests fail.
{code}
10:39:15  Running org.apache.hadoop.hbase.master.TestRestartCluster
10:39:15  Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
58.153 sec <<< FAILURE!
...
11:25:01  Running org.apache.hadoop.hbase.catalog.TestCatalogTrackerOnCluster
11:25:01  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
26.298 sec <<< FAILURE!

14:20:06  Running 
org.apache.hadoop.hbase.replication.TestReplicationDisableInactivePeer
14:20:06  Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 33.31 
sec <<< FAILURE!
...
{code}

One of the snapshot large test seems to pass for me locally but has a failed a 
few times on my internal jenkins instance.
                
> Online snapshots 
> -----------------
>
>                 Key: HBASE-7290
>                 URL: https://issues.apache.org/jira/browse/HBASE-7290
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>
> HBASE-6055 will be closed when the offline snapshots pieces get merged with 
> trunk.  This umbrella issue has all the online snapshot specific patches.  
> This will get merged once one of the implementations makes it into trunk.  
> Other flavors of online snapshots can then be done as normal patches instead 
> of on a development branch.

--
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

Reply via email to