CI: Fix cancellation workflow API flags, permissions, and filters

[arpittkhandelwal]

Background

This PR contains follow-up fixes for the manual workflow cancellation tool introduced in #7205. While the cancel-ci label and /cancel-ci comment triggers are in place, the script encountered a few GitHub CLI and API limitations in production that caused it to fail.

Errors Fixed

This PR addresses the following issues to make the script fully operational and robust:

1. Precise PR Filtering: Switched from branch-based filtering to a direct GitHub API query (gh api). This ensures that only runs specifically tied to the PR number are cancelled, avoiding any issues with common branch names (e.g., patch-1) or forks.
2. "Resource not accessible" Error: Added issues: write permissions so that gh pr edit can successfully remove the cancel-ci label.
3. Safety & Self-Cancellation: Added set -euo pipefail for strict shell execution and used tonumber in the jq filter to reliably exclude the current run from being cancelled.
4. Pagination Limit: Added --per_page=100 to the API call to ensure all active runs are captured on busy PRs.

Key Code Updates

The core logic now uses the GitHub API for precise targeting:

# Fetch recent runs and filter by the specific PR number
RUN_IDS=$(gh api "/repos/${{ github.repository }}/actions/runs?per_page=100" \
  --jq ".workflow_runs[] | select(.status != \"completed\" and .id != (env.CURRENT_RUN_ID | tonumber) and any(.pull_requests[]; .number == ($PR_NUMBER | tonumber))) | .id")

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[Copilot]

Pull request overview

Follow-up fixes to the manual CI workflow cancellation automation (introduced in #7205) to address GitHub CLI/API limitations encountered in production and make the cancellation tool reliably operational.

Changes:

• Replace unsupported gh run list --pr usage by first resolving the PR head branch and filtering runs via --branch.
• Expand workflow permissions to allow label removal (issues: write) and fix self-exclusion in jq by casting CURRENT_RUN_ID to a number.
• Increase gh run list pagination limit to capture more active runs (--limit 200).

[hkaiser]

@arpittkhandelwal Could you please rebase this onto master? That should resolve most of the CI errors.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[StellarBot]

Performance test report

HPX Performance

Comparison

BENCHMARK	FORK_JOIN_EXECUTOR	PARALLEL_EXECUTOR	SCHEDULER_EXECUTOR
For Each	(=)	(=)	(=)

Info

Property	Before	After
HPX Datetime	2026-03-09T14:08:29+00:00	2026-05-19T16:32:11+00:00
HPX Commit	0eeca86	283e4a5
Envfile
Datetime	2026-03-09T09:15:24.034803-05:00	2026-05-19T21:04:02.405537-05:00
Compiler	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8
Hostname	medusa08.rostam.cct.lsu.edu	medusa08.rostam.cct.lsu.edu
Clustername	rostam	rostam

Comparison

BENCHMARK	NO-EXECUTOR
Future Overhead - Create Thread Hierarchical - Latch	++

Info

Property	Before	After
HPX Datetime	2026-03-09T14:08:29+00:00	2026-05-19T16:32:11+00:00
HPX Commit	0eeca86	283e4a5
Envfile
Datetime	2026-03-09T09:17:15.638328-05:00	2026-05-19T21:06:07.153669-05:00
Compiler	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8
Hostname	medusa08.rostam.cct.lsu.edu	medusa08.rostam.cct.lsu.edu
Clustername	rostam	rostam

Comparison

BENCHMARK	FORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATOR	PARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATOR	SCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATOR
Stream Benchmark - Add	(=)	-	--
Stream Benchmark - Scale	(=)	--	--
Stream Benchmark - Triad	(=)	-	--
Stream Benchmark - Copy	(=)	+++	++

Info

Property	Before	After
HPX Datetime	2026-03-09T18:50:37+00:00	2026-05-19T16:32:11+00:00
HPX Commit	ba89f5d	283e4a5
Envfile
Datetime	2026-03-09T17:49:10.837937-05:00	2026-05-19T21:06:52.301063-05:00
Compiler	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8	/opt/apps/llvm/18.1.8/bin/clang++ 18.1.8
Hostname	medusa08.rostam.cct.lsu.edu	medusa08.rostam.cct.lsu.edu
Clustername	rostam	rostam

Explanation of Symbols

Symbol	MEANING
=	No performance change (confidence interval within ±1%)
(=)	Probably no performance change (confidence interval within ±2%)
(+)/(-)	Very small performance improvement/degradation (≤1%)
+/-	Small performance improvement/degradation (≤5%)
++/--	Large performance improvement/degradation (≤10%)
+++/---	Very large performance improvement/degradation (>10%)
?	Probably no change, but quite large uncertainty (confidence interval with ±5%)
??	Unclear result, very large uncertainty (±10%)
???	Something unexpected…

[hkaiser]

LGTM, thanks!

[hkaiser]

@arpittkhandelwal Have you tested this? And if yes, how?