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 2019/12/16 06:53:36 UTC

[GitHub] [flink] klion26 opened a new pull request #10588: [FLINK-15105][test] Resuming Externalized Checkpoint after terminal failure (rocks, incremental) end-to-end test stalls on travis

klion26 opened a new pull request #10588: [FLINK-15105][test] Resuming Externalized Checkpoint after terminal failure (rocks, incremental) end-to-end test stalls on travis
URL: https://github.com/apache/flink/pull/10588
 
 
   ## What is the purpose of the change
   
   Skip all the exception_checks when running `test_resume_externalized_checkpoints.sh`
   
   Currently, when running `test_resume_externalized_checkpoints.sh`, we'll throw Exception in `FailureMapper#map` and `FailureMapper#notifyCheckpointComplete`, if the `Artificail Exception` was thrown in `FailureMapper#map` the test will fail because the log contains error/exception. In another hand, the correctness of the execution is verified by the test itself, so we disable the exception check in `test_resume_externalized_checkpoints.sh` here.
   
   ## Verifying this change
   
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services