You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Jan Lukavský (Jira)" <ji...@apache.org> on 2022/01/12 08:18:00 UTC

[jira] [Commented] (BEAM-8090) Add test for Self Setting Timers close to GC TImer

    [ https://issues.apache.org/jira/browse/BEAM-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474350#comment-17474350 ] 

Jan Lukavský commented on BEAM-8090:
------------------------------------

This seems related to 'UsesStrictTimerOrdering' validates runner suites. I think we can close this Jira, because the runners that fail the suite are tracked in separated issues.

> Add test for Self Setting Timers close to GC TImer
> --------------------------------------------------
>
>                 Key: BEAM-8090
>                 URL: https://issues.apache.org/jira/browse/BEAM-8090
>             Project: Beam
>          Issue Type: Test
>          Components: sdk-java-core
>            Reporter: Reza ardeshir rokni
>            Priority: P3
>              Labels: Clarified
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Create test for bug around self setting timers and interaction with GC Timers. Create timer that is a milli behind GC so they likely show up in the same bundle.
> Scenario this is expected to catch:
> If a user timer and the GC timer show up in the same bundle, and the user timer resets itself, and the reset timer is not called (because it had to be committed and then restored), then you have your failure.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)