From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
igt-dev@lists.freedesktop.org,
Martin Peres <martin.peres@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] runner: Treat dmesg warnings as pure warnings
Date: Wed, 14 Nov 2018 15:25:39 +0200 [thread overview]
Message-ID: <20181114132539.GO9144@intel.com> (raw)
In-Reply-To: <20181114115653.GY17124@platvala-desk.ger.corp.intel.com>
On Wed, Nov 14, 2018 at 01:56:53PM +0200, Petri Latvala wrote:
> On Tue, Nov 13, 2018 at 05:25:47PM +0000, Chris Wilson wrote:
> > I have whinged on for ages about the dmesg-warnings being an expected
> > part of kernel testing (where else is the kernel meant to log its
> > errors?) and should be treated the same as our stderr for the test. That
> > is if a test fails, it fails and does not need to be conflated with
> > whether or not there was a dmesg warning (just as the test saying why it
> > failed on stderr does not need flagging), and that a passing test with a
> > dmesg warning is simply a warn.
> >
> > The effect is that we simply remove the "dmesg-" flagging from results
> > names, as the err/dmesg output is simply collated for the error report
> > already.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Petri Latvala <petri.latvala@intel.com>
> > Cc: Martin Peres <martin.peres@linux.intel.com>
>
>
> Yep, now's a good a time as any to remove this cargo cult if ever.
>
> Some acks from kernel people in general would be nice.
>
> TODO:
> Martin: cibuglog filters ready for this
> Tomi et al: Visualization ready for this (tooltips etc)
Can I still see from the color/etc. whether there was some dmesg spew or
not? I often glance at those and would prefer to not have to go through
all the fails to find them.
--
Ville Syrjälä
Intel
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-11-14 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 17:25 [igt-dev] [PATCH i-g-t] runner: Treat dmesg warnings as pure warnings Chris Wilson
2018-11-13 18:40 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2018-11-14 11:56 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2018-11-14 13:25 ` Ville Syrjälä [this message]
2018-11-14 13:34 ` Chris Wilson
2018-11-14 13:53 ` Ville Syrjälä
2018-11-21 8:07 ` Joonas Lahtinen
2018-11-21 9:18 ` Chris Wilson
2018-11-21 10:05 ` Joonas Lahtinen
2018-11-22 9:41 ` Daniel Vetter
2018-11-22 9:42 ` Daniel Vetter
2018-11-22 12:59 ` Joonas Lahtinen
2018-11-22 14:26 ` Daniel Vetter
2018-11-14 13:04 ` [igt-dev] ✗ Fi.CI.BAT: failure for runner: Treat dmesg warnings as pure warnings (rev2) Patchwork
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=20181114132539.GO9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox