You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2019/02/26 00:52:02 UTC

[jira] [Updated] (SAMZA-2036) MessageStreamAssert.containsInAnyOrder does not fail if there is an error

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

Jake Maes updated SAMZA-2036:
-----------------------------
    Fix Version/s: 1.0.1
                   1.0.1

> MessageStreamAssert.containsInAnyOrder does not fail if there is an error
> -------------------------------------------------------------------------
>
>                 Key: SAMZA-2036
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2036
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Cameron Lee
>            Priority: Major
>             Fix For: 1.0.1
>
>
> MessageStreamAssert.containsInAnyOrder uses a java.util.Timer to do verification. However, Timer will do the check in a background thread, and any error/exception does not get propagated to the main thread for the test. Therefore, any error will not cause a test to fail, so a test will pass even if there is an issue.
> In addition, the MessageStreamAssert.CheckAgainstExpected helper class is broken, since the "expected" messages get cleared out when the operator graph is serialized then deserialized, and an NPE is thrown when trying to run "apply". This is already covered in https://issues.apache.org/jira/browse/SAMZA-1829.
> SchedulingTest and TestRepartitionJoinWindowApp both use MessageStreamAssert.containsInAnyOrder, and they pass, but they should fail.



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