I’ve sent the build link to the travis ci support email!
This problem has resurfaced. Things that buildt af few days ago, now get this error, without anything new being pushed. VERY Anoying
@Lars-m Sorry to hear this is happening again.
Could you share with us an example of a build that shows the issue?
If it’s a private build, you can send it over to
support [AT] travis-ci [DOT] com .
This is the build that failed: https://travis-ci.org/dat3startcode/rest-jpa-devops-startcode/builds/581202674
Right now it’s OK, because I added the hack given ealier in this thread.
sudo apt-get update || true
I’m getting this too here:
Is there any indication as to why the error is so intermittent?
On option on the Travis side that has not yet been mentioned here yet is to implement a proper mirror using debmirror. Running that hourly while avoiding the xx:17 “cron.hourly” sync window would fix the problem.
I’m recieving the very same error for one of my projects on bionic today.
hitting this today https://travis-ci.com/kind-ci/containerd-nightlies/builds/130446473
All of my projects are running into this issue today.
This issue caused a lot of excitement: I use TravisCI to auto grade coding assignments for one of my classes. There was a lot of panic when everybody’s builds started failing at once
The problem was back again around lunchtime today: https://travis-ci.com/gvsucis263/lists-blueberrycola/builds/130580622
The problem seems to persist, even after the patch!
But as a special side fact, https://travis-ci.org/sjaeckel/travis-pg-test/jobs/596007087 succeeded at the same time …
We’ve made another try to fix this issue yesterday by deploying
Could you tell us if you are encountering this issue again from now on?