On Sun, 30 Aug 2026, Martin Storsjö wrote:
On Sun, 30 Aug 2026, LIU Hao wrote:
Unfortunately, these don't seem to be entirely reliable either;
in a first test build, 3 out of 4 build jobs succeeded.
If there are other suggestions from where to download these
projects sources, that would be more reliable when fetched from
github actions, I'm open for suggestions.
---
.github/workflows/build.yml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
What about mirrors on https://www.gnu.org/prep/ftp.html?
I guess I could try with some of them.
Previously we've used ftp.gnu.org first, which became unreliable at some
point, after which we switched to ftpmirror.gnu.org, which also has become
unreliable.
I guess we could try to locate which mirror seems to be closest to where the
github actions run at the moment, and see if direct access to that one would
happen to be more reliable than the main frontends.
I tried to follow where ftpmirror.gnu.org redirects, when executed from
github actions, but it doesn't seem to be consistent - it seems to be
picking mirrors from either the US or Germany. It is of course possible
that the github actions themselves are executed on servers in many
diffeent locations.
(Sadly, to get reasonable info about it, I guess we should run a number of
attempts over the course of a day or two, to see which ones respond best at
the moment.)
I did a number of test runs, over the course of a day, at different times
of the day. I tested with ftpmirror.gnu.org, ftp.gnu.org, a handful of
different mirrors that ftpmirror.gnu.org had redirected towards. I also
tested downloading GMP/MPFR/MPC from their upstream hosts, as in this
patch.
All the gnu.org mirrors, plus ftp.gnu.org, worked flawlessly in every
single of the test runs.
Some times of the day, ftpmirror.gnu.org works just fine, some times it
just returns "502 Bad Gateway".
The upstream hosts also works fine some times, but some times they also
just time out. (I remember reading that GMP tried to block all the IP
ranges where github actions executed, a couple years ago, due to excessive
load from cloning a mercurial repo in each CI execution.)
See https://github.com/mstorsjo/mingw-w64/actions/runs/33374361738 for my
test setup and results (see the earlier reruns of the same pipeline as
wel), if you're curious.
So in practice, our current choice of ftpmirror.gnu.org isn't reliable,
and neither is the upstream hosts.
The plain ftp.gnu.org, and the various mirrors I tested
(https://mirror.us-midwest-1.nexcess.net/gnu,
https://mirrors.ocf.berkeley.edu/gnu, https://mirror.cyberbits.eu/gnu, and
https://mirror.team-cymru.com/gnu) all work reliably enough for us.
Which one do you prefer for us to pick? The main one, or any of the other
ones, to avoid unnecessary load on the main site?
// Martin
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
