All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
@ 2014-09-17 11:34 Chris Wilson
  2014-09-17 15:54 ` Daniel Vetter
  0 siblings, 1 reply; 8+ messages in thread
From: Chris Wilson @ 2014-09-17 11:34 UTC (permalink / raw)
  To: intel-gfx

At the end of a subtest, check for any WARNs or ERRORs (or worse!)
emitted since the start of our test and FAIL the subtest if any are
found. This will prevent silent failures due to oops from going amiss or
being falsely reported as TIMEOUTs.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 lib/igt_core.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 104 insertions(+), 10 deletions(-)

diff --git a/lib/igt_core.c b/lib/igt_core.c
index 5d41468..29a262f 100644
--- a/lib/igt_core.c
+++ b/lib/igt_core.c
@@ -208,6 +208,7 @@ static char *run_single_subtest = NULL;
 static bool run_single_subtest_found = false;
 static const char *in_subtest = NULL;
 static struct timespec subtest_time;
+static int subtest_kmsg = -1;
 static bool in_fixture = false;
 static bool test_with_subtests = false;
 static enum {
@@ -229,14 +230,14 @@ enum {
 
 __attribute__((format(printf, 1, 2)))
 static void kmsg(const char *format, ...)
-#define KERN_EMER	"<0>"
-#define KERN_ALERT	"<1>"
-#define KERN_CRIT	"<2>"
-#define KERN_ERR	"<3>"
-#define KERN_WARNING	"<4>"
-#define KERN_NOTICE	"<5>"
-#define KERN_INFO	"<6>"
-#define KERN_DEBUG	"<7>"
+#define KMSG_EMER	"<0>"
+#define KMSG_ALERT	"<1>"
+#define KMSG_CRIT	"<2>"
+#define KMSG_ERR	"<3>"
+#define KMSG_WARNING	"<4>"
+#define KMSG_NOTICE	"<5>"
+#define KMSG_INFO	"<6>"
+#define KMSG_DEBUG	"<7>"
 {
 	va_list ap;
 	FILE *file;
@@ -478,7 +479,7 @@ out:
 		exit(ret == -1 ? 0 : IGT_EXIT_INVALID);
 
 	if (!list_subtests) {
-		kmsg(KERN_INFO "%s: executing\n", command_str);
+		kmsg(KMSG_INFO "%s: executing\n", command_str);
 		print_version();
 
 		oom_adjust_for_doom();
@@ -610,7 +611,11 @@ bool __igt_run_subtest(const char *subtest_name)
 		return false;
 	}
 
-	kmsg(KERN_INFO "%s: starting subtest %s\n", command_str, subtest_name);
+	kmsg(KMSG_INFO "%s: starting subtest %s\n", command_str, subtest_name);
+
+	subtest_kmsg = open("/dev/kmsg", O_RDONLY | O_NONBLOCK);
+	if (subtest_kmsg != -1)
+		lseek(subtest_kmsg, 0, SEEK_END);
 
 	gettime(&subtest_time);
 	return (in_subtest = subtest_name);
@@ -643,6 +648,82 @@ static bool succeeded_one = false;
 static bool failed_one = false;
 static int igt_exitcode;
 
+static char *readfile(int fd)
+{
+	char *buf;
+	int len, end;
+
+	end = 0;
+	len = 4096;
+	buf = malloc(4096);
+	if (buf == NULL)
+		return NULL;
+
+	do {
+		char *newbuf;
+		int rem = len - end - 1;
+		int ret = read(fd, buf + end, rem);
+		if (ret <= 0)
+			break;
+
+		end += ret;
+		if (ret < rem)
+			break;
+
+		newbuf = realloc(buf, len *= 2);
+		if (newbuf == NULL)
+			break;
+
+		buf = newbuf;
+	} while (1);
+
+	if (end == 0) {
+		free(buf);
+		return NULL;
+	}
+
+	buf[end] = '\0';
+	return buf;
+}
+
+static int print_kernlog(char *log, int prio)
+#define PRIO_EMER	0
+#define PRIO_ALERT	1
+#define PRIO_CRIT	2
+#define PRIO_ERR	3
+#define PRIO_WARNING	4
+#define PRIO_NOTICE	5
+#define PRIO_INFO	6
+#define PRIO_DEBUG	7
+{
+	int count = 0;
+
+	do {
+		char *s, *t;
+		int lvl;
+
+		s = strchr(log, ';');
+		if (s == NULL)
+			break;
+
+		t = strchr(s + 1, '\n');
+		if (t == NULL)
+			break;
+
+		*t = '\0';
+
+		lvl = atoi(log);
+		if (lvl <= prio) {
+			puts(s+1);
+			count++;
+		}
+
+		log = t + 1;
+	} while (*log);
+
+	return count;
+}
+
 static void exit_subtest(const char *) __attribute__((noreturn));
 static void exit_subtest(const char *result)
 {
@@ -653,7 +734,20 @@ static void exit_subtest(const char *result)
 	elapsed = now.tv_sec - subtest_time.tv_sec;
 	elapsed += (now.tv_nsec - subtest_time.tv_nsec) * 1e-9;
 
+	if (subtest_kmsg != -1) {
+		char *log;
+
+		log = readfile(subtest_kmsg);
+		if (log) {
+			if (print_kernlog(log, PRIO_WARNING))
+				result = "FAIL";
+			free(log);
+		}
+		close(subtest_kmsg);
+	}
+
 	printf("Subtest %s: %s (%.3fs)\n", in_subtest, result, elapsed);
+
 	in_subtest = NULL;
 	longjmp(igt_subtest_jmpbuf, 1);
 }
-- 
2.1.0

^ permalink raw reply related	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-17 11:34 [PATCH] lib/core: Check for kernel error messages and FAIL if any are found Chris Wilson
@ 2014-09-17 15:54 ` Daniel Vetter
  2014-09-17 16:01   ` Chris Wilson
  0 siblings, 1 reply; 8+ messages in thread
From: Daniel Vetter @ 2014-09-17 15:54 UTC (permalink / raw)
  To: Chris Wilson; +Cc: intel-gfx

On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
> At the end of a subtest, check for any WARNs or ERRORs (or worse!)
> emitted since the start of our test and FAIL the subtest if any are
> found. This will prevent silent failures due to oops from going amiss or
> being falsely reported as TIMEOUTs.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

We already have this in piglit, including filtering for non-i915 issues
(which especially on s/r tests happen a lot). So this just duplicates
that.

Also imo it's nice to differentiate between test failures and dmesg noise
in at least some tests, so clamping to fail isn't the righ thing to do I
think.
-Daniel

> ---
>  lib/igt_core.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 104 insertions(+), 10 deletions(-)
> 
> diff --git a/lib/igt_core.c b/lib/igt_core.c
> index 5d41468..29a262f 100644
> --- a/lib/igt_core.c
> +++ b/lib/igt_core.c
> @@ -208,6 +208,7 @@ static char *run_single_subtest = NULL;
>  static bool run_single_subtest_found = false;
>  static const char *in_subtest = NULL;
>  static struct timespec subtest_time;
> +static int subtest_kmsg = -1;
>  static bool in_fixture = false;
>  static bool test_with_subtests = false;
>  static enum {
> @@ -229,14 +230,14 @@ enum {
>  
>  __attribute__((format(printf, 1, 2)))
>  static void kmsg(const char *format, ...)
> -#define KERN_EMER	"<0>"
> -#define KERN_ALERT	"<1>"
> -#define KERN_CRIT	"<2>"
> -#define KERN_ERR	"<3>"
> -#define KERN_WARNING	"<4>"
> -#define KERN_NOTICE	"<5>"
> -#define KERN_INFO	"<6>"
> -#define KERN_DEBUG	"<7>"
> +#define KMSG_EMER	"<0>"
> +#define KMSG_ALERT	"<1>"
> +#define KMSG_CRIT	"<2>"
> +#define KMSG_ERR	"<3>"
> +#define KMSG_WARNING	"<4>"
> +#define KMSG_NOTICE	"<5>"
> +#define KMSG_INFO	"<6>"
> +#define KMSG_DEBUG	"<7>"
>  {
>  	va_list ap;
>  	FILE *file;
> @@ -478,7 +479,7 @@ out:
>  		exit(ret == -1 ? 0 : IGT_EXIT_INVALID);
>  
>  	if (!list_subtests) {
> -		kmsg(KERN_INFO "%s: executing\n", command_str);
> +		kmsg(KMSG_INFO "%s: executing\n", command_str);
>  		print_version();
>  
>  		oom_adjust_for_doom();
> @@ -610,7 +611,11 @@ bool __igt_run_subtest(const char *subtest_name)
>  		return false;
>  	}
>  
> -	kmsg(KERN_INFO "%s: starting subtest %s\n", command_str, subtest_name);
> +	kmsg(KMSG_INFO "%s: starting subtest %s\n", command_str, subtest_name);
> +
> +	subtest_kmsg = open("/dev/kmsg", O_RDONLY | O_NONBLOCK);
> +	if (subtest_kmsg != -1)
> +		lseek(subtest_kmsg, 0, SEEK_END);
>  
>  	gettime(&subtest_time);
>  	return (in_subtest = subtest_name);
> @@ -643,6 +648,82 @@ static bool succeeded_one = false;
>  static bool failed_one = false;
>  static int igt_exitcode;
>  
> +static char *readfile(int fd)
> +{
> +	char *buf;
> +	int len, end;
> +
> +	end = 0;
> +	len = 4096;
> +	buf = malloc(4096);
> +	if (buf == NULL)
> +		return NULL;
> +
> +	do {
> +		char *newbuf;
> +		int rem = len - end - 1;
> +		int ret = read(fd, buf + end, rem);
> +		if (ret <= 0)
> +			break;
> +
> +		end += ret;
> +		if (ret < rem)
> +			break;
> +
> +		newbuf = realloc(buf, len *= 2);
> +		if (newbuf == NULL)
> +			break;
> +
> +		buf = newbuf;
> +	} while (1);
> +
> +	if (end == 0) {
> +		free(buf);
> +		return NULL;
> +	}
> +
> +	buf[end] = '\0';
> +	return buf;
> +}
> +
> +static int print_kernlog(char *log, int prio)
> +#define PRIO_EMER	0
> +#define PRIO_ALERT	1
> +#define PRIO_CRIT	2
> +#define PRIO_ERR	3
> +#define PRIO_WARNING	4
> +#define PRIO_NOTICE	5
> +#define PRIO_INFO	6
> +#define PRIO_DEBUG	7
> +{
> +	int count = 0;
> +
> +	do {
> +		char *s, *t;
> +		int lvl;
> +
> +		s = strchr(log, ';');
> +		if (s == NULL)
> +			break;
> +
> +		t = strchr(s + 1, '\n');
> +		if (t == NULL)
> +			break;
> +
> +		*t = '\0';
> +
> +		lvl = atoi(log);
> +		if (lvl <= prio) {
> +			puts(s+1);
> +			count++;
> +		}
> +
> +		log = t + 1;
> +	} while (*log);
> +
> +	return count;
> +}
> +
>  static void exit_subtest(const char *) __attribute__((noreturn));
>  static void exit_subtest(const char *result)
>  {
> @@ -653,7 +734,20 @@ static void exit_subtest(const char *result)
>  	elapsed = now.tv_sec - subtest_time.tv_sec;
>  	elapsed += (now.tv_nsec - subtest_time.tv_nsec) * 1e-9;
>  
> +	if (subtest_kmsg != -1) {
> +		char *log;
> +
> +		log = readfile(subtest_kmsg);
> +		if (log) {
> +			if (print_kernlog(log, PRIO_WARNING))
> +				result = "FAIL";
> +			free(log);
> +		}
> +		close(subtest_kmsg);
> +	}
> +
>  	printf("Subtest %s: %s (%.3fs)\n", in_subtest, result, elapsed);
> +
>  	in_subtest = NULL;
>  	longjmp(igt_subtest_jmpbuf, 1);
>  }
> -- 
> 2.1.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-17 15:54 ` Daniel Vetter
@ 2014-09-17 16:01   ` Chris Wilson
  2014-09-17 16:13     ` Daniel Vetter
  0 siblings, 1 reply; 8+ messages in thread
