Most packaging tooling runs in offline / network sandboxed environments, so it would be useful for packagers if all tests requiring network connectivity could be disabled in one go e.g. with a commandline argument when running the tests, or an environment variable.
This currently affects the following tests (as of release 1.3.0):
KeycacheTest.NegativeCacheTestkeycacheTest.RefreshTestKeycacheTest.RefreshExpiredTestKeycacheTest.LoadJwksTriggersRefreshWhenStale
(for reference, see for example gentoo/gentoo#45567 )
Thanks to @bbockelm for proposing this. 👍
Most packaging tooling runs in offline / network sandboxed environments, so it would be useful for packagers if all tests requiring network connectivity could be disabled in one go e.g. with a commandline argument when running the tests, or an environment variable.
This currently affects the following tests (as of release 1.3.0):
KeycacheTest.NegativeCacheTestkeycacheTest.RefreshTestKeycacheTest.RefreshExpiredTestKeycacheTest.LoadJwksTriggersRefreshWhenStale(for reference, see for example gentoo/gentoo#45567 )
Thanks to @bbockelm for proposing this. 👍