Fossil Forum
barak_pearlmutter
1 month, 1 week ago
Post: Test Suite Failure—No Network?
There was an automated test suite regression failure on the Debian systems, for fossil 2.27-2. (I've uploaded 2.28-1 but I don't think it solves the issue.)
The problem is shown in Debian bug 1123552 and the relevant bit is:
...
199s test settings-valid-local-anon-cookie-lifespan FAILED!
...
199s test settings-valid-local-regexp-limit FAILED!
...
199s test settings-valid-local-robot-exception FAILED!
...
199s test settings-valid-global-anon-cookie-lifespan FAILED!
...
199s test settings-valid-global-regexp-limit FAILED!
...
199s test settings-valid-global-robot-exception FAILED!
...
212s ***** End of wiki: 6 errors so far ******
212s ***** Final results: 6 errors out of 42573 tests
212s ***** Considered failures: settings-valid-local-anon-cookie-lifespan settings-valid-local-regexp-limit settings-valid-local-robot-exception settings-valid-global-anon-cookie-lifespan settings-valid-global-regexp-limit settings-valid-global-robot-exception
212s ***** Ignored results: 0 ignored errors out of 42573 tests
212s ***** Skipped tests: json merge5 set-manifest th1-docs th1-hooks th1-tcl unversioned
Is it possible that the tests assume a configured network (e.g., at least able to connect to localhost) but the test environment has no network whatsoever including loopback? If that's the issue, a testing --fail-to-fail-if-there-is-no-network-not-even-loopback option would be useful.