From: Chris Wilson @ 2014-09-17 16:01 UTC (permalink / raw)
  To: Daniel Vetter; +Cc: intel-gfx

On Wed, Sep 17, 2014 at 05:54:52PM +0200, Daniel Vetter wrote:
> On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
> > At the end of a subtest, check for any WARNs or ERRORs (or worse!)
> > emitted since the start of our test and FAIL the subtest if any are
> > found. This will prevent silent failures due to oops from going amiss or
> > being falsely reported as TIMEOUTs.
> > 
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> 
> We already have this in piglit, including filtering for non-i915 issues
> (which especially on s/r tests happen a lot). So this just duplicates
> that.

What piglit? I don't see QA reports involving pigligt and they seem to
mistake kernel OOPSes for benign TIMEOUTs quite frequently.
 
> Also imo it's nice to differentiate between test failures and dmesg noise
> in at least some tests, so clamping to fail isn't the righ thing to do I
> think.

Also where is my XFAIL? :)
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-17 16:01   ` Chris Wilson
@ 2014-09-17 16:13     ` Daniel Vetter
  2014-09-17 16:30       ` Chris Wilson
  2014-09-18  8:34       ` Daniel, Thomas
  0 siblings, 2 replies; 8+ messages in thread
From: Daniel Vetter @ 2014-09-17 16:13 UTC (permalink / raw)
  To: Chris Wilson, Daniel Vetter, intel-gfx, Thomas Daniel

