[
https://issues.apache.org/jira/browse/FLINK-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16993437#comment-16993437
]
Till Rohrmann commented on FLINK-15105:
---------------------------------------
Wouldn't this affect all tests which use the {{FailureMapper}}? Moreover, we
would no longer be able to test the behaviour when {{notifyCheckpointComplete}}
fails which imo is a valid case. We would need to check all tests that no other
test uses this feature for any test.
Does the above-mentioned test case rely on the {{isReachedFailureThreshold}} in
the {{map}} function? If not, then one could maybe reconfigure the
{{FailureMapper}} to not throw exceptions at all. Or one extends it so that one
can control that it should not throw exceptions in {{notifyCheckpointComplete}}.
Alternatively, one could change the message of the {{RuntimeException}} to not
contain "error" in it. Then the check should not fail.
> Resuming Externalized Checkpoint after terminal failure (rocks, incremental)
> end-to-end test stalls on travis
> -------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-15105
> URL: https://issues.apache.org/jira/browse/FLINK-15105
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.10.0
> Reporter: Yu Li
> Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0
>
>
> Resuming Externalized Checkpoint after terminal failure (rocks, incremental)
> end-to-end test fails on release-1.9 nightly build stalls with "The job
> exceeded the maximum log length, and has been terminated".
> https://api.travis-ci.org/v3/job/621090394/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
