From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
piglit discussion list <piglit@lists.freedesktop.org>,
jari.tahvanainen@intel.com,
Petri Latvala <petri.latvala@intel.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH] tests/igt: dmesg noise is a kernel failure
Date: Fri, 7 Oct 2016 11:43:01 +0300 [thread overview]
Message-ID: <20161007084301.GT4329@intel.com> (raw)
In-Reply-To: <20161007071202.GA5540@nuc-i3427.alporthouse.com>
On Fri, Oct 07, 2016 at 08:12:02AM +0100, Chris Wilson wrote:
> On Fri, Oct 07, 2016 at 09:06:31AM +0200, Daniel Vetter wrote:
> > At least when testing the kernel. In normal programs pretty much all
> > the dmesg noise would simply be replaced by debug asserts, but in the
> > kernel we try rely hard to not fall over minor inconsistencies.
> >
> > Still for CI purposes there's not really a difference, hence don't
> > treat it as such.
> >
> > Motivated since once again I've seen a statistics where this was split
> > up, and then a reduction of "failures" (but in reality just trading
> > them in for more "warnings") praised as success.
> >
> > v2: Clamp to "dmesg-fail" to keep dmesg noise easily identifiable
> > (Ville).
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Acked-by: Dylan Baker <dylan@pnwbakers.com>
> > Cc: jari.tahvanainen@intel.com
> > Cc: Petri Latvala <petri.latvala@intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > ---
> > tests/igt.py | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/tests/igt.py b/tests/igt.py
> > index 7ebb03646b50..21e55e115654 100644
> > --- a/tests/igt.py
> > +++ b/tests/igt.py
> > @@ -123,6 +123,10 @@ class IGTTest(Test):
> > else:
> > self.result.result = 'fail'
> >
> > + # all dmesg noise is considered a test failure when testing the kernel
> > + if self.result.dmesg
> > + self.result.result = 'dmesg-fail'
>
> This is changing a fail to dmesg-fail. I hate that.
I don't know if there's a way to win here. We're trying to reduce 4
states to 3 states for whatever reason, so we're going to lose
information :(
Doing it this way you'll have to go through every dmesg-fail as well as
the fails if you want to see all test failures. Doing it the other way
means going through all the fails to find the dmesg warns.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-10-07 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 7:06 [PATCH] tests/igt: dmesg noise is a kernel failure Daniel Vetter
2016-10-07 7:12 ` Chris Wilson
2016-10-07 7:59 ` Tahvanainen, Jari
2016-10-07 8:43 ` Ville Syrjälä [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-06 9:07 Daniel Vetter
2016-10-06 9:16 ` Chris Wilson
2016-10-06 9:33 ` Ville Syrjälä
[not found] ` <20161006090717.23527-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2016-10-06 18:25 ` Dylan Baker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161007084301.GT4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=petri.latvala@intel.com \
--cc=piglit@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.