On Wed, Sep 17, 2014 at 6:01 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Wed, Sep 17, 2014 at 05:54:52PM +0200, Daniel Vetter wrote:
>> On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
>> > At the end of a subtest, check for any WARNs or ERRORs (or worse!)
>> > emitted since the start of our test and FAIL the subtest if any are
>> > found. This will prevent silent failures due to oops from going amiss or
>> > being falsely reported as TIMEOUTs.
>> >
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>
>> We already have this in piglit, including filtering for non-i915 issues
>> (which especially on s/r tests happen a lot). So this just duplicates
>> that.
>
> What piglit? I don't see QA reports involving pigligt and they seem to
> mistake kernel OOPSes for benign TIMEOUTs quite frequently.

Can you please reply with the relevant bugzillas? Since about 2 months
QA is supposed to be using the piglit runner for their framework, so
any difference in test results compared to what piglit would report is
fail.

Note though that the piglit timeout support was busted by some
refactoring from Dylan Baker, Thomas has patches to fix that again.
But if this is indeed a failure from QA then I'll escalate this like
mad.

>> Also imo it's nice to differentiate between test failures and dmesg noise
>> in at least some tests, so clamping to fail isn't the righ thing to do I
>> think.
>
> Also where is my XFAIL? :)

The plan is to have a server with piglit jsons of latest -nightly for
the full set of machines. QA hasn't yet delivered that though ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-17 16:13     ` Daniel Vetter
@ 2014-09-17 16:30       ` Chris Wilson
  2014-09-18  8:34       ` Daniel, Thomas
  1 sibling, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2014-09-17 16:30 UTC (permalink / raw)
  To: Daniel Vetter; +Cc: intel-gfx

