[jira] [Resolved] (REEF-1645) Assertion in RuntimeClock.stop() is always true

["Markus Weimer (JIRA)" <ji...@apache.org>]

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

Markus Weimer resolved REEF-1645.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [#1160|https://github.com/apache/reef/pull/1160]

> Assertion in RuntimeClock.stop() is always true
> -----------------------------------------------
>
>                 Key: REEF-1645
>                 URL: https://issues.apache.org/jira/browse/REEF-1645
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF-Common
>            Reporter: Sergiy Matusevych
>            Assignee: Sergiy Matusevych
>            Priority: Trivial
>              Labels: assertion, clock, logging
>             Fix For: 0.16
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In {{RuntimeClock.stop()}}, the assertion for {{numClientAlarms}} is placed immediately *after* its assigment. It should be the other way around.
> It would also be helpful to print the number of outstanding alarms to the log to debug clock idleness/shutdown issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)