[
https://issues.apache.org/jira/browse/FLINK-31561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703976#comment-17703976
]
Matthias Pohl commented on FLINK-31561:
---------------------------------------
There's still a permission. It seem to have worked temporarily?
{quote}Because the Jenkins was configured to FLINK-30870's branch, I updated
the Jenkins configuration to the master branch on March 15, the new detection
algorithm has not detected any regression recently, so I didn't notice that the
pipeline failed🤦♂️
{quote}
Ah, FLINK-30870 is where the term "cutoff" comes from. :D Just a hint: It's
easier to for investigations to use Jira issues for branch names (or at least
add the Jira issue along the descriptive name) to make it easier investigate
things. :)
> flink-master-regression-check is failing since March 15, 2023
> -------------------------------------------------------------
>
> Key: FLINK-31561
> URL: https://issues.apache.org/jira/browse/FLINK-31561
> Project: Flink
> Issue Type: Bug
> Components: Test Infrastructure
> Affects Versions: 1.18.0
> Reporter: Matthias Pohl
> Assignee: Yanfei Lei
> Priority: Critical
> Labels: pull-request-available
>
> [flink-master-benchmarks-regression-check|http://codespeed.dak8s.net:8080/job/flink-master-benchmarks-regression-check/]
> is failing since March 15, 2023:
> {code}
> Started by timer
> hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune
> origin +refs/heads/cutoff:refs/remotes/origin/cutoff" returned status code
> 128:
> stdout:
> stderr: fatal: Couldn't find remote ref refs/heads/cutoff
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1985)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:80)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:563)
> at
> jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:348)
> at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197)
> at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173)
> at
> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:115)
> at
> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69)
> at
> org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> Finished: FAILURE
> {code}
> As a consequence, no regressions are reported in Slack
--
This message was sent by Atlassian Jira
(v8.20.10#820010)