ci: use self-hosted runners for ci workflows
Metadata
Current evaluation
Changes to use self-hosted runners for CI workflows were closed without merging. Lacking reviews or CI validation, the pull request was likely abandoned.
Suggested action: —
No scores available.
Issue body
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Changes to use self-hosted runners for CI workflows were closed without merging. Lacking reviews or CI validation, the pull request was likely abandoned. | |
| qwen/qwen3.8-27b |
Impact:
5
Quick Win:
4.6
Staleness:
92
Complexity:
8
Confidence:
88
|
close stale | Tiny CI config change (+3/-2, 2 files) to use self-hosted runners. Abandoned for 838 days with 0 comments/reviews. CI infra has since been fully restructured to starflow reusable workflows and explicitly switched back to hosted runners in #1160. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
5
Confidence:
90
|
close stale | Configures CI to use self-hosted runners. Inactive for over a year with no description, CLA, or maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
88
Complexity:
35
Confidence:
85
|
close stale | PR proposes switching CI to self-hosted runners. Opened 2 years ago with no description, comments, or activity for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
35
Confidence:
85
|
close stale | Proposes switching CI workflows to self-hosted runners. Open for over two years with no comments or updates. CI infrastructure evolves rapidly, making this change likely obsolete or superseded. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
|
close stale | Proposes switching CI workflows to self-hosted runners. Open for over two years with no comments or recent activity. CLA remains unsigned. Stalled pending review and contributor agreement completion. |
Update history
| Date | Change |
|---|---|
| closed |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #293 ci: run on self-hosted runners | fetch-service | merged | CI configuration updated to run on self-hosted runners. Merged after approval from two reviewers, modifying one file with 15 additions and 5 deletions. | |
| #359 ci: use hosted runners for QA | craft-cli | merged | Merged update to CI configuration switching QA workflows from self-hosted to GitHub-hosted runners. Enables non-x86 architecture testing. Approved by two reviewers with all CI checks passing. Changes modify one file. | |
| #2325 ci: run heavy workflows less frequently | charmcraft | closed | Closed without merging. The PR to reduce heavy CI workflow frequency was abandoned due to pending review, unresolved comments, and failing CI checks. No configuration changes were applied. | |
| #143 ci: update CI platforms | craft-cli | closed | Closed without merging. The CI platform update received no reviews, comments, or CI checks over 1156 days and was abandoned. | |
| #1160 ci(qa): switch to hosted runners | rockcraft | merged | Merged after approval by two reviewers and passing CI checks. The change switches unit and integration tests to GitHub-hosted runners, resolving external contributor CI issues by standardizing the execution environment. | |
| #1570 ci: split QA workflows by runner | craft-parts | open | Splits QA workflow into separate GitHub-hosted and self-hosted runner files. 117 days old, zero review activity, 11 CI checks failing on self-hosted platforms (s390x, ppc64el, resolute, arm64). Not yet merged; qa.yaml in repo still unsplit. | |
| #385 ci: make the CI run in a standard Ubuntu container | craft-parts | closed | Author closed the pull request without merging, abandoning the attempt to run CI in a standard Ubuntu container. The changes were rejected as they would require a ground-up redo to address Node 18-induced CI failures. |