[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15850287#comment-15850287
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/2485


> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Sub-task
>  Components: unit tests
>Reporter: Ashish Singh
>Assignee: Guozhang Wang
> Fix For: 0.10.2.0, 0.10.3.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849536#comment-15849536
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

GitHub user guozhangwang opened a pull request:

https://github.com/apache/kafka/pull/2485

KAFKA-3896: Fix KStream-KStream leftJoin

The issue of transiently having duplicates is due to the bad design of the 
left join itself: in order to ignore the partial joined results such as 
`A:null`, it lets the producer to potentially send twice to source stream one 
and rely on all the following conditions to be true in order to pass the test:

1. `receiveMessages` happen to have fetched all the produced results and 
have committed offsets.
2. streams app happen to have completed sending all result data.
3. consumer used in `receiveMessages` will complete getting all messages in 
a single poll().

If any of the above is not true, the test fails.

Fixed this test to add a filter right after left join to filter out partial 
joined results. Minor cleanup on integration test utils.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/guozhangwang/kafka 
K3896-duplicate-join-results

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2485.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2485


commit 186c32075bb8cab217dddeb23aa341fb3ac5e5d0
Author: Guozhang Wang 
Date:   2017-02-02T06:51:57Z

fix left join




> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Sub-task
>  Components: unit tests
>Reporter: Ashish Singh
>Assignee: Guozhang Wang
> Fix For: 0.10.2.0, 0.10.3.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836546#comment-15836546
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/2405


> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Sub-task
>  Components: unit tests
>Reporter: Ashish Singh
>Assignee: Guozhang Wang
> Fix For: 0.10.2.0, 0.10.3.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Guozhang Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15831285#comment-15831285
 ] 

Guozhang Wang commented on KAFKA-3896:
--

The root cause of this issue is that before 
https://github.com/apache/kafka/pull/2389, we use delete-and-recreate with 
{{StreamsKafkaClient}}, and due to a bad design pattern, we are creating and 
deleting topics one-at-a-time, for this test, there are 12 topics to be 
created, and each creating call will need to be coupled with a delete call with 
empty topic list as always, as a result it is possible that the consumer could 
time out during the assignment in rebalance, and the next leader has to do the 
same again because of "makeReady" calls are one-at-a-time.

PR https://github.com/apache/kafka/pull/2389 remedies this problem as we are 
not calling delete any more and that is why we have not seen this issue after 
this PR. However we still need to make the {{InternalTopicManager}} more 
efficient.

> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Sub-task
>  Components: unit tests
>Reporter: Ashish K Singh
>Assignee: Guozhang Wang
> Fix For: 0.10.1.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829310#comment-15829310
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

GitHub user guozhangwang opened a pull request:

https://github.com/apache/kafka/pull/2405

KAFKA-3896: Fix KStreamRepartitionJoinTest [WIP]



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/guozhangwang/kafka 
K3896-fix-kstream-repartition-join-test

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/2405.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2405


commit 3fb4e84a7e270fa6e7b1e9ad654cc00968e314e2
Author: Guozhang Wang 
Date:   2017-01-19T04:40:08Z

minor changes for jenkins builds




> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Sub-task
>  Components: unit tests
>Reporter: Ashish K Singh
>Assignee: Guozhang Wang
> Fix For: 0.10.1.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Guozhang Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15826752#comment-15826752
 ] 

Guozhang Wang commented on KAFKA-3896:
--

Another instance: 
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/929/testReport/junit/org.apache.kafka.streams.integration/KStreamRepartitionJoinTest/shouldCorrectlyRepartitionOnJoinOperations_1_/

{code}
Stacktrace

java.lang.AssertionError: Condition not met within timeout 6. Did not 
receive 5 number of records
at org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:259)
at 
org.apache.kafka.streams.integration.utils.IntegrationTestUtils.waitUntilMinValuesRecordsReceived(IntegrationTestUtils.java:259)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.receiveMessages(KStreamRepartitionJoinTest.java:381)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.verifyCorrectOutput(KStreamRepartitionJoinTest.java:291)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations(KStreamRepartitionJoinTest.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Guozhang Wang (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15819555#comment-15819555
 ] 

Guozhang Wang commented on KAFKA-3896:
--

{code}
java.lang.AssertionError: Condition not met within timeout 6. Did not 
receive 5 number of records
at org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:259)
at 
org.apache.kafka.streams.integration.utils.IntegrationTestUtils.waitUntilMinValuesRecordsReceived(IntegrationTestUtils.java:253)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.receiveMessages(KStreamRepartitionJoinTest.java:401)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.verifyCorrectOutput(KStreamRepartitionJoinTest.java:311)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations(KStreamRepartitionJoinTest.java:145)
{code}

See another occurrence of this failure, re-opening.

> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Bug
>  Components: unit tests
>Reporter: Ashish K Singh
>Assignee: Damian Guy
> Fix For: 0.10.1.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Philippe Derome]

Never mind sorry. I should research this on my own.
On 27 Jun 2016 3:29 p.m., "Philippe Derome"  wrote:

