-
Notifications
You must be signed in to change notification settings - Fork 847
Description
General info
The last couple of days I'm running into an issue where untaring of GHC fails:
Preparing to download ghc-8.6.5 ...
ghc-8.6.5: download has begun
ghc-8.6.5: 17.49 MiB / 175.83 MiB ( 9.95%) downloaded...
ghc-8.6.5: 47.24 MiB / 175.83 MiB ( 26.87%) downloaded...
ghc-8.6.5: 76.67 MiB / 175.83 MiB ( 43.61%) downloaded...
ghc-8.6.5: 107.02 MiB / 175.83 MiB ( 60.86%) downloaded...
ghc-8.6.5: 136.92 MiB / 175.83 MiB ( 77.87%) downloaded...
ghc-8.6.5: 167.14 MiB / 175.83 MiB ( 95.06%) downloaded...
ghc-8.6.5: 175.83 MiB / 175.83 MiB (100.00%) downloaded...
Downloaded ghc-8.6.5.
Unpacking GHC into /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.temp/ ...
Received ExitFailure (-15) when running
Raw command: /bin/tar Jxf /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.tar.xz
Run from: /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.temp/
Error: Error encountered while unpacking GHC with
tar Jxf /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.tar.xz
run in /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.temp/
The following directories may now contain files, but won't be used by stack:
- /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5.temp/
- /home/vsts_azpcontainer/.stack/programs/x86_64-linux/ghc-8.6.5/
For more information consider rerunning with --verbose flag
Steps to reproduce
I don't have exact steps, but the code and CI builds are all open and available.
The code is available at: https://github.com/magthe/ci-test-hs/ (the branch Add Azure Pipelines)
Examples of CI builds at:
- VM, pre-built binary: https://dev.azure.com/magthe/CI%20Test/_build/results?buildId=20
- Building docker image (Build and deploy stage, if you look at earlier stages VM with pre-built binary worked): https://travis-ci.com/magthe/ci-test-hs/jobs/208730847
- Successful build of docker image: https://cloud.drone.io/magthe/ci-test-hs/25/1/4
Building image locally (docker build -t foo:0 .) first failed, then I followed the suggestion and added --verbose, then it succeeded. Howerver, the CI builds keep failing sporadically.
Expected
I'm used to stack setup working like a charm.
Actual
Well, see above.
Stack version
The version I'm using on VMs is the pre-built 2.1.1 downloaded from GitHub, e.g. https://github.com/magthe/ci-test-hs/blob/153ca80eaca23eae6444abdbf32e0e3b91240d76/.travis.yml#L15
The version used in container, including when building images, is the one that's found in fpco/stack-build:lts-13 (I believe that's been fpco/stack-build:lts-13.25 and thus stack 2.1.1)
Method of installation
See above.