← Back to issue list

CI is failing on the hotfix/2.7 branch

View original Github issue

Metadata

Project
charmcraft
Number
#2510
Type
issue
State
open
Author
lengau
Labels
Status: Triaged Type: Bug
Created
Updated
Closed
—

Current evaluation

CI failing on legacy hotfix/2.7 branch; triaged with Jira ticket CHARMCRAFT-716. No specific failure details. Related #2423 suggests CI partially fixed via PR #2422 and subsequent 2.7.x releases.

Suggested action: keep open

Reason: Issue is triaged (Status: Triaged label) and has an internal Jira ticket (CHARMCRAFT-716), but the body provides no specific failure details, making it hard to act on without investigation. Git log shows 2.7.2, 2.7.3, and 2.7.4 releases were made after related issue #2423, suggesting CI was at least partially working, but this issue remains open and valid for the legacy branch.

Evaluated by: mr-cal-bot

Impact: 35 Quick Win: 6 Complexity: 55 Confidence: 45 Actionability: 35

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request Fix the CI on the `hotfix/2.7` branch ### The problem it solves <!-- Describe the impact your request would have. -->

Evaluation history

Date Model Scores Action Summary
~deepseek/deepseek-pro-latest
Impact: 35
Quick Win: 6
Complexity: 55
Confidence: 45
Actionability: 35
keep open CI failing on legacy hotfix/2.7 branch; triaged with Jira ticket CHARMCRAFT-716. No specific failure details. Related #2423 suggests CI partially fixed via PR #2422 and subsequent 2.7.x releases.
qwen/qwen3.6-35b-a3b
Impact: 10
Quick Win: 2
Complexity: 20
Confidence: 85
Actionability: 30
close resolved CI failing on hotfix/2.7 branch, which has since been merged into main via PR #1742 and released as versions 2.7.0 and 2.7.1.
qwen/qwen3.8-27b
Impact: 10
Quick Win: 8
Staleness: 80
Complexity: 20
Confidence: 80
Support Request: 5
close stale CI failures on the hotfix/2.7 branch, triaged but unresolved. The branch was merged into main via PR #1742 and the project has since advanced to v4.5, making the branch-specific CI issue no longer applicable.
qwen/qwen3.6-35b-a3b
Staleness: 65
Complexity: 20
Confidence: 90
Support Request: 5
keep open CI is failing on the hotfix/2.7 branch. Triaged as a bug by a maintainer, currently awaiting investigation or a fix after a period of inactivity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
close stale CI failure on hotfix/2.7 branch reported by maintainer. No comments or labels. Issue remains open and unaddressed after 213 days of inactivity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 20
Confidence: 75
Support Request: 10
close stale CI is failing on the hotfix/2.7 branch. Open for 210 days with zero comments or labels, awaiting investigation but likely obsolete.

Update history

No update history recorded yet.

Related work

  • Related To: charmcraft#2423 (confidence 85%)

    Same topic (CI fix for 2.7 branch); #2423 references PR #2422 merged to hotfix/2.7 and subsequent 2.7.x releases, suggesting partial resolution.

Related issues

Issue Project State Summary Similarity
#2423 Fix the CI for 2.7 charmcraft open CI repair for the 2.7 hotfix branch was completed by merged PR #2424 after dependency bugfix PR #2422; the tracking issue remains open.
79%
#2511 [WIP] Fix CI issues on hotfix/2.7 branch charmcraft closed PR #2511 was closed unmerged after a maintainer requested a redo from hotfix/2.7; the action upgrades remained incomplete and CI checks failed.
76%