git clone on travis doesn't work

Oleg Grenrus oleg.grenrus at
Sat Mar 9 16:41:03 UTC 2019

I can reproduce that problem on Ubuntu 14.04 which Travis uses now by
It's "fixed" in Ubuntu 16.04. Use

    dist: xenial

and your travis build should proceed.


Ubuntu 14.04

root at 6f98cdde6521:/# git clone
Cloning into 'ci-images'...
fatal: unable to access '':
gnutls_handshake() failed: Handshake failed

Ubuntu 16.04

root at a66b1076e2f8:/#  git clone
Cloning into 'ci-images'...
remote: Enumerating objects: 110, done.
remote: Counting objects: 100% (110/110), done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 110 (delta 49), reused 81 (delta 36)
Receiving objects: 100% (110/110), 17.14 KiB | 0 bytes/s, done.
Resolving deltas: 100% (49/49), done.
Checking connectivity... done.


- Oleg

On 9.3.2019 14.15, Shayne Fletcher wrote:
> On Sat, Mar 9, 2019 at 1:23 AM Ben Gamari <ben at
> <mailto:ben at>> wrote:
>     Shayne Fletcher via ghc-devs <ghc-devs at
>     <mailto:ghc-devs at>> writes:
> [...] 
>     I feel like I'm missing something here. I recall you mentioned this in
>     your previous message but there I'm still lacking crucial context. Can
>     you offer any additional details? How exactly does it fail?
> git clone fails on Travis Linux
> Ubuntu VMs with "fatal: unable to access
> '': gnutls_handshake() failed:
> Handshake failed.
>     In principle there is no reason why cloning from
> <> from
>     Travis shouldn't work. I'd be happy to fix the issue if there is
>     one but
>     without knowing more I'm pretty powerless to change the situation.
> The issue as I understand relates to gitlab's use of the "Let's
> Encrypt" certificate authority. Apparently this is a relatively new
> authority and is unrecognized by the SSL software on the Ubuntu VM
> that Travis provides. I don't know of any workarounds at this time
> that can be applied in the VM that to overcome this problem. I also
> don't know if anything can be done on the gitlab side to mitigate it
> but suspect not. I do have a procedure that allows me to side-step the
> problem for my own case and can share that with anyone that needs it.
>     Cheers,
>     - Ben
> This message, and any attachments, is for the intended recipient(s)
> only, may contain information that is privileged, confidential and/or
> proprietary and subject to important terms and conditions available
> at
> <>. If you are not the
> intended recipient, please delete this message. 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the ghc-devs mailing list