I test my binary extension (C++) using four different versions of Node (8, 10, 12, 13). Before running a build the script adds a recommended PPA. I assume it should either work or fail regardless of Node version yet it fails in some cases and works in others:
I tried to restart failed jobs manually yet they failed again. The last time it happened it was dismissed as some mysterious network problems. I am on the edge of my seat to learn the cause this time.
I have no doubt that it is a flaky I/O — sometimes sudo apt works, sometimes it doesn’t as evidenced in my link. 99.999% is for some network trouble between Travis CI hosts and the standard apt sources. The question is: when is it going to be fixed?
For now I removed the Travis CI build badge so not to upset users.
I am faced apt-add-repository’s error “Error: retrieving gpg key timed out” on xenial environment last month. I am not sure it is same error with you.
software-properties (0.96.24.25) bionic; urgency=medium
* ppa.py:
- rework key retrieval, instead of using hkp & gnupg/dirmngr, use https
& python's built in urllib.
- thus, add-apt-key for PPAs observes https_proxy for key retrieval
- simplify gnupg operations, depend on gpg package only, and use
import/public key operations only.
In my case, just using the software-properties deb package newer version by dist: bionic or sudo apt-get -yq install --only-upgrade software-properties-common might work.