[
https://issues.apache.org/jira/browse/KAFKA-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032321#comment-18032321
]
Greg F edited comment on KAFKA-19828 at 10/23/25 1:02 AM:
----------------------------------------------------------
Most of the time I run the test, I see this:
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.880 s
– in com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
However, like I mentioned, every once in a while I see this:
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.058 s
<<< FAILURE! – in com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3
[ERROR]
com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3.testChainedWindowedAggregationsWithDifferentGracePeriods
– Time elapsed: 1.049 s <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:633)
at
com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3.testChainedWindowedAggregationsWithDifferentGracePeriods(ChainedEmitStrategyTopologyTest3.java:116)
What that means, most of the time a record passes from input to output topic in
the time expected, but every once in a while it does not.
was (Author: JIRAUSER311223):
Most of the time I run the test, I see this:
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.880 s
-- in com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
However, like I mentioned, every once in a while I see this:
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.058 s
<<< FAILURE! -- in com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3
[ERROR]
com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3.testChainedWindowedAggregationsWithDifferentGracePeriods
-- Time elapsed: 1.049 s <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<0>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:633)
at
com.k8sflowprocessor.ChainedEmitStrategyTopologyTest3.testChainedWindowedAggregationsWithDifferentGracePeriods(ChainedEmitStrategyTopologyTest3.java:116)
> Intermittent test failures when using chained emit strategy on window close
> ---------------------------------------------------------------------------
>
> Key: KAFKA-19828
> URL: https://issues.apache.org/jira/browse/KAFKA-19828
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Greg F
> Priority: Major
> Attachments: ChainedEmitStrategyTopologyTest3.java
>
>
> Hi,
> I have a test case that contains a topology with 2 time windows and chained
> emitStrategy calls. The standalone reproduction use case is attached to this
> issue
> The problem is that about 25% of the time the test fails. About 75% of the
> time the test succeeds. I followed the conclusions of
> !https://issues.apache.org/jira/secure/viewavatar?size=xsmall&avatarId=21133&avatarType=issuetype|width=16,height=16!
> KAFKA-19810
> to make sure that I am sending events at the correct times (at least I think
> my calculations are correct). I really need to get to the bottom of why the
> test fails intermittently, as the test somewhat reflects a real life topology
> of a project I am working on, and we cannot have an intermittently failing
> test in our build pipeline.
> Greg
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
