You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/10/27 15:13:00 UTC
[jira] [Commented] (FLINK-19839) e2e test failures are not causing
the build to fail
[ https://issues.apache.org/jira/browse/FLINK-19839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17221501#comment-17221501 ]
Chesnay Schepler commented on FLINK-19839:
------------------------------------------
Is this what you are referring to?
{code:java}
Oct 27 13:54:12 Waiting for Dispatcher REST endpoint to come up...
Oct 27 13:54:13 Dispatcher REST endpoint has not started within a timeout of 30 sec
Oct 27 13:54:13 Checking of logs skipped.
Oct 27 13:54:13
Oct 27 13:54:13 [PASS] 'Local recovery and sticky scheduling end-to-end test' passed after 0 minutes and 34 seconds! Test exited with exit code 0. {code}
This should fail the test. So it's not that a failed tests is not noticed by the CI scripts, it is that the test does not officially fail.
> e2e test failures are not causing the build to fail
> ---------------------------------------------------
>
> Key: FLINK-19839
> URL: https://issues.apache.org/jira/browse/FLINK-19839
> Project: Flink
> Issue Type: Bug
> Components: Build System / Azure Pipelines
> Affects Versions: 1.12.0
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Priority: Blocker
>
> Example: https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=8373&view=logs&j=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5&t=54421a62-0c80-5aad-3319-094ff69180bb
--
This message was sent by Atlassian Jira
(v8.3.4#803005)