Warning: Failed to cancel https://github.com/pingcap/dm/actions/runs/766226952

[lance6716]

https://github.com/pingcap/dm/runs/2388157523?check_suite_focus=true

⬆️ This run says it wants to cancel https://github.com/pingcap/dm/actions/runs/766226952 but failed, left a warning. However I see the latter one is stuck in "Queued" status, seems the cancelation somehow taken effects. How could I solve it?

[emabrey]

You may have configured your repository settings to make GITHUB_TOKEN restrictive.

Try adding this permission configuration to the build job you use to run this action:

permissions:
  actions: write
  checks: read
  contents: read
  deployments: read
  issues: read
  discussions: read
  packages: read
  pull-requests: read
  repository-projects: read
  security-events: read
  statuses: read

[jneira]

Hi @emabrey , i am afraid it did not work for me, i've set

permissions:
  actions: write
  pull-requests: write

https://github.com/haskell/haskell-language-server/actions/runs/1398445950/workflow

but the action fails to cancell previous runs:

https://github.com/haskell/haskell-language-server/runs/4045146716?check_suite_focus=true

I suspect it happens if the pr is from a fork (nd most of them are in our case 😟 )

[lance6716]

Hi @jneira , I found cancel-in-progress and that works. I'm closing this issue now.

https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#example-using-concurrency-to-cancel-any-in-progress-job-or-run

[jneira]

@lance6716 thanks for the info, i am little bit confused: that option makes the workflow cancel previous builds on its own (having or no the skip-duplicate-actions) or make skip-duplicate-actions cancel attempts works?

[jneira]

cause if it is the latter, the issue still is reproduced (you are free to close it anyways of course)

[lance6716]

@lance6716 thanks for the info, i am little bit confused: that option makes the workflow cancel previous builds on its own (having or no the skip-duplicate-actions) or make skip-duplicate-actions cancel attempts works?

skip-duplicate-actions is not needed now :P

[jneira]

thanks for the clarification, in our case it is giving us other nicities and we want to keep it though so i am opening another issue