GNOME Bugzilla – Bug 736063
Some tests fail to run when network is disconnected
Last modified: 2021-05-25 12:45:57 UTC
Maybe their failures shouldn't be fatal then: make[2]: Entering directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' make[3]: Entering directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' PASS: proxy PASS: proxy-continuous PASS: oauth2 ../build/test-driver: line 107: 3199 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: oauth-async PASS: threaded PASS: custom-serialize ../build/test-driver: line 107: 3180 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: oauth ../build/test-driver: line 107: 3320 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: lastfm ../build/test-driver: line 107: 3353 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 XFAIL: xml ../build/test-driver: line 107: 3304 Trace/breakpoint trap (core dumped) "$@" > $log_file 2>&1 FAIL: flickr make[4]: Entering directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' ============================================================================ Testsuite summary for rest 0.7.92 ============================================================================ # TOTAL: 10 # PASS: 5 # SKIP: 0 # XFAIL: 1 # FAIL: 4 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log ============================================================================ make[3]: *** [test-suite.log] Error 1 make[3]: Leaving directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' make[2]: *** [check-TESTS] Error 2 make[2]: Leaving directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/var/tmp/portage/net-libs/rest-0.7.92/work/rest-0.7.92/tests' make: *** [check-recursive] Error 1
Since some of these use third-party services (like oauthbin.com) to check for correctness without implementing the oauth server side, the best thing we could do is disabling those if no connection is available? It would still not protect us from the services themselves being not reachable of course. Or should we just accept certain errors from e.g. rest_proxy_call_sync that appear when no network connection is available and handle those cases gracefully without letting the test case completely fail?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/librest/-/issues/ Thank you for your understanding and your help.