Hi,
Ivan Vučica wrote:
I saw this: this was recently addressed by replacing probe of
example.org/silly-url-test because example.org started returning 503
or similar for that URL instead of 404.
We rely on github there... wonder what happened.
But also creating the file doesn't seem to be a good idea if 404 is
looked after?
Tests should not be trying to access network as part of CI. The right
fix would be to spin up a temporary server on localhost etc. That
itself requires carefully doing process management on all supported
platforms.
Richard should chime in here... but before Easter I had all tests
running on Linux, FreeBSD, NetBSD...
I think there is minimal HTTP test server.
Why does it fail for windows+clang? No clue. Maybe CI for windows
actually blocks outgoing requests completely? This would be the cause
only if we have more tests dependent on the network and they’re also
failing. Maybe the CORRECT fix is not to do the test at all, at least
in Ci?
It could be somehow put as skipped or dashed hope under certain
conditions? like a CI flag?
Riccardo
