snapcraft tiggers jammy/nobel/resolute backend tests on resolute GH runner

Metadata

Project: snapcraft
Number: #6526
Type: issue
State: open
Author: taurus-forever
Labels: —
Created: 2026-10-28 07:07 PM UTC
Updated: 2026-10-28 07:08 PM UTC
Closed: —

Current evaluation

snapcraft triggers all backend tests (Jammy, Noble, Resolute) on Resolute GH runner instead of only Resolute backend. Issue is open, unlabelled, and awaiting maintainer triage.

Suggested action: needs triage

Reason: This is a new, unlabelled issue with no maintainer response. The bug is clearly described with specific CI log evidence showing that on a Resolute GH runner, snapcraft allocates craft:ubuntu-22.04, craft:ubuntu-26.04, and craft:ubuntu-24.04 instead of only craft:ubuntu-26.04 as expected. The template at snapcraft/templates/test/spread.yaml.j2 shows the craft backend configuration, but the root cause in the backend allocation logic needs investigation by a maintainer.

Evaluated by: mr-cal-bot

Impact: 60 Quick Win: 24 Complexity: 50 Confidence: 75 Actionability: 80

Issue body

### Check existing issues - [x] I've verified that this bug isn't described by any existing issues. ### Bug description Hi, Issue: normally snapcraft tiggers jammy-backend tests only on `Jammy` GH runner. Same for `Noble`. The same time snapcraft tiggers jammy+nobel+resolute backend tests on `Resolute` GH runner Example: see the PR changes https://github.com/canonical/postgresql-snap/pull/165/changes On CI/CD site: * [22.04 Jammy GH runner](https://github.com/canonical/postgresql-snap/actions/runs/31679241742/job/94381686578#step:5:130): ``` :: 2026-08-13 07:56:45 Allocating craft:ubuntu-22.04... # as expected. OK. ``` * [24.04 Noble GH runner](https://github.com/canonical/postgresql-snap/actions/runs/31679241742/job/94381686641#step:5:131): ``` :: 2026-08-13 07:56:39 Allocating craft:ubuntu-24.04... # as expected. OK. ``` * [26.04 Resolute GH runner](https://github.com/canonical/postgresql-snap/actions/runs/31679241742/job/94381686640#step:5:133): ``` :: 2026-08-13 07:55:44 Allocating craft:ubuntu-22.04... # Not OK. Why? :: 2026-08-13 07:55:44 Allocating craft:ubuntu-26.04... # OK (the only one expected to be triggered). :: 2026-08-13 07:55:44 Allocating craft:ubuntu-24.04... # Not OK. Why? ``` ### Steps to reproduce Try to tests snap on many backends (to guaranty core26 snap be deployed to Jammy host, UbuntuCore, etc). See/use [postgresql-snap](https://github.com/canonical/postgresql-snap/blob/16/edge/spread.yaml#L6-L9) as a example. Goal: test all backends on localhost "snapcraft test" and matrix them on GH CI/CD for better retry story there. ### Environment > snap list snapcraft Name Version Rev Tracking Publisher Notes snapcraft 9.2.1.post13 19458 latest/edge canonical✓ classic ### snapcraft.yaml ```yaml https://github.com/canonical/postgresql-snap/blob/16/edge/snap/snapcraft.yaml ``` ### Log output ```shell No logs. GH CI linked in the bugreport. ```

Evaluation history

Date	Model	Scores	Action	Summary
2026-11-01 01:02 PM UTC	qwen/qwen3.6-35b-a3b	Impact: 60 Quick Win: 24 Complexity: 50 Confidence: 75 Actionability: 80	needs triage	snapcraft triggers all backend tests (Jammy, Noble, Resolute) on Resolute GH runner instead of only Resolute backend. Issue is open, unlabelled, and awaiting maintainer triage.

Update history

Date	Change
2026-10-28 07:08 PM UTC	created

Related issues

No related issues found above the similarity threshold.