You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2019/03/16 03:27:00 UTC

[jira] [Updated] (STORM-3310) JCQueueTest is flaky

     [ https://issues.apache.org/jira/browse/STORM-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim updated STORM-3310:
--------------------------------
    Fix Version/s:     (was: 2.0.1)
                   2.0.0

> JCQueueTest is flaky
> --------------------
>
>                 Key: STORM-3310
>                 URL: https://issues.apache.org/jira/browse/STORM-3310
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Stig Rohde Døssing
>            Assignee: Stig Rohde Døssing
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The JCQueueTest is flaky
> {quote}
> [ERROR]   JCQueueTest.testFirstMessageFirst:61 We expect to receive first published message first, but received null expected:<FIRST> but was:<null>
> {quote}
> The issue is that the test has a race condition. There is no check that the consumer thread has read all (or any) of the produced messages before the test terminates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)