timeout if doing snapcraft pull and build seperately
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
A report detailing a hang when running snapcraft pull and build separately was closed without comments or resolution, indicating it was abandoned. No fix or workaround was provided.
Suggested action: —
No scores available.
Issue body
I am building a snap using snapcraft version 7.2.9 and lxd 5.11-ad0b61e and if I trigger the build by simply executing 'snapcraft' it works. However if I do 'snapcraft pull; snapcraft;' it never completes and seems to hang on "Running build phase..." indefinitely. I am using a Launchpad snap recipe to build my snap for multiple architectures and am no longer able to do so. It appears that this behaviour started after I upgraded the snap to use core22 (previously core20).
From LP:
...
Executing action
Executed: pull patchelf
Executed parts lifecycle
Running build phase...
Error: websocket: close 1006 (abnormal closure): unexpected EOF
Build failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 269, in run
self.build()
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 253, in build
self.run_build_command(["snapcraft"], cwd=output_path, env=env)
File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 62, in run_build_command
return self.backend.run(args, cwd=cwd, env=full_env, **kwargs)
File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 730, in run
subprocess.check_call(cmd, **kwargs)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-jammy-amd64', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'http_proxy=http://10.10.10.1:8222/', '--env', 'https_proxy=http://10.10.10.1:8222/', '--env', 'GIT_PROXY_COMMAND=/usr/local/bin/lpbuildd-git-proxy', '--env', 'SNAPPY_STORE_NO_CDN=1', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build-request-id": "lp-77700990", "build-request-timestamp": "2023-02-24T13:43:42Z", "build_url": "https://launchpad.net/~hopem/hotsos/+snap/hotsos/+build/2032346"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--env', 'SNAPCRAFT_BUILD_FOR=amd64', '--', '/bin/sh', '-c', 'cd /build/hotsos && linux64 snapcraft']' returned non-zero exit status 1.
Revoking proxy token...
RUN: /usr/share/launchpad-buildd/bin/in-target scan-for-processes --backend=lxd --series=jammy --arch=amd64 SNAPBUILD-2032346
Scanning for processes to kill in build SNAPBUILD-2032346
If I try locally I get the same:
$ snapcraft pull
Launching instance...
Executed: pull hotsos
Executed: pull patchelf
Executed parts lifecycle
$ snapcraft
Launching instance...
Initializing parts lifecycle \ (505.3s)
I checked and it has successfully created the build container:
$ lxc list --project snapcraft
+----------------------------------------------+---------+-----------------------+------+-----------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+----------------------------------------------+---------+-----------------------+------+-----------+-----------+
| snapcraft-hotsos-on-amd64-for-amd64-29493175 | RUNNING | 10.205.190.104 (eth0) | | CONTAINER | 0 |
+----------------------------------------------+---------+-----------------------+------+-----------+-----------+
It just never completes.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | A report detailing a hang when running snapcraft pull and build separately was closed without comments or resolution, indicating it was abandoned. No fix or workaround was provided. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report described a hang when running snapcraft pull and build separately, but received no comments or fixes before closure. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report describes a hang when running snapcraft pull and build separately on core22, but no comments, fixes, or resolution details were provided. Likely closed due to inactivity. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1688151 snapcraft pull doesn't save the installed build dependencies | snapcraft (launchpad) | closed | Closed without comments or resolution. The bug where snapcraft pull omitted build package dependencies from the pull state file was abandoned. | |
| #1591563 snapcraft gets stuck with getting cloudfoundry cli | snapcraft (launchpad) | closed | Closed without comments or resolution details, likely abandoned. The report described snapcraft hanging during a Go source pull for the cloudfoundry-cli package. | |
| #1647139 CalledProcessError: Command '['/usr/bin/sudo', '/usr/sbin/chroot', '/home/buildd/build-SNAPBUILD-12520/chroot-autobuild', 'linux64', '/bin/sh', '-c', 'cd /build/qucs-spice && env LANG=C.UTF-8 https_proxy=http://snap-proxy.launchpad.net:3128 http_proxy=http://snap-proxy.launchpad.net:3128 SNAPCRAFT_LOCAL_SOURCES=1 snapcraft pull']' returned non-zero exit status 1 | snapcraft (launchpad) | closed | A snapcraft build failure during the pull stage was closed without resolution. The report was abandoned due to prolonged inactivity, with no comments or fixes provided. | |
| #1957915 Cleaning later steps and re-pulling with snapcraft 6.0.1 | snapcraft (launchpad) | closed | Abandoned. The report described repeated part pulls during snapcraft 6.0.1 builds, but received no comments or patches to address the issue. | |
| #1869505 Snapcraft is pulling content snap before building a snap | snapcraft (launchpad) | closed | Closed as abandoned. The report detailed snapcraft unnecessarily pulling content snaps before building, causing high resource usage. No discussion, fixes, or follow-up occurred. | |
| #1675516 can't cleanbuild snapcraft itself | snapcraft (launchpad) | closed | Closed without resolution or comments, the report of a failed snapcraft cleanbuild due to missing build-packages was abandoned. | |
| #1746359 snapcraft cleanbuild --debug should provide guidance on build failure | snapcraft (launchpad) | closed | Closed as abandoned due to inactivity. The requested debug shell guidance for snapcraft cleanbuild was never implemented. | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | Closed without resolution. The report details a PermissionError during snapcraft cleanbuild caused by restricted access to the .aptitude directory. With zero comments and no fix applied, the issue was abandoned or marked stale. | |
| #4142 snapcraft remote-build exits with return code 0 even when some snaps failed to build for a given arch | snapcraft | closed | Closed without comments or resolution, indicating the request was abandoned. No official fix or merge details were provided. | |
| #1973146 snapcraftctl build fails with message "expected string or bytes-like object" | snapcraft (launchpad) | closed | Closed without comments or resolution details. Likely abandoned due to inactivity. No fix was implemented or documented for the snapcraftctl build TypeError. |