Recently, incomplete tests changed status from "crash" to "incomplete". Previously, we could filter out these results with the [expected-crashes] section in the config file. At the moment, there is no way to filter out "incomplete" tests, and they show up as failures in JUnit, even if they are known issues. This makes them look like regressions.
I have sent a patch that should resolve this issue: https://bugs.freedesktop.org/show_bug.cgi?id=92205 tl;dr: there's an uncaught exception in the test running thread, which causes it to return incomplete.
(In reply to Dylan from comment #1) > I have sent a patch that should resolve this issue: > https://bugs.freedesktop.org/show_bug.cgi?id=92205 > > tl;dr: there's an uncaught exception in the test running thread, which > causes it to return incomplete. sorry, wrong link: https://patchwork.freedesktop.org/patch/60810/
Patch 1/2 fixes this issue. Please push it to master.
b9e49a9..2b690c5 master -> master
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.