Sent a patch that fixed it for me. I meant to send it as a reply to this, but something went wrong.
Here it is: [PATCH wayland] test-runner: wait for concrete pid <http://lists.freedesktop.org/archives/wayland-devel/2015-February/019710.html> Does it fix it on your side? Cheers, Marek On Mon, Feb 2, 2015 at 7:55 AM, Marek Chalupa <[email protected]> wrote: > Or does the tests run in parallel? > > On Sat, Jan 31, 2015 at 5:37 PM, Jan Engelhardt <[email protected]> wrote: > >> >> From openSUSE's attempts to build wayland 1.6.91: >> >> [ 98s] ---------------------------------------- >> [ 98s] Timeout was set to 3 seconds from now. >> [ 98s] test "threading_errors_tst": exit status 0, pass. >> [ 98s] ---------------------------------------- >> [ 98s] unable to open lockfile >> >> /home/abuild/rpmbuild/BUILD/wayland-1.6.91/xdg/wayland-tests/wayland-test-6076-1422702535552354.lock >> check permissions >> [ 98s] display-test: tests/test-compositor.c:295: display_create: >> Assertion `stat == 0 && "Failed adding socket"' failed. >> [ 98s] test "post_nomem_tst": signal 6, fail. >> >> >> Parts of the testsuite fail randomly, i.e. there seems to be a race >> condition involved. >> _______________________________________________ >> wayland-devel mailing list >> [email protected] >> http://lists.freedesktop.org/mailman/listinfo/wayland-devel >> > >
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
