← Back to issue list

`snapcraft remote-build --launchpad-timeout` does not work

View original Github issue

Metadata

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

Current evaluation

Fixed Snapcraft 7 remote-build argument parsing in merged PRs #4426 (c6f41daa8) and #4427 (0054b0cfe), covering the main and fallback builders.

Resolution: closed resolved

Reason: PR #4426 restored --launchpad-timeout parsing for the main builder and was merged as c6f41daa8. Companion PR #4427, merged as 0054b0cfe into hotfix/7.5, fixed the fallback path.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### Bug Description The argument `--launchpad-timeout` for remote-build stopped being accepted when snapcraft 7 was release. Scope of work: 1. Add `--launchpad-timeout` as an argparse argument in `snapcraft/commands/remote.py` 2. Test that it gets passed to the new and fallback remote builders. ### To Reproduce `snapcraft remote-build --launchpad-timeout <seconds>` ### Environment n/a ### snapcraft.yaml ```shell n/a ``` ### Relevant log output ```shell Usage: snapcraft [options] command [args]... Try 'snapcraft remote-build -h' for help. Error: unrecognized arguments: --launchpad-timeout 3600 ``` ### Additional context _No response_

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Fixed Snapcraft 7 remote-build argument parsing in merged PRs #4426 (c6f41daa8) and #4427 (0054b0cfe), covering the main and fallback builders.
stealth/space-bunny-alpha — closed resolved Restored --launchpad-timeout parsing for remote-build in #4426 (c6f41daa8) for the main builder and #4427 (0054b0cfe) for the fallback builder, covering both Snapcraft 7 code paths.
qwen/qwen3.6-35b-a3b — — The --launchpad-timeout argument for snapcraft remote-build was broken in version 7. The issue was closed without resolution, leaving the feature abandoned.
qwen/qwen3.6-35b-a3b — — The --launchpad-timeout argument for snapcraft remote-build was reported as broken after v7. The issue was closed without implementation or a fix, leaving the argument unsupported.
qwen/qwen3.6-35b-a3b — — The --launchpad-timeout argument for snapcraft remote-build was reported as broken in snapcraft 7. The issue was closed without resolution or follow-up, indicating it was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — The --launchpad-timeout argument for snapcraft remote-build was reported as broken in v7. The issue was closed without resolution, indicating it was abandoned due to inactivity.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/snapcraft#4426 (confidence 100%)

    Merged fix restoring --launchpad-timeout parsing for the main remote builder.

  • Likely Fixed By: canonical/snapcraft#4427 (confidence 100%)

    Companion merged fix for the fallback remote builder, released through hotfix/7.5.

Related issues

Issue Project State Summary Similarity
#4426 fix(remote-build): parse `--launchpad-timeout` argument snapcraft merged Merged #4426 as c6f41daa8, restoring --launchpad-timeout parsing for the new remote builder. Companion #4427 fixed the fallback builder, resolving #4397.
80%
#4427 fix(remote-build): parse `--launchpad-timeout` argument snapcraft merged Merged #4427 as 0054b0cfe into hotfix/7.5, restoring parsing of --launchpad-timeout for the fallback remote builder. Companion PR #4426 (c6f41daa8) fixed the main branch code path. Fixes #4397.
78%
#5080 `snapcraft remote-build` succeeds even if the build fails snapcraft closed Fixed in Snapcraft 8 by PR #4826 (commit 552897340), which makes remote-build fail when Launchpad produces no artifacts.
75%
#2845 remote-build: configurable timeout/deadline for starting and monitoring build snapcraft merged PR #2845 merged as ba92ac5f7, restoring --launchpad-timeout as a shared deadline for starting and monitoring remote builds and clarifying timeout failures.
72%