> Guozhang, all on this thread,
>
> I've been spending a fair amount looking at this problem very indirectly
> with my PR for KAFKA-3902. I had 3 commits on the PR and the last one fails
> on Jenkins for this unit test here:
> https://github.com/apache/kafka/pull/1556
>
> Additionally, that particular file KStreamRepartitionJoinTest.java is not
> in my local repo and I cannot seem to resolve merge conflicts between my
> local repo and trunk (I admit to be unfamiliar with git commands, which is
> possibly the main issue).
>
> Is it possible for anyone to validate that my PR is actually reasonably
> sensible despite that unit test failure?
>
> Thanks,
>
> Phil
>
> On Mon, Jun 27, 2016 at 2:51 PM, ASF GitHub Bot (JIRA) 
> wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351603#comment-15351603
>> ]
>>
>> ASF GitHub Bot commented on KAFKA-3896:
>> ---
>>
>> Github user asfgit closed the pull request at:
>>
>> https://github.com/apache/kafka/pull/1549
>>
>>
>> > Unstable test
>> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
>> >
>> ---
>> >
>> > Key: KAFKA-3896
>> > URL: https://issues.apache.org/jira/browse/KAFKA-3896
>> > Project: Kafka
>> >  Issue Type: Bug
>> >  Components: unit tests
>> >Reporter: Ashish K Singh
>> >Assignee: Damian Guy
>> > Fix For: 0.10.1.0
>> >
>> >
>> >
>> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}}
>> seems to be unstable. A failure can be found [here|
>> https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not
>> reproduce the test failure locally though.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v6.3.4#6332)
>>
>
>

Re: [jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Philippe Derome]

Guozhang, all on this thread,

I've been spending a fair amount looking at this problem very indirectly
with my PR for KAFKA-3902. I had 3 commits on the PR and the last one fails
on Jenkins for this unit test here:
https://github.com/apache/kafka/pull/1556

Additionally, that particular file KStreamRepartitionJoinTest.java is not
in my local repo and I cannot seem to resolve merge conflicts between my
local repo and trunk (I admit to be unfamiliar with git commands, which is
possibly the main issue).

Is it possible for anyone to validate that my PR is actually reasonably
sensible despite that unit test failure?

Thanks,

Phil

On Mon, Jun 27, 2016 at 2:51 PM, ASF GitHub Bot (JIRA) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351603#comment-15351603
> ]
>
> ASF GitHub Bot commented on KAFKA-3896:
> ---
>
> Github user asfgit closed the pull request at:
>
> https://github.com/apache/kafka/pull/1549
>
>
> > Unstable test
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> >
> ---
> >
> > Key: KAFKA-3896
> > URL: https://issues.apache.org/jira/browse/KAFKA-3896
> > Project: Kafka
> >  Issue Type: Bug
> >  Components: unit tests
> >Reporter: Ashish K Singh
> >Assignee: Damian Guy
> > Fix For: 0.10.1.0
> >
> >
> >
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}}
> seems to be unstable. A failure can be found [here|
> https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not
> reproduce the test failure locally though.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351603#comment-15351603
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/1549


> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Bug
>  Components: unit tests
>Reporter: Ashish K Singh
>Assignee: Damian Guy
> Fix For: 0.10.1.0
>
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347889#comment-15347889
 ] 

ASF GitHub Bot commented on KAFKA-3896:
---

GitHub user dguy opened a pull request:

https://github.com/apache/kafka/pull/1549

KAFKA-3896: Unstable test 
KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

@ijuma i checked the cases where this test has failed and it seems to 
always be on the verification of the left join. I've ran this test plenty of 
times and i can't get it to fail. However in the interest of having stable 
builds, i've removed just the part of the test that is failing (which happens 
to be the last verification).
Thanks,
Damian

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dguy/kafka kafka-3896

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1549.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1549


commit 3827d91345c5a166512cc12633f8879ad4896436
Author: Damian Guy 
Date:   2016-06-24T07:09:51Z

remove verify left join from KStreamRepartitionJoinTest as it is causing 
transitive build failures




> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Bug
>  Components: unit tests
>Reporter: Ashish K Singh
>Assignee: Damian Guy
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[Ismael Juma (JIRA)]

[ 
https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347154#comment-15347154
 ] 

Ismael Juma commented on KAFKA-3896:


Including the error message as Jenkins jobs are deleted periodically.

{code}
Expected: is <[1:A, 2:B, 3:C, 4:D, 5:E]>
 but: was <[1:null, 2:null, 3:null, 4:null, 5:null]>
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.verifyCorrectOutput(KStreamRepartitionJoinTest.java:425)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.verifyLeftJoin(KStreamRepartitionJoinTest.java:337)
at 
org.apache.kafka.streams.integration.KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations(KStreamRepartitionJoinTest.java:137)
{code}

> Unstable test 
> KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations
> ---
>
> Key: KAFKA-3896
> URL: https://issues.apache.org/jira/browse/KAFKA-3896
> Project: Kafka
>  Issue Type: Bug
>  Components: unit tests
>Reporter: Ashish K Singh
>
> {{KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations}} 
> seems to be unstable. A failure can be found 
> [here|https://builds.apache.org/job/kafka-trunk-git-pr-jdk7/4363/]. Could not 
> reproduce the test failure locally though.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)