FS#72514 - "Operation too slow" should fallback to other servers

Attached to Project: Pacman
Opened by Simon Ser (emersion) - Friday, 22 October 2021, 10:47 GMT
Task Type Bug Report
Category Backend/Core
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I have a CI system with Arch Linux builds. The CI image uses reflector to
generate a mirrorlist with 30 entries.

It seems like one of the mirrors has networking issues today, and sometimes
fails with:

error: failed retrieving file 'compiler-rt-12.0.1-2-x86_64.pkg.tar.zst.=
sig' from mirror.osbeck.com : Operation too slow. Less than 1 bytes/sec tra=
nsferred the last 10 seconds
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.

Full log at [1].

I'd assume this kind of error would automatically fall back to the next
available server in the mirrorlist, but it doesn't seem like this happens?
Is this intentional? It seems like a good idea to have a fallback for
robustness.

[1]: https://builds.sr.ht/~emersion/job/612556
This task depends upon

Comment by Allan McRae (Allan) - Friday, 22 October 2021, 11:00 GMT
Hrm... It should go to the next server if a package fails. But I see it is a signature failing - apparently that does not fall through!

Loading...