travis linux package cache out of date?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

travis linux package cache out of date?

Alistair Grant
 
Hi Everyone,

Linux builds have been failing recently with error messages like:

E: Failed to fetch http://something.deb 404 Not Found [IP: 35.184.213.5 80]

I've seen these types of errors on my machine, typically when I forget
to run apt-get update before attempting to install or upgrade
packages.

@Rydier kindly provided some supporting evidence for the problem:

--
Error logs of linux builds for
https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/378430866
(and onwards) state they try loading
http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.3_amd64.deb
while the file on server is
http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.4_amd64.deb
so an out-of-date package cache is the likely culprit?
--


I've created an experimental branch which appears to solve the problem:

https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261

However I would expect that the travis infrastructure should
automatically update build environments to ensure that the package
cache is up to date.

Can someone who is familiar with travis perhaps confirm that this is
the correct approach, or suggest a better alternative (one possibility
is that we keep this until the infrastructure is updated and then
revert it).

Thanks,
Alistair
Reply | Threaded
Open this post in threaded view
|

Re: travis linux package cache out of date?

fniephaus
 
The discussion has been moved to https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261 ...

On Tue, May 15, 2018 at 5:55 PM Alistair Grant <[hidden email]> wrote:
 
Hi Everyone,

Linux builds have been failing recently with error messages like:

E: Failed to fetch http://something.deb 404 Not Found [IP: 35.184.213.5 80]

I've seen these types of errors on my machine, typically when I forget
to run apt-get update before attempting to install or upgrade
packages.

@Rydier kindly provided some supporting evidence for the problem:

--
Error logs of linux builds for
https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/jobs/378430866
(and onwards) state they try loading
http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.3_amd64.deb
while the file on server is
http://security.ubuntu.com/ubuntu/pool/main/g/gcc-4.8/libx32itm1_4.8.4-2ubuntu1~14.04.4_amd64.deb
so an out-of-date package cache is the likely culprit?
--


I've created an experimental branch which appears to solve the problem:

https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/261

However I would expect that the travis infrastructure should
automatically update build environments to ensure that the package
cache is up to date.

Can someone who is familiar with travis perhaps confirm that this is
the correct approach, or suggest a better alternative (one possibility
is that we keep this until the infrastructure is updated and then
revert it).

Thanks,
Alistair