[ 
https://issues.apache.org/jira/browse/FLINK-30733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706363#comment-17706363
 ] 

Matthias Pohl edited comment on FLINK-30733 at 3/29/23 11:41 AM:
-----------------------------------------------------------------

I opened a 2nd report on the Azure Dev Community which was closed right away 
and merged with the previous bug report. I'm getting a bit tired of following 
up on that one. I'm inclined to close this issue and leave it like that. 

We seem to run into this slack notification issue rather rarely. Severe Flink 
test stability issues should appear more often and, therefore, should be also 
captured with other failed builds. [~martijnvisser] any objections against that 
or ideas how to proceed with that issue?


was (Author: mapohl):
I opened a 2nd report on the Azure Dev Community which was closed right away 
and merged with the previous bug report. I'm getting a bit of following up on 
that one. It feels to not appear that often. I'm inclined to close this issue 
and leave it like that. 

Severe Flink test stability issues should appear more often and, therefore, 
should be also captured with other failed builds. [~martijnvisser] any 
objections against that or ideas how to proceed with that issue?

> The AzureCI Slack bot does not list all failed builds in the Slack channel
> --------------------------------------------------------------------------
>
>                 Key: FLINK-30733
>                 URL: https://issues.apache.org/jira/browse/FLINK-30733
>             Project: Flink
>          Issue Type: Bug
>          Components: Test Infrastructure
>    Affects Versions: 1.16.0, 1.17.0, 1.15.3
>            Reporter: Matthias Pohl
>            Assignee: Martijn Visser
>            Priority: Major
>              Labels: test-stability
>
> We've experienced failing builds not being reported by the AzureCI Slack bot 
> in [Apache Flink/#builds Slack 
> channel|https://apache-flink.slack.com/archives/C03MR1HQHK2].
> Builds affected:
>  * 
> [20230118.2|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44988&view=results]
>  (["manual" Slack 
> thread|https://apache-flink.slack.com/archives/C03MR1HQHK2/p1674032103576869])
>  * 
> [20230113.8|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=44782&view=results]
>  (["manual" Slack 
> thread|https://apache-flink.slack.com/archives/C03MR1HQHK2/p1673615705103309])
>  * 
> [20230119.6|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45044&view=results]
>  (["manual" Slack 
> thread|https://apache-flink.slack.com/archives/C03MR1HQHK2/p1674136551787109])
> * 
> [20230121.1|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45135&view=results]
>  (["manual" Slack 
> thread|https://apache-flink.slack.com/archives/C03MR1HQHK2/p1674546072581919])
> * 
> [20230123.2|https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=45149&view=results]
>  (["manual" Slack 
> thread|https://apache-flink.slack.com/archives/C03MR1HQHK2/p1674546051484829])



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to