GNOME Bugzilla – Bug 723467
souphttpsrc: Failing/racy checks
Last modified: 2016-04-18 10:54:01 UTC
71%: Checks: 14, Failures: 0, Errors: 4 elements/souphttpsrc.c:124:E:general:test_redirect_yes:0: (after this point) Test timeout expired elements/souphttpsrc.c:124:E:general:test_redirect_no:0: (after this point) Test timeout expired elements/souphttpsrc.c:124:E:general:test_not_found:0: (after this point) Test timeout expired elements/souphttpsrc.c:124:E:general:test_forbidden:0: (after this point) Test timeout expired This is on a slow-ish machine (can't reproduce it on fast machine). What's "interesting" is that it's constantly those tests that fail (and not the other tests that also use a local web server). I haven't managed to figure out anything that particuliar between those tests and other tests.
I have a different set of failing tests here. I added a 1 sec sleep at the end of run_server and now they all work forever.
The only racy thing which I've seen or am aware of is an issue I fixed a while back: commit 8e2c1d1de56bddbff22170f8b17473882e0e63f9 Author: Tim-Philipp Müller <tim@centricular.com> Date: Thu Feb 18 13:43:07 2016 +0000 tests: fix spurious souphttpsrc test timouts Set GSETTINGS_BACKEND=memory, apparently there's something about fork() and the dconf backend (or whatever else that drags in or activates) that messes up locking and causes timeouts due to deadlocks in g_mutex_lock(), since everything works fine with CK_FORK=no as well. So I'd say let's close this. Please re-open if you still get other issues.