← Back to issue list

ci: always discard spread workers in snap-store-tests

View original Github issue

Metadata

Project
charmcraft
Number
#2770
Type
pull request
State
closed
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Closed unmerged after no reviews; the equivalent cleanup was merged for main in canonical/charmcraft#2771 via commit ff99aac2.

Resolution: closed superseded

Reason: PR #2770 was abandoned without merge. The same always-run spread-worker cleanup for snap-store-tests landed on main through canonical/charmcraft#2771 in commit ff99aac2.

Evaluated by: mr-cal-bot

No scores available.

Issue body

This PR adds the 'Discard spread workers' cleanup step to the 'snap-store-tests' job in the 'spread.yaml' workflow. Without this step, if the job is cancelled or crashes, the remote Google Cloud VM instances allocated by 'spread' are not discarded, causing them to leak and run until the halt timeout (2h). Adding this step mirrors the cleanup behavior in the other jobs of the workflow.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed superseded Closed unmerged after no reviews; the equivalent cleanup was merged for main in canonical/charmcraft#2771 via commit ff99aac2.
stealth/space-bunny-alpha — closed superseded Abandoned without merge after receiving no reviews; the same spread-worker cleanup was merged for main in canonical/charmcraft#2771.
qwen/qwen3.6-35b-a3b — — Abandoned without merge. The change to add a cleanup step preventing CI VM leaks in snap-store-tests received no reviews and was closed.

Update history

No update history recorded yet.

Related work

Related issues

Issue Project State Summary Similarity
#2771 ci: always discard spread workers in snap-store-tests (main) charmcraft merged Merged PR #2771 (main) adds an always-run "Discard spread workers" cleanup step to the snap-store-tests job in spread.yaml, so cancelled/crashed CI runs no longer leak GCE VMs until the 2h halt timeout.
81%