Use GHC 8.6.5 as the minimum bootstrap compiler version

mentioned in merge request !26 (closed)

$ CONTAINER_IMAGE="$CONTAINER_IMAGE_BASE/$IMAGE" # collapsed multi-line command
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?
Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?

ERROR: Job failed: exit code 1

I have no idea what might be causing this. Any ideas, @bgamari?

I have fixed this in !28 (merged) and some configuration changes on the builders. I'll rebase once it has landed.

unmarked as a Work In Progress

added 4 commits

22beb711...55e23c93 - 3 commits from branch master
a9ba9ac7 - WIP: Use GHC 8.6.5 as the minimum bootstrap compiler version

Compare with previous version

marked as a Work In Progress from a9ba9ac7

Thanks, @bgamari! Unfortunately, it appears that master is still failing on certain configurations.

Here is how build-linters, build-i386-linux-deb8, build-i386-linux-deb9, build-x86_64-linux-centos7, and build-x86_64-linux-deb8 fails:

713aaa24f997: Retrying in 12 seconds
19a93d008a5f: Retrying in 12 seconds
713aaa24f997: Retrying in 11 seconds
19a93d008a5f: Retrying in 11 seconds
713aaa24f997: Retrying in 10 seconds
19a93d008a5f: Retrying in 10 seconds
713aaa24f997: Retrying in 9 seconds
19a93d008a5f: Retrying in 9 seconds
713aaa24f997: Retrying in 8 seconds
19a93d008a5f: Retrying in 8 seconds
713aaa24f997: Retrying in 7 seconds
19a93d008a5f: Retrying in 7 seconds
713aaa24f997: Retrying in 6 seconds
19a93d008a5f: Retrying in 6 seconds
713aaa24f997: Retrying in 5 seconds
19a93d008a5f: Retrying in 5 seconds
713aaa24f997: Retrying in 4 seconds
19a93d008a5f: Retrying in 4 seconds
713aaa24f997: Retrying in 3 seconds
19a93d008a5f: Retrying in 3 seconds
713aaa24f997: Retrying in 2 seconds
19a93d008a5f: Retrying in 2 seconds
713aaa24f997: Retrying in 1 second
19a93d008a5f: Retrying in 1 second
error creating overlay mount to /var/lib/docker/overlay2/e16cb392775d90c3533a990370afacb0ed6a17861b68702895aa01d45517be10/merged: device or resource busy

Here is how build-x86_64-linux-deb9 fails:

Step 6/18 : RUN apt-key adv --keyserver keyserver.ubuntu.com  --recv-keys BA3CBA3FFE22B574
 ---> Running in 34b1c1a10274
Warning: apt-key output should not be parsed (stdout is not a terminal)
Executing: /tmp/apt-key-gpghome.eW30OdHSp6/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys BA3CBA3FFE22B574
gpg: keyserver receive failed: No data
The command '/bin/bash -o pipefail -c apt-key adv --keyserver keyserver.ubuntu.com  --recv-keys BA3CBA3FFE22B574' returned a non-zero code: 2

I wonder if some of these errors are nondeterministic. For instance, the build-x86_64-linux-deb8 build passes on this MR. Quite strange.

Some of the errors on this MR are actually different from what is on master. I'll see if I can reproduce these errors locally.

Indeed I've been investigating this. I suspect this is another manifestation of the rather obnoxious gitlab #49345 but it's very hard to say for certain.

Regardless, I can finish up this MR if you would rather.