https://bugs.kde.org/show_bug.cgi?id=380269
--- Comment #6 from Louis Brunner <[email protected]> --- Rhys, No problem, here are the results before the patch (but with https://bugs.kde.org/show_bug.cgi?id=385279 applied): == 655 tests, 335 stderr failures, 85 stdout failures, 8 stderrB failures, 8 stdoutB failures, 31 post failures == And after: == 655 tests, 322 stderr failures, 74 stdout failures, 8 stderrB failures, 8 stdoutB failures, 31 post failures == Note that some tests block the test runner in both case (mcwatchpoints) and some tests block after the patch (pselect_alarm and pth_term_signal). This is due to the tests previously crashing because of pthread, and now some issues with signals is preventing them to complete. Here is the difference between the failures: $ diff tests_pre.txt tests_post.txt 49,50d48 < memcheck/tests/err_disable3 (stderr) < memcheck/tests/err_disable4 (stderr) 99d96 < memcheck/tests/threadname (stderr) 150,151d146 < callgrind/tests/threads-use (stderr) < callgrind/tests/threads (stderr) 210,216d204 < none/tests/pselect_alarm (stderr) < none/tests/pth_2sig (stderr) < none/tests/pth_atfork1 (stdout) < none/tests/pth_atfork1 (stderr) < none/tests/pth_blockedsig (stdout) < none/tests/pth_blockedsig (stderr) < none/tests/pth_cancel1 (stdout) 219,221d206 < none/tests/pth_cvsimple (stdout) < none/tests/pth_cvsimple (stderr) < none/tests/pth_exit (stderr) 224,225d208 < none/tests/pth_stackalign (stdout) < none/tests/pth_stackalign (stderr) 229d211 < none/tests/sigsusp (stderr) 234d215 < none/tests/threaded-fork (stdout) 330d310 < helgrind/tests/pth_destroy_cond (stdout) 342d321 < helgrind/tests/tc07_hbl1 (stdout) 344d322 < helgrind/tests/tc08_hbl2 (stdout) 348d325 < helgrind/tests/tc11_XCHG (stdout) 358d334 < helgrind/tests/tc21_pthonce (stdout) -- You are receiving this mail because: You are watching all bug changes.
