You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:13 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=17174668#comment-17174668 ] 

Beam JIRA Bot commented on BEAM-8090:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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: P2
>              Labels: stale-P2
>          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.3.4#803005)