[
https://issues.apache.org/jira/browse/HBASE-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852275#comment-13852275
]
stack commented on HBASE-10203:
-------------------------------
bq. We can see that testLogRollOnPipelineRestart took almost as long as the
other tests combined.
And? This is not reason enough to duplicate all the crazy setup this test has
-- custom config and log4j static configing -- into another test suite making
it harder on those who want to find tests related to log rolling (now they must
look in two places).
Rather than make a new test suite, why not look and figure why the test is
taking so long?
> Separate testLogRollOnPipelineRestart out of TestLogRolling
> -----------------------------------------------------------
>
> Key: HBASE-10203
> URL: https://issues.apache.org/jira/browse/HBASE-10203
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: 10203-v1.txt
>
>
> From
> https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/16/testReport/org.apache.hadoop.hbase.regionserver.wal/TestLogRolling/
> :
> {code}
> testCompactionRecordDoesntBlockRolling 30 sec Passed
> testLogRollOnDatanodeDeath 3 min 19 sec Passed
> testLogRollOnPipelineRestart 6 min 16 sec Passed
> testLogRolling 4 min 27 sec Passed
> {code}
> We can see that testLogRollOnPipelineRestart took almost as long as the other
> tests combined.
> This JIRA separates testLogRollOnPipelineRestart out of TestLogRolling
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
