From: Daniel Vetter <daniel@ffwll.ch>
To: "Gao, Ethan" <ethan.gao@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Add Dmesg Triage Feature: further triage i-g-t kmsg log to reduce result noise resulted from piglit dmesg defect
Date: Fri, 20 Mar 2015 11:30:25 +0100 [thread overview]
Message-ID: <20150320103025.GL1349@phenom.ffwll.local> (raw)
In-Reply-To: <167E537E1C47494F99743D99A5D56220017075BC@shsmsx102.ccr.corp.intel.com>
On Fri, Mar 20, 2015 at 01:58:02AM +0000, Gao, Ethan wrote:
> Actually, I sent to piglit ML before intel-gfx ML.
> Why It's here is because many internal guys don't subscribe to piglit ML.
Please send it to both mailing lists in one command next time around, so
that the discussion doesn't split between piglit and intel-gfx mailing
lists.
Thanks, Daniel
>
> Best Regards
> Ethan, Gao
>
> -----Original Message-----
> From: Lespiau, Damien
> Sent: Friday, March 20, 2015 1:16 AM
> To: Gao, Ethan
> Cc: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] Add Dmesg Triage Feature: further triage i-g-t kmsg log to reduce result noise resulted from piglit dmesg defect
>
> On Thu, Mar 19, 2015 at 10:36:51AM +0800, ethan gao wrote:
> > tests/igt.py: add igt env to enable or disable dmesg triage
> > framework/test/base.py: trigger dmesg triage depending on dmesg log
> > occurrence
> > framework/dmesg.py: employ dmesg triage simply for Linux dmesg
> > dmesg_triage/*: deal with kmsg log with pre-defined dmesg oops pattern
> >
> > In general, if dmesg triage is enabled and there is new dmesg along
> > with i-g-t testcases running, the new dmesg will be captured and
> > worked out a tag and head to rollback the detail when necessary, in
> > addition, on the basis of different dmesg tag or head, the final result noise of a testcase can be reduced with defined rules or strategy.
> >
> > Signed-off-by: ethan gao <ethan.gao@intel.com>
>
> That's a patch to piglit, shouldn't be sent to the piglit ml as well to get their opinion?
>
> --
> Damien
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-20 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 2:36 [PATCH] Add Dmesg Triage Feature: further triage i-g-t kmsg log to reduce result noise resulted from piglit dmesg defect ethan gao
2015-03-19 17:16 ` Damien Lespiau
2015-03-20 1:58 ` Gao, Ethan
2015-03-20 10:30 ` Daniel Vetter [this message]
2015-03-23 1:34 ` Gao, Ethan
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=20150320103025.GL1349@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ethan.gao@intel.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox