You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jingcheng Du (JIRA)" <ji...@apache.org> on 2016/06/27 05:04:52 UTC
[jira] [Updated] (HBASE-16112) TestFlushSnapshotFromClient is flaky
[ https://issues.apache.org/jira/browse/HBASE-16112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jingcheng Du updated HBASE-16112:
---------------------------------
Summary: TestFlushSnapshotFromClient is flaky (was: TestMobFlushSnapshotFromClient is flaky)
> TestFlushSnapshotFromClient is flaky
> ------------------------------------
>
> Key: HBASE-16112
> URL: https://issues.apache.org/jira/browse/HBASE-16112
> Project: HBase
> Issue Type: Test
> Reporter: Ted Yu
> Assignee: Jingcheng Du
> Priority: Minor
> Attachments: TestFlushSnapshotFromClient-2353.out, TestMobFlushSnapshotFromClient-2353.out, testSnapshotStateAfterMerge-2353.out
>
>
> On recent QA runs, TestMobFlushSnapshotFromClient failed twice.
> https://builds.apache.org/job/PreCommit-HBASE-Build/2360/#showFailuresLink
> https://builds.apache.org/job/PreCommit-HBASE-Build/2353/artifact/patchprocess/patch-unit-hbase-server.txt
> {code}
> org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient.org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient
> Run 1: TestMobFlushSnapshotFromClient>TestFlushSnapshotFromClient.tearDown:123->Object.wait:-2 » TestTimedOut
> Run 2: TestMobFlushSnapshotFromClient.org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient »
> org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient.testSnapshotStateAfterMerge(org.apache.hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient)
> Run 1: TestMobFlushSnapshotFromClient>TestFlushSnapshotFromClient.testSnapshotStateAfterMerge:335->TestFlushSnapshotFromClient.waitRegionsAfterMerge:526 » RetriesExhausted
> Run 2: TestMobFlushSnapshotFromClient>TestFlushSnapshotFromClient.tearDown:123 » InterruptedIO
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)