beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <>
Subject [jira] [Updated] (BEAM-3599) kinesis.ShardReadersPoolTest.shouldInterruptKinesisReadingAndStopShortly is flaky
Date Tue, 06 Feb 2018 17:58:00 GMT


Kenneth Knowles updated BEAM-3599:
    Labels: sickbay  (was: flake)

> kinesis.ShardReadersPoolTest.shouldInterruptKinesisReadingAndStopShortly is flaky
> ---------------------------------------------------------------------------------
>                 Key: BEAM-3599
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-extensions
>            Reporter: Thomas Groh
>            Assignee: Alexey Romanenko
>            Priority: Critical
>              Labels: sickbay
> This appears to be unavoidable due to the construction of the test - the amount of realtime
that the thread waits is asserted to be less than one second, but as the class doesn't consume
a {{Ticker}} (or related way to track elapsed time), we have no way of deterministically controlling
that value within the test.
> Example failure: []
> {{java.lang.AssertionError: Expecting: <4169L> to be less than: <1000L> at
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)}} 
> The test could also do with a more precise error message (it looks like too many elements
were received based on the error message, rather than the actual "took too long" failure.

This message was sent by Atlassian JIRA

View raw message