[
https://issues.apache.org/jira/browse/BEAM-8090?focusedWorklogId=341195&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-341195
]
ASF GitHub Bot logged work on BEAM-8090:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Nov/19 08:36
Start Date: 11/Nov/19 08:36
Worklog Time Spent: 10m
Work Description: stale[bot] commented on issue #9429: [BEAM-8090] Create
test for bug around self setting timers
URL: https://github.com/apache/beam/pull/9429#issuecomment-552344510
This pull request has been marked as stale due to 60 days of inactivity. It
will be closed in 1 week if no further activity occurs. If you think that’s
incorrect or this pull request requires a review, please simply write any
comment. If closed, you can revive the PR at any time and @mention a reviewer
or discuss it on the [email protected] list. Thank you for your
contributions.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 341195)
Time Spent: 0.5h (was: 20m)
> 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
> Assignee: Reza ardeshir rokni
> Priority: Major
> Time Spent: 0.5h
> 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)