On Wed, Sep 17, 2014 at 06:13:56PM +0200, Daniel Vetter wrote:
> On Wed, Sep 17, 2014 at 6:01 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > On Wed, Sep 17, 2014 at 05:54:52PM +0200, Daniel Vetter wrote:
> >> On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
> >> > At the end of a subtest, check for any WARNs or ERRORs (or worse!)
> >> > emitted since the start of our test and FAIL the subtest if any are
> >> > found. This will prevent silent failures due to oops from going amiss or
> >> > being falsely reported as TIMEOUTs.
> >> >
> >> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >>
> >> We already have this in piglit, including filtering for non-i915 issues
> >> (which especially on s/r tests happen a lot). So this just duplicates
> >> that.
> >
> > What piglit? I don't see QA reports involving pigligt and they seem to
> > mistake kernel OOPSes for benign TIMEOUTs quite frequently.
> 
> Can you please reply with the relevant bugzillas? Since about 2 months
> QA is supposed to be using the piglit runner for their framework, so
> any difference in test results compared to what piglit would report is
> fail.

All reproduction recipes still use the bare test runner, e.g.
https://bugs.freedesktop.org/show_bug.cgi?id=83969 from today. Which is
also a good example for the test missing the kernel warning that
triggered the actual fail. I don't see any problem with having the bare
test runner being able to detect an oops during a subtest. I am pretty
sure there have been timeouts within the last month or so that have been
mutex deadlocks due to a driver oops - but that would require a bit of
digging to confirm.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-17 16:13     ` Daniel Vetter
  2014-09-17 16:30       ` Chris Wilson
