-
Notifications
You must be signed in to change notification settings - Fork 10.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport 987087df9002 to release/18.x #79253
Comments
Hi @tstellar, I know release/18.x is just created. May I cherry-pick this fix into 18.x? |
@llvm/issue-subscribers-debuginfo Author: Lu Weining (SixWeining)
/cherry-pick baba7e4
This can address buildbot failures: |
Failed workflow: https://github.com/llvm/llvm-project/actions/runs/7635785866/job/20801796617 I think it's because empty |
I agree. And thanks for the fix. |
Remove the `--phab-token` argument (which currently eats the subsequent "auto" as the token no longer exists) and related code. I think this will fix the workflow failure in #79253 (comment).
/cherry-pick baba7e4 |
Now it fails with (https://github.com/llvm/llvm-project/actions/runs/7638782349/job/20810392396):
I think this is because the workflow is defined with |
Note that the backport branch did get successfully created at https://github.com/llvmbot/llvm-project/tree/issue79253. It failed when posting the issue comment. |
The `/cherry-pick` command needs `issues: write` to post a comment on the issue. The `/branch` command also posts a comment, and also needs `pull-requests: write` to open a PR. This should fix the failure encountered at #79253 (comment).
/cherry-pick baba7e4 |
1 similar comment
/cherry-pick baba7e4 |
/branch llvmbot/llvm-project/issue79253 |
1 similar comment
/branch llvmbot/llvm-project/issue79253 |
Failed to create pull request for issue79253 https://github.com/llvm/llvm-project/actions/runs/7642251632 |
/branch llvmbot/llvm-project/issue79253 |
/pull-request #79323 |
Merged: c9e73cd |
/cherry-pick baba7e4
This can address buildbot failures:
The text was updated successfully, but these errors were encountered: