Should we make out CI tests immune network failures?

[sbc100]

For a while today it seem that https://lua.org/ was completely down. This meant that our CI tests were failing becasue we have tests that download and build each of our ports (lua being one of them).

This kind of thing happens from occasionally and its can be very disruptive to our workflow.

One thing we did in the past to mitigate this is that we mirrors all the archive from sourceforge.net into our Google Cloud Storage bucket (which we already rely on in many places). This is because sourceforge.net was having outages every few weeks/months.

To mitigate this further have a couple more options:

1. Move all our ports to use GCS
2. Implement some kind of local caching so that tests don't actually hit the real network.

Any other ideas?

[sbc100]

One thing to note is that its very unlikely we can run our CI at all without at least github.com and GCS being up. This is because we server the emsdk binaries from GCS, so its its down we can't even get llvm and binaryen.

This makes me think that the simple solution (1) is probably fine?