Build fails on snapcraft.io, works locally (during `cabal update`)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Triaged
|
High
|
Unassigned |
Bug Description
I have a build that consistently fails on build.snapcraft.io, but I'm unable to reproduce it locally.
Here's the snapcraft log: https:/
It appears to fail during `cabal update` to fetch the list of available Haskell packages:
Downloading the latest package list from hackage.haskell.org
[11/
cabal: <socket: 10>: resource vanished
Failed to run 'build': Exit code was 1.
The same build fails with the same message for all architectures.
Meanwhile, `snapcraft cleanbuild --debug` on my local machine works fine:
Downloading the latest package list from hackage.haskell.org
Warning: ShellCheck.cabal: Ignoring unknown section type: custom-setup
Resolving dependencies...
Notice: installing into a sandbox located at
/root/
Downloading base-compat-
Downloading dlist-0.8.0.5...
Configuring dlist-0.8.0.5...
[...]
Retrieved 'shellcheck_
Is this a proxy problem? Or a Hackage IP block? Or a cabal issue? I'm not sure how to troubleshoot it.
summary: |
- Build fails on snapcraft, works locally (during `cabal update`) + Build fails on snapcraft.io, works locally (during `cabal update`) |
affects: | snapcraft → launchpad-buildd |
Changed in launchpad-buildd: | |
importance: | Undecided → High |
status: | New → Triaged |
This is really a bug in the somewhat old version of the Haskell HTTP library present in xenial's version of cabal-install:
https:/ /github. com/haskell/ HTTP/issues/ 14
We may be able to work around it by adding connection persistence support to launchpad-buildd's internal proxy.