I have a pull request open, but every time github tries to run the tests on it, the fetching of RPMs to build a CentOS image times out. Is there a magic day of week/time of day when the CentOS servers are less busy?
2022-02-27T00:53:56.9888213Z Status: Downloaded newer image for centos:8
2022-02-27T00:53:56.9918818Z docker.io/library/centos:8
2022-02-27T00:53:58.1958352Z daa0893bcccc88631dd1a11ee19a1223d940e6251bec0e4b8bcd09f79fc1453e
2022-02-27T00:55:29.3479511Z CentOS Linux 8 - AppStream 0.0 B/s | 0 B 01:30
2022-02-27T00:55:29.3480699Z Errors during downloading metadata for repository 'appstream':
2022-02-27T00:55:29.3481981Z - Curl error (28): Timeout was reached for http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/d8472d61c5e53a3e9cbffb68e0dddbd04a07c2b7d864b07ddd211c6ad1380c6e-primary.xml.gz [Connection timed out after 30000 milliseconds]
2022-02-27T00:55:29.3483609Z - Curl error (28): Timeout was reached for http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/5ea46cc5dfdd4a6f9c181ef29daa4a386e7843080cd625843267860d444df2f3-comps-AppStream.x86_64.xml [Connection timed out after 30000 milliseconds]
2022-02-27T00:55:29.3489442Z - Curl error (28): Timeout was reached for http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/d8472d61c5e53a3e9cbffb68e0dddbd04a07c2b7d864b07ddd211c6ad1380c6e-primary.xml.gz [Connection timed out after 30001 milliseconds]
2022-02-27T00:55:29.3491490Z - Curl error (28): Timeout was reached for http://vault.centos.org/centos/8/AppStream/x86_64/os/repodata/768e088faaaba73d00aee49f134e22d5d1803171ffb167260c8b55f4165e0372-filelists.xml.gz [Connection timed out after 30000 milliseconds]
2022-02-27T00:55:29.3495137Z Error: Failed to download metadata for repo 'appstream': Yum repo downloading error: Downloading error(s): repodata/d8472d61c5e53a3e9cbffb68e0dddbd04a07c2b7d864b07ddd211c6ad1380c6e-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/768e088faaaba73d00aee49f134e22d5d1803171ffb167260c8b55f4165e0372-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/5ea46cc5dfdd4a6f9c181ef29daa4a386e7843080cd625843267860d444df2f3-comps-AppStream.x86_64.xml - Cannot download, all mirrors were already tried without success; repodata/75e00d390273f65b94d63a5ac7db2677d832bfa95b3d7eecf651c6f45e33f8ff-modules.yaml.xz - Cannot download, all mirrors were already tried without success
2022-02-27T00:55:29.4508749Z /home/vsts/work/1/s
2022-02-27T00:55:29.4525183Z env: 'python3': No such file or directory
From what I have found on the CentOS forums, the “vault” server is not intended to be used this way.
Related question: How do I trigger a new running of the tests, other than to commit/push a dummy change?
Thanks.