@ 2014-09-18  8:34       ` Daniel, Thomas
  2014-09-18 10:01         ` Daniel Vetter
  2014-09-18 10:02         ` Daniel Vetter
  1 sibling, 2 replies; 8+ messages in thread
From: Daniel, Thomas @ 2014-09-18  8:34 UTC (permalink / raw)
  To: Daniel Vetter, Chris Wilson, intel-gfx

> -----Original Message-----
> From: daniel.vetter@ffwll.ch [mailto:daniel.vetter@ffwll.ch] On Behalf Of
> Daniel Vetter
> Sent: Wednesday, September 17, 2014 5:14 PM
> To: Chris Wilson; Daniel Vetter; intel-gfx; Daniel, Thomas
> Subject: Re: [Intel-gfx] [PATCH] lib/core: Check for kernel error messages
> and FAIL if any are found
> 
> On Wed, Sep 17, 2014 at 6:01 PM, Chris Wilson <chris@chris-wilson.co.uk>
> wrote:
> > On Wed, Sep 17, 2014 at 05:54:52PM +0200, Daniel Vetter wrote:
> >> On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
> >> > At the end of a subtest, check for any WARNs or ERRORs (or worse!)
> >> > emitted since the start of our test and FAIL the subtest if any are
> >> > found. This will prevent silent failures due to oops from going
> >> > amiss or being falsely reported as TIMEOUTs.
> >> >
> >> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >>
> >> We already have this in piglit, including filtering for non-i915
> >> issues (which especially on s/r tests happen a lot). So this just
> >> duplicates that.
> >
> > What piglit? I don't see QA reports involving pigligt and they seem to
> > mistake kernel OOPSes for benign TIMEOUTs quite frequently.
> 
> Can you please reply with the relevant bugzillas? Since about 2 months QA is
> supposed to be using the piglit runner for their framework, so any difference
> in test results compared to what piglit would report is fail.
> 
> Note though that the piglit timeout support was busted by some refactoring
> from Dylan Baker, Thomas has patches to fix that again.
I haven't seen any patches for piglit...

Thomas.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-18  8:34       ` Daniel, Thomas
@ 2014-09-18 10:01         ` Daniel Vetter
  2014-09-18 10:02         ` Daniel Vetter
  1 sibling, 0 replies; 8+ messages in thread
From: Daniel Vetter @ 2014-09-18 10:01 UTC (permalink / raw)
  To: Daniel, Thomas; +Cc: intel-gfx

