The last couple of days (at least yesterday and today) I've seen this behaviour a lot:
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
But I don't see it all the time. Am I alone?
@qrilka_twitter I don't really have reproduction steps, but the code is available at: https://github.com/magthe/ci-test-hs/ (the branch
Add Azure Pipelines)
Examples of CI builds at:
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.
If anyone is running into the "mirrors.json is expired" issue, please see this issue for explanation and workaround:
Also, please feel free to weigh in with a vote on that issue.
Compiler thinks a type is different depending on where it is referenced
core:testas a separate target from
core:lib, so the arrow should look like
core:lib -> testlib:lib -> core:test
core:testthe same target in some way?