snap builds randomly failing via proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Undecided
|
Unassigned |
Bug Description
I'm trying to build amd64,armhf,arm64 snaps of forgejo, using the yaml at https:/
It kept failing with errors connecting to the npm registry.
So I added the following to the override-build stanza in the yaml:
+
+ # Setup proxy access if required.
+ if [[ -n "${http_proxy:-}" ]]; then
+ export HTTP_PROXY=
+ export HTTPS_PROXY=
+ npm config set proxy "${http_proxy}"
+ npm config set https-proxy "${https_proxy}"
+ fi
+
However, it's now failing inconsistently. Sometimes it will work on one architecture and fail on another or fail on all three. It's seemingly random.
Here's the log of it failing most recently.
Here's a snippet:
```
[13/Mar/
[13/Mar/
[13/Mar/
[13/Mar/
:: npm ERR! Proxy connection ended before receiving CONNECT response
::
:: npm ERR! A complete log of this run can be found in: /root/.
:: make[1]: *** [Makefile:949: node_modules] Error 1
:: make: *** [Makefile:989: public/
[13/Mar/
[13/Mar/
[13/Mar/
'override-build' in part 'forgejo' failed with code 2.
Review the scriptlet and make sure it's correct.
```
Hi Alan,
Thanks for reaching out. We had a couple of similar reports lately, but there it was about builds taking more than 6 hours and the proxy token expired, which does not seem to be the case here.
Do you see the same issues when building the Snap locally?