tests/fedora32: retry dnf#2511
Conversation
Fedora mirrors are not very stable recently, leading to CI failures that usually look like this: > sudo: make: command not found In fact it's caused by dnf failure to read metadata from mirrors: > Errors during downloading metadata for repository 'updates': > - Downloading successful, but checksum doesn't match. Calculated: <....> > Error: Failed to download metadata for repo 'updates': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried The error went undetected due to lack of exit code check. This commit: - adds `set -e -u -o pipefail` so the script will fail early; - adds a retry loop with a sleep around dnf invocation. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
|
I plan to kick CI a few times in order to repro the dnf failure/retry. |
495f58a to
904d3c1
Compare
|
It is now failed on with "429 too many requests", and I have seen it before. Not sure what to do about it. Also retry? This is getting ugly :-\ |
|
Ran fedora32 vagrant CI 6 times, was not able to repro the repo failure. Yet, I am pretty sure the retry code works as intended. @AkihiroSuda @mrunalp PTAL |
|
Travis not responding :( |
Add `set -e -u -o pipefail` so the script will fail early if there's an error. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
|
force-pushed to re-kick CI |
|
CI is actually green, did not propagate to github though (see https://travis-ci.org/github/opencontainers/runc/builds/706190244) @mrunalp PTAL |
|
Hmm, another force push maybe? |
|
this time I have a link to Travis, so I just clicked on on "restart build" in there |
|
CI failed on checkpoint |
Fedora mirrors are not very stable recently, leading to CI failures
(seen in multiple recent PRs) that usually look like this:
In fact it's caused by dnf failure to read metadata from mirrors:
The error went undetected due to lack of exit code check.
This PR:
set -e -u -o pipefailso the script will fail early (and do the same for centos7 vagrantfile);