Bug 92205

Summary:	tests with incomplete status are not filtered by configuration files
Product:	piglit	Reporter:	Mark Janes <mark.a.janes>
Component:	infrastructure	Assignee:	Dylan Baker <baker.dylan.c>
Status:	CLOSED FIXED	QA Contact:	Piglit Mailing List <piglit>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Mark Janes 2015-09-30 20:09:50 UTC

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.

Comment 1 Dylan Baker 2015-10-01 00:39:27 UTC

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.

Comment 2 Dylan Baker 2015-10-01 00:43:45 UTC

(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/

Comment 3 Mark Janes 2015-10-01 17:16:00 UTC

Patch 1/2 fixes this issue.  Please push it to master.

Comment 4 Dylan Baker 2015-10-01 17:20:10 UTC

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.