← Back to issue list

Add spread test for remote-build

View original Github issue

Metadata

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

Current evaluation

Adding a spread test for remote-build was abandoned. Closed without implementation or discussion, no pull requests were opened, and the task remains unaddressed.

Suggested action:

No scores available.

Issue body

### What needs to get done Add a spread test for the new remote-build. It should run as part of the scheduled spread test workflow. This will require adding a Launchpad token as a Github secret. ### Why it needs to get done There are currently no spread tests for remote-build (new or fallback).

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Adding a spread test for remote-build was abandoned. Closed without implementation or discussion, no pull requests were opened, and the task remains unaddressed.
qwen/qwen3.6-35b-a3b Closed without implementation. The request to add a spread test for remote-build and configure a Launchpad token as a GitHub secret was abandoned. No tests were added or workflow changes merged.
qwen/qwen3.6-35b-a3b Closed without implementation or comments. The request to add a spread test for remote-build and configure a Launchpad token was abandoned.
qwen3.6-35b-a3b-mtp-q6 Closed without implementation. The request to add a spread test for remote-build and configure the required Launchpad token was abandoned after no comments or follow-up activity.
qwen3.6-35b-a3b-mtp-q6 Adding a spread test for remote-build was closed without implementation. Zero comments and no pull requests indicate the request was abandoned. Required GitHub secrets and workflow integration were never configured.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#4433 tests(spread): add remote-build spread test snapcraft merged Merged changes adding spread tests for new and legacy remote-build, resolving issue #4398. Approved by two reviewers with passing CI checks.
80%
#6197 test(spread): debug spread failures 2 snapcraft closed Closed without merging. The author reproduced the failing spread tests in pull request #6198, making this debugging effort redundant and abandoned.
74%
#5054 Add a spread test for registries snapcraft closed Closed without implementation. The request to add a spread test for registries was abandoned, with no pull request or resolution documented beyond an automated Jira sync comment.
70%