Hi,
Anyone else experiencing problems with remote builds? I’m using GitHub + Snapcraft.io.
I normally have to trigger a build multiple times to succeed for every architecture.
Today I’ve also experienced failed builds (constantly, for every architecture) for one of the snaps I’m maintaining and I’m not sure what’s wrong. It’s building fine on my local machines.
On remote it (home-assistant-snap) fails with:
Check the build logs and ensure the part's configuration and sources are correct.
Build failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 258, in run
self.build()
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 247, in build
env=env)
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 100, in run_build_command
return self.backend.run(args, env=full_env, **kwargs)
File "/usr/lib/python3/dist-packages/lpbuildd/target/lxd.py", line 537, in run
subprocess.check_call(cmd, **kwargs)
File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['lxc', 'exec', 'lp-focal-amd64', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build-request-id": "lp-63549903", "build-request-timestamp": "2021-05-11T19:17:18Z", "build_url": "https://launchpad.net/~build.snapcraft.io/+snap/c8c030b03a17f51bd10e02ab2f95e72b/+build/1405599"}', '--env', 'SNAPCRAFT_BUILD_ENVIRONMENT=host', '--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/snap-git-proxy', '--', '/bin/sh', '-c', 'cd /build/home-assistant-snap && linux64 snapcraft']' returned non-zero exit status 2.
Revoking proxy token...
Unsure if it’s a proxy issue again?
The other (zwavejs2mqtt) is failing of various reasons:
[11/May/2021:16:32:41 +0000] "CONNECT registry.npmjs.org:443 HTTP/1.1" 200 10998 "-" "-"
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated @babel/polyfill@7.12.1: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated core-js@2.6.12: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm notice
npm notice New minor version of npm available! 7.7.6 -> 7.12.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.12.1>
npm notice Run `npm install -g npm@7.12.1` to update!
npm notice
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! network request to https://registry.npmjs.org/which-module/-/which-module-2.0.0.tgz failed, reason: socket hang up
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-05-11T16_34_40_324Z-debug.log
Failed to run 'override-build': Exit code was 1.
Build failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/lpbuildd/target/build_snap.py", line 258, in run
self.build()
However this will complete after X tries, based on trials and errors the past weeks.
Build duration is only between 7 - 25 minutes, depending of the architecture.