Hello,
We have a snap named `charm` that builds fine on all supported architectures, however, when building using a snap recipe and the launchpad buildfarm the arm64 build is somehow always stopped with the terse message: Killed.
What could be causing this, and what could we do to debug?
Excerpt:
...
[29/Sep/2022:00:56:29 +0000] "GET http://ftpmaster.internal/ubuntu/pool/main/libe/liberror-perl/liberror-perl_0.17029-1_all.deb HTTP/1.1" 200 26460 "-" "Debian APT-HTTP/1.3 (2.0.9) non-interactive"
Starting Snapcraft 7.1.3
Logging execution to '/root/.cache/snapcraft/log/snapcraft-20220929-005530.196177.log'
Running on arm64 for arm64
Initializing parts lifecycle
Executing parts lifecycle...
Executing parts lifecycle: pull charm-tools
Executing action
Executed: pull charm-tools
Executing parts lifecycle: pull patchelf
Executing action
Executed: pull patchelf
Executed parts lifecycle
Running build phase...
Killed
Build failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 206, in run
self.build()
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 190, in build
self.run_build_command(["snapcraft"], cwd=output_path, env=env)
File "/usr/lib/python3/dist-packages/lpbuildd/target/operation.py", line 46, 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 538, 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-arm64', '--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-74362109", "build-request-timestamp": "2022-09-29T00:52:40Z", "build_url": "https://launchpad.net/~charm-toolers/charm-tools/+snap/charm-tools.master/+build/1895303"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--env', 'SNAPCRAFT_BUILD_FOR=arm64', '--', '/bin/sh', '-c', 'cd /build/charm && linux64 snapcraft']' returned non-zero exit status 137.
Revoking proxy token...
RUN: /usr/share/launchpad-buildd/bin/in-target scan-for-processes --backend=lxd --series=jammy --arch=arm64 SNAPBUILD-1895303
Scanning for processes to kill in build SNAPBUILD-1895303
Full log: https://launchpadlibrarian.net/626170410/buildlog_snap_ubuntu_jammy_arm64_charm-tools.master_BUILDING.txt.gz
Recipe: https://launchpad.net/~charm-toolers/charm-tools/+snap/charm-tools.master
Interestingly, just as I filed this bug, the s390x build failed for the first time in the same way. At this time of release schedule I gather the build farms would be quite busy?
The build is quiet, so I wonder if there could be some kill-the-