[
https://issues.apache.org/jira/browse/FLINK-30015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633577#comment-17633577
]
Yanfei Lei commented on FLINK-30015:
------------------------------------
This was caused by waiting for the available executor.
http://codespeed.dak8s.net:8080/job/flink-master-benchmarks-regression-check/1411/console
{code:java}
Started by timer
Obtained jenkinsfiles/regression-check.jenkinsfile from git
https://github.com/apache/flink-benchmarks.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] timestamps
[Pipeline] {
[Pipeline] timeout
08:38:01 Timeout set to expire in 3 hr 0 min
[Pipeline] {
[Pipeline] node
08:38:16 Still waiting to schedule task
08:38:16 Waiting for next available executor on ‘hetzner EX42-NVMe-1245348’
11:38:01 Cancelling nested steps due to timeout
[Pipeline] // node
[Pipeline] }
[Pipeline] // timeout
[Pipeline] slackSend
11:38:01 Slack Send Pipeline step running, values are - baseUrl: <empty>,
teamDomain: apache-flink, channel: #flink-dev-benchmarks, color: <empty>,
botUser: false, tokenCredentialId: 2d52c4a5-ab95-42f5-b9b7-eb1a1a95b232,
notifyCommitters: false, iconEmoji: <empty>, username: <empty>
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
Finished: SUCCESS {code}
I changed the build trigger to "H 11 * * *" to reduce resource competition.
> Benchmarks are failing
> ----------------------
>
> Key: FLINK-30015
> URL: https://issues.apache.org/jira/browse/FLINK-30015
> Project: Flink
> Issue Type: Bug
> Components: Benchmarks
> Reporter: Martijn Visser
> Priority: Blocker
> Labels: test-stability
>
> {code:java}
> Build interrupted 1411 of flink-master-benchmarks-regression-check (Open):
> org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
> {code}
> Build 1405 until 1411 have all failed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
