stack build gets stuck at 100% cpu for hours

[alexanderkjeldaas]

My stack gets stuck for 3 hours until the CI times out now:

Didn't see JuicyPixels-3.2.9.1 in your package indices.
Updating and trying again.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
No updates to your package list were found
Updating package index Hackage (mirrored at https://s3.amazonaws.com/hackage.fpcomplete.com/) ...

[mgsloan]

What version of stack is this with? It would also be good to get a verbose log.

I believe this is likely a bug in the hackage-security package. Stack currently defaults to using hackage-security, and the code path that doesn't use hackage-security would output "Downloading package index from ". I have opened this issue on the upstream repo: haskell/hackage-security#192

One thing to note is that stack-1.5 uses the same version of hackage-security (0.5.2.2) as stack-1.6 (not yet released - soon!).

[alexanderkjeldaas]

1.4.0 and also 1.5.(1?) I think. both behaved the same.

I rebuilt the docker image used for CI and with updated package versions this didn't happen anymore.

[alexanderkjeldaas]

Version 1.4.0, Git revision 5986498 (4642 commits) x86_64 hpack-0.17.0
but this also persisted after upgrading to the latest version

[alexanderkjeldaas]

I think #3830 might be the same issue, but stack has possibly changed outputs during the various updates?