← Back to issue list

CI: remote build tests time out when the build queue is busy

View original Github issue

Metadata

Project
charmcraft
Number
#1566
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

CI remote-build tests timed out on busy Launchpad queue; proposed amd64-only builds, longer timeout, weekly scheduling. All three appear implemented via PRs #1573, #1632, #1705.

Suggested action: close resolved

Reason: All three requested fixes are present in the current codebase: tests/spread/smoketests/remote-build/task.yaml limits architectures to amd64 and sets kill-timeout: 30m, and .github/workflows/spread-manual.yaml runs remote-build on a schedule rather than every PR. Merged PRs #1573, #1632, and #1705 correspond to the amd64 restriction, weekly scheduling, and timeout extension respectively.

Evaluated by: mr-cal-bot

Impact: 30 Quick Win: 19 Complexity: 20 Confidence: 85 Actionability: 80

Issue body

### Bug Description When Launchpad's build queue is busy, the remote build tests will time out in CI. Things we should do in the fix: 1. Modify the init'd charm to only build on & for amd64 (so there's only one build in the queue where Launchpad typically has the most availability) 2. Extend the build time 3. Move the remote build tests to a scheduled weekly test rather than on every PR ### To Reproduce https://github.com/canonical/charmcraft/actions/runs/8096831733/job/22127019796?pr=1560 ### Environment CI ### charmcraft.yaml ```shell n/a ``` ### Relevant log output ```shell n/a ```

Evaluation history

Date Model Scores Action Summary
~deepseek/deepseek-pro-latest
Impact: 30
Quick Win: 19
Complexity: 20
Confidence: 85
Actionability: 80
close resolved CI remote-build tests timed out on busy Launchpad queue; proposed amd64-only builds, longer timeout, weekly scheduling. All three appear implemented via PRs #1573, #1632, #1705.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 19
Complexity: 20
Confidence: 90
Actionability: 80
close resolved Remote build tests were timing out due to busy Launchpad queues. The issue suggested limiting to amd64, extending build time, and moving to weekly scheduled tests. All three fixes have been implemented in the codebase.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 21
Staleness: 55
Complexity: 30
Confidence: 70
Support Request: 0
keep open CI remote build tests time out when Launchpad's build queue is busy. Three fixes requested: limit to amd64, extend build time, move to weekly scheduled test. Two of three are done in the repo (amd64 limit in #1573, weekly move in #1632); only the build-time extension remains unverified.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
needs triage Remote build tests in CI time out due to a busy build queue. Author suggests limiting architecture, extending timeouts, and moving tests to weekly runs. Currently inactive with no maintainer follow-up or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 25
Confidence: 85
Support Request: 0
close stale CI remote build tests time out due to a busy Launchpad build queue. Open for over 2 years with only a Jira sync comment and no maintainer follow-up.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 15
Confidence: 80
Support Request: 5
close stale CI remote build tests time out during busy Launchpad queues. Suggests limiting to amd64, extending timeouts, and moving to weekly scheduling. Unlabelled and inactive for over two years with only automated Jira sync comments.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: charmcraft#1573 (confidence 90%)

    Merged PR limits the remote-build smoke test to one architecture (amd64), matching requested fix #1.

  • Likely Fixed By: charmcraft#1632 (confidence 90%)

    Merged PR moves remote-build tests to a weekly job, matching requested fix #3.

  • Likely Fixed By: charmcraft#1705 (confidence 70%)

    Merged PR extends timeouts for several spread tests; current remote-build task has kill-timeout: 30m, matching requested fix #2.

Related issues

No related issues found above the similarity threshold.