Hi – Maybe I’m confused, but I think builds are not working correctly. I am able to do a debug build just fine locally, but when build.snapcraft.io does an automatic build, they all fail like this:
CalledProcessError: Command '['lxc', 'exec', 'lp-xenial-amd64', '--env', 'LANG=C.UTF-8', '--env', 'SHELL=/bin/sh', '--env', 'SNAPCRAFT_BUILD_INFO=1', '--env', 'SNAPCRAFT_IMAGE_INFO={"build_url": "https://launchpad.net/~build.snapcraft.io/+snap/dca5c443e20d73a7996af733f7a42649-xenial/+build/363196"}', '--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/jgalaxian && linux64 snapcraft']' returned non-zero exit status 2
Any ideas?
The actual error is further up in the logging output:
You have used ./snap in the source parameter for the wrapper part. This is what is causing snapcraft to fail. Snapcraft will save and modify files and folders within ./snap as part of it’s processing of the build. When you also set a part’s source in the ./snap folder the modifications that snapcraft does will cause it to notice that the files you specified as source are changing.
The solution is to move the wrapper part’s sources somewhere else in your project.
Great. Thanks for that. I fixed that bit by moving my run.sh script outside of snap and updating the yaml. Now, however, my builds succeed, but the releases all fail. Mostly I get this:
Error:(‘Connection aborted.’, gaierror(-3, ‘Temporary failure in name resolution’))
But I also see this for the s390x:
Error:[Errno 12] Cannot allocate memory
The build log for one of the errors is here. Seems sane, but . . .
Is this some other issue with my snap in particular?
Releases seem to be happening now. Thanks for the help.
