[
https://issues.apache.org/jira/browse/HBASE-15872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293730#comment-15293730
]
Matteo Bertozzi commented on HBASE-15872:
-----------------------------------------
The core of the tests run under 2sec, and those should not be flaky.
The stress test is probably the one that shows up in the flaky list since it
does a lot of wal roll
{noformat}
Running org.apache.hadoop.hbase.procedure2.store.wal.TestWALProcedureStore
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.359 sec - in
org.apache.hadoop.hbase.procedure2.store.wal.TestWALProcedureStore
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m;
support was removed in 8.0
Running org.apache.hadoop.hbase.procedure2.store.wal.TestStressWALProcedureStore
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.235 sec - in
org.apache.hadoop.hbase.procedure2.store.wal.TestStressWALProcedureStore
{noformat}
> Split TestWALProcedureStore
> ---------------------------
>
> Key: HBASE-15872
> URL: https://issues.apache.org/jira/browse/HBASE-15872
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Affects Versions: 2.0.0, 1.3.0, 1.2.1
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Trivial
> Attachments: HBASE-15872-v0.patch
>
>
> TestWALProcedureStore shows up in flaky, probably just because inside of it
> there is one stress test that takes most of the time. splitting the
> TestWALProcedureStore from the StressWALProcedureStore so we avoid the proc
> store test not running
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
