You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit 31ca666, which switched the CI from using 8.10.3 to 8.10.7, inadvertently broke the nightly cryptol-remote-api Docker builds:
#5 [toolchain 1/6] FROM docker.io/library/debian:buster-20210511@sha256:acf7795dc91df17e10effee064bd229580a9c34213b4dba578d64768af5d8c51
#5 DONE 0.0s
------
> [build 4/10] COPY cabal.GHC-8.10.3.config cabal.project.freeze:
------
cryptol-remote-api/Dockerfile:47
--------------------
45 | ENV LANG=C.UTF-8 \
46 | LC_ALL=C.UTF-8
47 | >>> COPY cabal.GHC-${GHCVER}.config cabal.project.freeze
48 |
49 | RUN if ${PORTABILITY}; then SERVERS_NOT_THREADED="true"; fi
--------------------
error: failed to solve: failed to compute cache key: failed to calculate checksum of ref 3vziof1hd8q05uyzn9nxoie8v::jqk5ypsbtusu4w64ltqwjw7gc: "/cabal.GHC-8.10.3.config": not found
Error: buildx failed with: error: failed to solve: failed to compute cache key: failed to calculate checksum of ref 3vziof1hd8q05uyzn9nxoie8v::jqk5ypsbtusu4w64ltqwjw7gc: "/cabal.GHC-8.10.3.config": not found
Ultimately, this is because I forgot to update 8.10.3 to 8.10.7 in the necessary Docker files. (I kind of wish GitHub Actions notified me in situations like this, since I wouldn't have noticed unless I manually look at the nightly CI jobs. Alas.)
The text was updated successfully, but these errors were encountered:
This converts the `cryptol-remote-api` Dockerfiles to use GHC 8.10.7 instead of
GHC 8.10.3, now that we have switched over to using 8.10.7 in the CI. This also
updates `cryptol-remote-api`'s `ghc.portability` patch to use the 8.10.7 branch
of GHC.
Fixes#1347.
Commit 31ca666, which switched the CI from using 8.10.3 to 8.10.7, inadvertently broke the nightly
cryptol-remote-api
Docker builds:Ultimately, this is because I forgot to update 8.10.3 to 8.10.7 in the necessary Docker files. (I kind of wish GitHub Actions notified me in situations like this, since I wouldn't have noticed unless I manually look at the nightly CI jobs. Alas.)
The text was updated successfully, but these errors were encountered: