[
https://issues.apache.org/jira/browse/FLINK-33052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764581#comment-17764581
]
Piotr Nowojski edited comment on FLINK-33052 at 9/13/23 10:28 AM:
------------------------------------------------------------------
We have been always treating benchmarking issues the same way as regular test
issues. If CI for tests was down, that would have been a clear blocker,
preventing everyone from merging any code, doing any releases. The same applies
for benchmarking, the only difference is that benchmarks are asynchronous and
not executed per every PR due to load that they are generating.
Some of the past examples:
FLINK-23153, FLINK-23879, FLINK-29886, FLINK-30015, FLINK-15171
Also as far as I remember that has been discussed on the dev mailing list at
least once or twice.
was (Author: pnowojski):
We have been always treating benchmarking issues the same way as regular test
issues. If CI for tests was down, that would have been a clear blocker,
preventing everyone from merging any code, doing any releases. The same applies
for benchmarking, the only difference is that benchmarks are asynchronous and
not executed per every PR due to load that they are generating.
> codespeed server is down
> ------------------------
>
> Key: FLINK-33052
> URL: https://issues.apache.org/jira/browse/FLINK-33052
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks, Test Infrastructure
> Affects Versions: 1.18.0
> Reporter: Jing Ge
> Assignee: Zakelly Lan
> Priority: Blocker
>
> No update in #flink-dev-benchmarks slack channel since 25th August.
> It was a EC2 running in a legacy aws account. Currently on one knows which
> account it is.
>
> https://apache-flink.slack.com/archives/C0471S0DFJ9/p1693932155128359
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
