Limit spread tests to runners that have spread
Metadata
Current evaluation
Spread CI was restricted to self-hosted runners labeled spread-installed by merged PR #1510 (commit 9c98b399), fixing #1463.
Resolution: closed resolved
Reason: PR #1510 merged as commit 9c98b399 and updated Spread workflows to target runners with the spread-installed label, preventing jobs from landing on runners without Spread.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Get an appropriate tag for the self-hosted runners with spread access and limit the spread tests to run on those.
Example:
* Job that has spread: https://github.com/canonical/charmcraft/actions/runs/7401809000/job/20138772548
* Job that failed because it got put on a runner without spread: https://github.com/canonical/charmcraft/actions/runs/7401809000/job/20138772744
### Why it needs to get done
Right now we have to re-run spread tests because they sometimes get put onto runners that don't have spread available
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Spread CI was restricted to self-hosted runners labeled spread-installed by merged PR #1510 (commit 9c98b399), fixing #1463. | |
| stealth/space-bunny-alpha | — | closed resolved | Spread CI was fixed by merged PR #1510 (commit 9c98b399), restricting tests to self-hosted runners labeled spread-installed. | |
| stealth/space-bunny-alpha | — | closed resolved | Spread CI was limited to self-hosted runners labeled spread-installed by merged PR #1510 (9c98b399), preventing tests from landing on runners without spread. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1510 (commit 9c98b399), restricting Spread CI to self-hosted runners labeled spread-installed. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR #1510 (9c98b399), restricting Spread CI to self-hosted runners labeled spread-installed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after a maintainer provided a resolution to tag compatible runners with spread-installed and filter jobs via runs-on: [self-hosted, spread-installed] to prevent failures. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by adding custom labels to self-hosted runners and filtering spread tests with runs-on: [self-hosted, spread-installed] to prevent failures on incompatible runners. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by labeling self-hosted runners with spread access. The fix uses a custom runs-on label in GitHub Actions to restrict spread tests to compatible runners, preventing failures. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved by implementing runner labels to filter spread tests. The maintainer updated the workflow to use runs-on: [self-hosted, spread-installed], ensuring tests only run on compatible runners and eliminating spurious failures. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#1510
(confidence 100%)
Merged PR #1510 explicitly resolves #1463 by restricting Spread jobs to spread-installed runners.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1510 ci(spread): limit github action runners to spread-installed label | charmcraft | merged | Merged PR #1510 (commit 9c98b399) restricted Spread CI to self-hosted runners labeled spread-installed, fixing #1463. | |
| #573 ci: run spread tests on 'spread-installed' runners | rockcraft | merged | Merged PR #573 as commit c8ff5823, updating CI to run Spread tests on runners labeled "spread-installed." | |
| #1453 ci(spread): install spread | charmcraft | closed | PR #1453 (add spread install step to spread CI) was closed unmerged by lengau as unnecessary; #1463 was instead solved by PR #1510 (9c98b399), which restricted spread jobs to self-hosted runners labelled spread-enabled. | |
| #4715 ci: adjust tags for spread runs | snapcraft | merged | Merged PR #4715 updated Spread CI runner tags to allow any machine with the spread-installed tag, preparing Canonical's self-hosted runners. | |
| #524 ci: adjust tags for spread runs | rockcraft | closed | Unmerged CI tag proposal was superseded by #573, where commit c8ff5823 moved Spread tests to self-hosted runners labeled spread-installed. | |
| #571 ci: use self-hosted runners for ci workflows | rockcraft | closed | Closed unmerged and superseded by PR #573, whose commit c8ff5823 moved spread tests to self-hosted runners labeled spread-enabled. | |
| #455 ci(spread): fix runner label ('spread-enabled') | imagecraft | closed | Merged as commit 8d05774, updating the Spread CI runner label from spread-installed to spread-enabled. | |
| #2525 test(spread): enable Ubuntu 25.10 and 26.04 spread runners | charmcraft | merged | Merged PR #2525 as commit 8beb372d, adding Ubuntu 25.10 and 26.04 Spread runners and resolving #2480. | |
| #1526 ci: reduce spread 18.04 runners and increase 22.04 runners | charmcraft | merged | PR #1526 merged as commit ccdd6015, rebalancing .github/workflows/spread.yaml to run fewer Ubuntu 18.04 spread runners and more 22.04 runners, matching where most tests now live. | |
| #495 ci(spread): run spread on all systems | imagecraft | merged | Merged PR #495 as commit 4c5701d, replacing per-system spread matrix limits with backend-wide runs controlled by spread.yaml. |