[openssl-dev] Travis failures

[Matt Caswell]

On 16/06/17 10:43, Matt Caswell wrote:
> 
> 
> On 16/06/17 10:25, Matt Caswell wrote:> Possibly a bad clang-3.9
> update?? Any ideas?
> After this command in the logs:
> 
> $ sudo -E apt-get -yq --no-install-suggests --no-install-recommends
> --force-yes install clang-3.9
> 
> Failing builds look like this:
> 
> After this operation, 262 MB of additional disk space will be used.
> Get:1 http://us-central1.gce.archive.ubuntu.com/ubuntu/
> trusty-updates/universe libllvm3.9v4 amd64 1:3.9.1-4ubuntu3~14.04.2
> [10.6 MB]
> Get:2 http://us-central1.gce.archive.ubuntu.com/ubuntu/
> trusty-updates/universe libclang1-3.9 amd64 1:3.9.1-4ubuntu3~14.04.2
> [5,709 kB]
> Get:3 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/
> trusty/main gcc-7-base amd64 7.1.0-5ubuntu2~14.04 [18.5 kB]
> Get:4 http://us-central1.gce.archive.ubuntu.com/ubuntu/
> trusty-updates/universe binutils-2.26 amd64 2.26.1-1ubuntu1~14.04 [3,437 kB]
> Get:5 http://us-central1.gce.archive.ubuntu.com/ubuntu/
> trusty-updates/universe libclang-common-3.9-dev amd64
> 1:3.9.1-4ubuntu3~14.04.2 [2,733 kB]
> 
> 
> Older successful builds have this:
> 
> Get:1 http://apt.llvm.org/trusty/ llvm-toolchain-trusty-3.9/main
> libllvm3.9 amd64 1:3.9~svn288847-1~exp1 [10.6 MB]
> Get:2 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/
> trusty/main gcc-7-base amd64 7.1.0-5ubuntu2~14.04 [18.5 kB]
> Get:3 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/
> trusty/main libstdc++6 amd64 7.1.0-5ubuntu2~14.04 [304 kB]
> Get:4 http://apt.llvm.org/trusty/ llvm-toolchain-trusty-3.9/main
> libclang1-3.9 amd64 1:3.9~svn288847-1~exp1 [5,752 kB]
> Get:5 http://apt.llvm.org/trusty/ llvm-toolchain-trusty-3.9/main
> libclang-common-3.9-dev amd64 1:3.9~svn288847-1~exp1 [2,328 kB]
> Get:6 http://apt.llvm.org/trusty/ llvm-toolchain-trusty-3.9/main
> clang-3.9 amd64 1:3.9~svn288847-1~exp1 [35.6 MB]
> 
> 
> Note the successful builds download from llvm.org but failing builds do
> not. I cannot seem to connect with my browser to llvm.org today, so I
> suspect they are having problems.

Well llvm.org is back up, but we still seem to be failing in travis with
the same issue.

Any ideas?

Matt