You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@flink.apache.org by Flink CI <fl...@foxmail.com> on 2020/02/08 04:30:59 UTC

Broken: apache/flink#42442 (release-1.10 - 1268a7b)

|  [

apache

/

flink

](https://travis-ci.org/apache/flink)  
---  
  
![branch icon](https://s3.amazonaws.com/travis-email-
assets/branch.png)[release-1.10](https://github.com/apache/flink/tree/release-1.10)  
  
|

![build hasfailed](https://s3.amazonaws.com/travis-email-assets/status-
failed.png)

[Build #42442 broken](https://travis-ci.org/apache/flink/builds/647452233)

![arrow to build time](https://s3.amazonaws.com/travis-email-assets/failure-
arrow.png)

![clock icon](https://s3.amazonaws.com/travis-email-assets/time.png)56 mins, 2
secs  
  
---  
  
![Gary Yao
avatar](https://secure.gravatar.com/avatar/25db1a9ed476c1ba032f95181c534a0a.jpg)Gary
Yao

[1268a7b CHANGESET
->](https://github.com/apache/flink/compare/cea09a8bd8d3...1268a7b9a3a3)  
  
[FLINK-15918][runtime] Fix that 'uptime' metric is not reset after restart  
  
The 'uptime' metric is the time difference between 'now' and the timestamp
when  
the job transitioned to state RUNNING. The new scheduler until now never  
transitioned out of status RUNNING when restarting tasks which had the effect  
that the 'uptime' metric was not reset after a restart. This introduces new  
state transitions to the job. We transition the job status to RESTARTING if at  
least one ExecutionVertex is waiting to be restarted, and we transition from  
RESTARTING immediately to RUNNING again after the restart.  
  
This closes #11032.