You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mark Robert Miller (Jira)" <ji...@apache.org> on 2020/02/13 11:12:00 UTC
[jira] [Updated] (HBASE-23835) TestFromClientSide3 and subclasses
often fail on testScanAfterDeletingSpecifiedRowV2.
[ https://issues.apache.org/jira/browse/HBASE-23835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Robert Miller updated HBASE-23835:
---------------------------------------
Description:
This test method fails a fair amount on me with something like:
TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:236 expected:<3> but was:<2>
I had a hunch that it might be due to interference from other test methods running first so I tried changing the table name for just this method to be unique - still fails.
However, when I just run
was:
This test method fails a fair amount on me with something like:
> TestFromClientSide3 and subclasses often fail on testScanAfterDeletingSpecifiedRowV2.
> -------------------------------------------------------------------------------------
>
> Key: HBASE-23835
> URL: https://issues.apache.org/jira/browse/HBASE-23835
> Project: HBase
> Issue Type: Test
> Affects Versions: master
> Reporter: Mark Robert Miller
> Priority: Major
>
> This test method fails a fair amount on me with something like:
> TestFromClientSide3WoUnsafe>TestFromClientSide3.testScanAfterDeletingSpecifiedRowV2:236 expected:<3> but was:<2>
> I had a hunch that it might be due to interference from other test methods running first so I tried changing the table name for just this method to be unique - still fails.
> However, when I just run
--
This message was sent by Atlassian Jira
(v8.3.4#803005)