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

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/06/15 05:57:02 UTC

[GitHub] [flink] zentol commented on pull request #19957: [FLINK-28052][tests] Remove RunFailedJobListener

zentol commented on PR #19957:
URL: https://github.com/apache/flink/pull/19957#issuecomment-1156020082

   > But I don't understand why it's important to know that one test issues task restarts for the old implementation to be kind of reasonable?
   
   It doesn't make sense because it's not even doing what it says on the tin.
   What it looks like the test is doing is completing some job cancellation (that came from _somewhere_) and waiting for it to reach a terminal state.
   
   In case of the restarting test, it just completes the restart (==acknowledging the cancel requests). The job actually keeps running. Which is then covered by this special case in the listener where we consider it terminal if it restarted.


-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org