[HBASE-6832] [WINDOWS] Tests should use explicit timestamp for Puts, and not rely on implicit RS timing

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.94.3, 0.95.2
• Fix Version/s: 0.95.0
• Labels: windows
• Hadoop Flags: Reviewed
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 19/Sep/12 01:04
• Updated: 23/Sep/13 18:30
• Resolved: 23/Jan/13 19:32

Description

TestRegionObserverBypass.testMulti() fails with

java.lang.AssertionError: expected:<1> but was:<0>
	at org.junit.Assert.fail(Assert.java:93)
	at org.junit.Assert.failNotEquals(Assert.java:647)
	at org.junit.Assert.assertEquals(Assert.java:128)
	at org.junit.Assert.assertEquals(Assert.java:472)
	at org.junit.Assert.assertEquals(Assert.java:456)
	at org.apache.hadoop.hbase.coprocessor.TestRegionObserverBypass.checkRowAndDelete(TestRegionObserverBypass.java:173)
	at org.apache.hadoop.hbase.coprocessor.TestRegionObserverBypass.testMulti(TestRegionObserverBypass.java:166)

Issue Links

• is part of: HBASE-6817 [WINDOWS] Get HBase tests working under Windows
• relates to: HBASE-6833 [WINDOWS] Java Milisecond precision on Windows
• relates to: HBASE-6826 [WINDOWS] TestFromClientSide failures