← Back to issue list

test: CI backend needs to be system-specific

View original Github issue

Metadata

Project
craft-application
Number
#722
Type
issue
State
open
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

CI backend for spread tests needs to be system-specific; references a commit and has an internal Jira ticket (CRAFT-4472) but no maintainer response or labels.

Suggested action: needs triage

Reason: The issue was filed by a maintainer (lengau) with no labels, no assignee, and only an automated Jira-sync bot comment. The referenced commit d4a3eb9 is not found in the current repo history, and the codebase now has a `_get_ci_system()` method and `craft:{ci_system}` prefix logic in `testing.py`, suggesting the system-specific CI backend behavior may already be partially or fully implemented. However, without confirmation that the referenced commit's concern is fully resolved, this needs triage to determine if it's still valid or can be closed as fixed.

Impact: 30 Quick Win: 18.0 Staleness: 75 Complexity: 40 Confidence: 55 Support Request: 10

Issue body

### Bug Description https://github.com/canonical/craft-application/commit/d4a3eb919867d94eaae7522c6f1cf658ee9557d8 ### To Reproduce https://github.com/canonical/craft-application/commit/d4a3eb919867d94eaae7522c6f1cf658ee9557d8 ### part yaml ```shell ``` ### Relevant log output ```shell n/a ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 75
Complexity: 40
Confidence: 55
Support Request: 10
needs triage CI backend for spread tests needs to be system-specific; references a commit and has an internal Jira ticket (CRAFT-4472) but no maintainer response or labels.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 15
Confidence: 85
Support Request: 10
close stale CI backend test configuration issue requesting system-specific setup. Over 14 months old with no maintainer engagement or updates.
qwen3.6-35b-a3b-mtp-q6
Staleness: 92
Complexity: 15
Confidence: 80
Support Request: 0
close stale CI backend configuration requires system-specific handling. The issue is over 15 months old, lacks maintainer engagement, and provides only a commit link without clear reproduction steps or current relevance.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 10
close stale CI backend requires system-specific configuration to resolve test failures. Open with no labels or developer activity, last updated by a Jira sync bot over a year ago. Requires triage and assignment to fix the CI pipeline dependency.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: craft-application#733 (confidence 60%)

    Commit e9dd8274 'fix(services/testing): set system for ci backend (#733)' directly addresses setting the system for the CI backend, which aligns with this issue's title.

  • Related To: craft-application#1155 (confidence 40%)

    Commit c8a68947 'test(spread): add Ubuntu 26.04/26.10 support to spread backends (#1155)' is a more recent change to spread backend systems, indicating ongoing work in this area.

Related issues

No related issues found above the similarity threshold.