← Back to issue list

feat(snapcraft): snapcraft test action

View original Github issue

Metadata

Project
craft-actions
Number
#56
Type
pull request
State
closed
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Closed without merge due to missing README and pending review. The snapcraft test action remains abandoned.

Suggested action: —

No scores available.

Issue body

This still needs a README file, but otherwise fixes #54 CRAFT-5032

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Closed without merge due to missing README and pending review. The snapcraft test action remains abandoned.
qwen/qwen3.8-27b
Impact: 45
Quick Win: 27.0
Staleness: 70
Complexity: 40
Confidence: 75
close stale Adds a standalone snapcraft/test GitHub Action (2 files, +157 lines) to fix #54; pending review, no comments, 167 days old, many CI test jobs failing. The requested capability was instead folded into snapcraft/pack as a 'test' input in the node-based rewrite (#100).
qwen/qwen3.6-35b-a3b
Staleness: 75
Complexity: 30
Confidence: 80
needs review Adds a snapcraft test action to fix issue #54. Currently pending review with multiple failing CI checks across architectures and an unaddressed README requirement. Inactive for 126 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 40
Confidence: 85
close stale Adds a snapcraft test action to address issue #54. Currently inactive for 113 days, lacks a README, and has zero reviews or comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 65
Complexity: 20
Confidence: 75
needs review Introduces a snapcraft test action to resolve issue #54. Awaiting a README update before merge. Inactive for 91 days with no comments or review activity.

Update history

Date Change
closed

Related issues

Issue Project State Summary Similarity
#1615764 Support snapcraft close snapcraft (launchpad) closed The requested snapcraft close command was closed without implementation. It appears abandoned due to prolonged inactivity, with zero comments or development activity after opening.
75%
#1666908 Create a snapcraft snap snapcraft (launchpad) closed Closed without implementation. The request to package snapcraft as a snap was abandoned after nearly a decade with no comments or follow-up action.
74%
#1448 snapcraft build using manifest.yaml snapcraft closed Closed without discussion or comments. The issue appears abandoned or superseded by newer snapcraft build workflows. No resolution or merge details were recorded.
74%
#1626625 snapcraft can't run tests as part of building a snap snapcraft (launchpad) closed Closed without implementation. The request to add test execution rules to snapcraft received no comments and was abandoned or superseded by newer snapcraft testing features.
73%
#3730 Snapcraft/7.0 snapcraft closed Closed without merging. The Snapcraft 7.0 pull request received zero reviews, comments, or CI checks, and was abandoned.
73%
#1069 snapcraft.yaml and building in snap directory snapcraft closed Closed without merging. The maintainer reviewed the snapcraft.yaml and build directory changes but opted to close the pull request to de-clutter the repository.
72%
#348 checking snapcraft's gh webhook snapcraft closed Closed without merging. The contribution tested snapcraft's GitHub webhook with a two-line change. No reviews, comments, or CI checks were performed. The request was abandoned.
71%
#1636653 During snapcraft releases, we are not testing that important projects continue to build snapcraft (launchpad) closed Closed without implementation. No automated test suite was created to verify critical projects build during snapcraft releases. The request was abandoned after extended inactivity.
71%
#1699 snapcraft <help> command snapcraft closed Closed without implementation or discussion. No resolution or merge details were provided, indicating the snapcraft help command feature request was abandoned.
71%
#202 Add snapcraft tests fetch-service open Feature request to add snapcraft tests for the fetch service snap package using the proposed test framework. Issue is 744 days old with no maintainer engagement beyond an auto-generated Jira sync.
70%