Closed erikd closed 5 years ago
I think that https://github.com/haskell/haskell-ide-engine/issues/1328 and I may also be experiencing this. For me, the issue only shows up on my Arch machine, when trying to build https://github.com/kframework/kore. This is on a fresh Arch lxc container which is brought up to date and then has these packages installed:
depends=('java-runtime' 'flex' 'gcc' 'gmp' 'mpfr' 'z3' 'clang' 'libyaml' 'jemalloc' 'opam' 'gawk' 'make' 'diffutils' 'patch' 'tar' 'grep' 'llvm' 'lld')
makedepends=('maven' 'jdk8-openjdk' 'cmake' 'boost' 'zlib' 'stack' 'pkg-config' 'bison' 'python' 'fakeroot')
I run:
$ git clone 'https://github.com/kframework/kore'
Cloning into 'kore'...
remote: Enumerating objects: 7, done.
remote: Counting objects: 100% (7/7), done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 35899 (delta 0), reused 4 (delta 0), pack-reused 35892
Receiving objects: 100% (35899/35899), 35.97 MiB | 6.96 MiB/s, done.
Resolving deltas: 100% (21397/21397), done.
$ cd kore
$ stack build
Warning: /home/dev/kore/stack.yaml: Unrecognized fields in PLArchive:github: sha256, size
Preparing to install GHC (tinfo6) to an isolated location.
This will not interfere with any system-level installation.
Already downloaded.
Installing GHC ...
thread blocked indefinitely in an STM transaction
Retrying doesn't seem to help.
Hi, thanks for reporting. Would you please paste the verbose output, @erikd (wrapped in <details>
tags, please)?
Likewise, @ehildenb, please paste the verbose output, and I'll take a look.
From stack build --verbose
:
Hmmm, sudo stack upgrade
(to version 2.1.3
) and now I can run stack build
. Makes it tough to make a PKGBUILD though with the default version of stack
that Arch comes with.
I've flagged it on the aur — glad you've found a fix.
There have been some tar
issues, recently (commercialhaskell/stack#4888) and I wonder whether this is related — I'll wait to see what @erikd reports.
I switched back to version 1.9.3 when I hit this issue and have not bothered to update since.
The version I had issue with (2.1.1.1) has been superseded and I will assume that this has been fixed. Closing this.
General summary/comments (optional)
Steps to reproduce
Result in:
Restarting it will get a bit further before hitting the same issue again (and again (and again ...)).
Expected
There should not be any blocked threads.
Actual
Stack version
Method of installation
Build from the Hackage tarball and turned into a custom Debian package.