[KAFKA-6256] Flaky Unit test: KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegionWithNonZeroByteCache

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.1, 1.1.0
• Assignee: Matthias J. Sax
• Reporter: Matthias J. Sax
• Created: 22/Nov/17 01:27
• Updated: 03/Jan/18 19:10
• Resolved: 03/Jan/18 19:09

Description

Expected: <[KeyValue(americas, 101), KeyValue(europe, 109), KeyValue(asia, 124)]>
     but: was <[KeyValue(europe, 13), KeyValue(asia, 25), KeyValue(americas, 23)]>
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:956)
	at org.junit.Assert.assertThat(Assert.java:923)
	at org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest.countClicksPerRegion(KStreamKTableJoinIntegrationTest.java:301)
	at org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegionWithNonZeroByteCache(KStreamKTableJoinIntegrationTest.java:144)

Issue Links

• is duplicated by: KAFKA-6402 KStream Ktable join integration test fails randomly
• links to: GitHub Pull Request #4364