On Thu, Sep 18, 2014 at 10:34 AM, Daniel, Thomas
<thomas.daniel@intel.com> wrote:
>> -----Original Message-----
>> From: daniel.vetter@ffwll.ch [mailto:daniel.vetter@ffwll.ch] On Behalf Of
>> Daniel Vetter
>> Sent: Wednesday, September 17, 2014 5:14 PM
>> To: Chris Wilson; Daniel Vetter; intel-gfx; Daniel, Thomas
>> Subject: Re: [Intel-gfx] [PATCH] lib/core: Check for kernel error
>> Note though that the piglit timeout support was busted by some refactoring
>> from Dylan Baker, Thomas has patches to fix that again.
> I haven't seen any patches for piglit...

http://patchwork.freedesktop.org/patch/33584/

Cheers, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] lib/core: Check for kernel error messages and FAIL if any are found
  2014-09-18  8:34       ` Daniel, Thomas
  2014-09-18 10:01         ` Daniel Vetter
@ 2014-09-18 10:02         ` Daniel Vetter
  1 sibling, 0 replies; 8+ messages in thread
From: Daniel Vetter @ 2014-09-18 10:02 UTC (permalink / raw)
  To: Daniel, Thomas, Thomas Wood; +Cc: intel-gfx

Oh, just noticed that I've added the wrong Thomas ;-)
-Daniel

On Thu, Sep 18, 2014 at 10:34 AM, Daniel, Thomas
<thomas.daniel@intel.com> wrote:
>> -----Original Message-----
>> From: daniel.vetter@ffwll.ch [mailto:daniel.vetter@ffwll.ch] On Behalf Of
>> Daniel Vetter
>> Sent: Wednesday, September 17, 2014 5:14 PM
>> To: Chris Wilson; Daniel Vetter; intel-gfx; Daniel, Thomas
>> Subject: Re: [Intel-gfx] [PATCH] lib/core: Check for kernel error messages
>> and FAIL if any are found
>>
>> On Wed, Sep 17, 2014 at 6:01 PM, Chris Wilson <chris@chris-wilson.co.uk>
>> wrote:
>> > On Wed, Sep 17, 2014 at 05:54:52PM +0200, Daniel Vetter wrote:
>> >> On Wed, Sep 17, 2014 at 12:34:46PM +0100, Chris Wilson wrote:
>> >> > At the end of a subtest, check for any WARNs or ERRORs (or worse!)
>> >> > emitted since the start of our test and FAIL the subtest if any are
>> >> > found. This will prevent silent failures due to oops from going
>> >> > amiss or being falsely reported as TIMEOUTs.
>> >> >
>> >> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> >>
>> >> We already have this in piglit, including filtering for non-i915
>> >> issues (which especially on s/r tests happen a lot). So this just
>> >> duplicates that.
>> >
>> > What piglit? I don't see QA reports involving pigligt and they seem to
>> > mistake kernel OOPSes for benign TIMEOUTs quite frequently.
>>
>> Can you please reply with the relevant bugzillas? Since about 2 months QA is
>> supposed to be using the piglit runner for their framework, so any difference
>> in test results compared to what piglit would report is fail.
>>
>> Note though that the piglit timeout support was busted by some refactoring
>> from Dylan Baker, Thomas has patches to fix that again.
> I haven't seen any patches for piglit...
>
> Thomas.



-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2014-09-18 10:02 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-09-17 11:34 [PATCH] lib/core: Check for kernel error messages and FAIL if any are found Chris Wilson
2014-09-17 15:54 ` Daniel Vetter
2014-09-17 16:01   ` Chris Wilson
2014-09-17 16:13     ` Daniel Vetter
2014-09-17 16:30       ` Chris Wilson
2014-09-18  8:34       ` Daniel, Thomas
2014-09-18 10:01         ` Daniel Vetter
2014-09-18 10:02         ` Daniel Vetter

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.