← Back to issue list

Migrate or copy core20 and core22 spread tests to core24

View original Github issue

Metadata

Project
snapcraft
Number
#4932
Type
issue
State
closed
Author
mr-cal
Labels
Created
Updated
Closed

Current evaluation

Closed without resolution. No implementation or merge details were provided. Only an automated Jira ticket sync was recorded. The task appears abandoned.

Suggested action:

No scores available.

Issue body

### What needs to get done Migrate or copy existing core20 and core22 spread tests to core24. For example, the core22 "Hello World" plugin tests should be copied to core24. ### Why it needs to get done The spread tests for core24 are not comprehensive. This was agreed to in the 2024-May-13 pulse retrospective.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution. No implementation or merge details were provided. Only an automated Jira ticket sync was recorded. The task appears abandoned.
qwen/qwen3.6-35b-a3b Closed without implementation or merge details, the test migration request was likely abandoned. Only an auto-generated Jira ticket creation was logged, leaving the core20 and core22 spread test expansion unresolved.
qwen/qwen3.6-35b-a3b Abandoned. The request to migrate core20 and core22 spread tests to core24 was closed without implementation, with no associated pull requests or code changes recorded after a Jira sync comment.
qwen3.6-35b-a3b-mtp-q6 Abandoned. The request to migrate core20 and core22 spread tests to core24 was closed without implementation or merge details, remaining only tracked via an internal Jira ticket.
qwen3.6-35b-a3b-mtp-q6 Closed without implementation. The request to migrate core20 and core22 spread tests to core24 was logged as internal Jira ticket CRAFT-3138. No code changes or merges were made, indicating the task was abandoned.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1320 Migrate to core22 charmcraft closed Closed without resolution or associated pull request. The core22 migration was likely abandoned or superseded by a later update, as no implementation or merge details were recorded.
80%