From: "Argotti, Yann" <yann.argotti@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Jairo Miramontes <jairo.daniel.miramontes.caton@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
otc gfx qa <otc.gfx.qa@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Regression report] Weekly regression report WW40
Date: Wed, 5 Oct 2016 15:39:27 +0000 [thread overview]
Message-ID: <59BBB0A1A3BECC4BA75F1465F36C66AC3736C014@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <59BBB0A1A3BECC4BA75F1465F36C66AC3736BFCE@IRSMSX103.ger.corp.intel.com>
> > On Mon, 03 Oct 2016, Jairo Miramontes
> > <jairo.daniel.miramontes.caton@linux.intel.com> wrote:
> > > This week regressions
> >
> > In the past we used "regression", "bisect_pending", and "bisected" in
> > the bugzilla "Keywords" field. Can we start using those again, please?
>
> I think this is a very good idea Jani. So we can start to scrub current
> regression (and then igt linked one) and update accordingly.
> Yann
Two additional thoughts are:
- add "regression_pending" (vs "regression") as well as keyword to indicate where bug reporter has doubt on the fact it is or not a regression.
- either use of "regression" or "regression_pending" must be coming with good & bad commit when reporting the bug
Yann
>
> >
> > BR,
> > Jani.
> >
> >
> > --
> > Jani Nikula, Intel Open Source Technology Center
_______________________________________________
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-05 15:39 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 22:50 Regression report] Weekly regression report WW45 jairo.daniel.miramontes.caton
2015-11-14 1:11 ` [Regression report] Weekly regression report WW46 jairo.daniel.miramontes.caton
2015-12-01 6:45 ` [Regression report] Weekly regression report WW48 jairo.daniel.miramontes.caton
2015-12-05 0:34 ` [Regression report] Weekly regression report WW49 jairo.daniel.miramontes.caton
2015-12-11 23:54 ` [Regression report] Weekly regression report WW50 jairo.daniel.miramontes.caton
2015-12-20 20:04 ` [Regression report] Weekly regression report WW51 jairo.daniel.miramontes.caton
2016-01-10 6:11 ` [Regression report] Weekly regression report WW2 jairo.daniel.miramontes.caton
2016-02-01 0:56 ` [Regression report] Weekly regression report WW05 jairo.daniel.miramontes.caton
2016-02-15 1:30 ` [Regression report] Weekly regression report WW07 jairo.daniel.miramontes.caton
2016-02-20 4:35 ` [Regression report] Weekly regression report WW08 jairo.daniel.miramontes.caton
[not found] ` <60334.10.254.52.171.1455942960.squirrel@linux.intel.com>
2016-02-29 5:49 ` [Regression report] Weekly regression report WW09 jairo.daniel.miramontes.caton
2016-03-14 3:42 ` [Regression report] Weekly regression report WW11 jairo.daniel.miramontes.caton
2016-03-27 2:12 ` [Regression report] Weekly regression report WW14 jairo.daniel.miramontes.caton
[not found] ` <2933.10.254.183.82.1459044774.squirrel@linux.intel.com>
2016-04-03 15:57 ` jairo.daniel.miramontes.caton
2016-05-09 4:20 ` [Regression report] Weekly regression report WW19 jairo.daniel.miramontes.caton
2016-05-17 15:45 ` [Regression report] Weekly regression report WW20 jairo.daniel.miramontes.caton
2016-05-30 3:16 ` [Regression report] Weekly regression report WW22 jairo.daniel.miramontes.caton
2016-06-06 1:31 ` [Regression report] Weekly regression report WW23 jairo.daniel.miramontes.caton
2016-06-15 16:58 ` [Regression report] Weekly regression report WW24 Jairo Miramontes
2016-06-20 2:31 ` [Regression report] Weekly regression report WW25 Jairo Miramontes
2016-06-25 19:12 ` [Regression report] Weekly regression report WW26 Jairo Miramontes
2016-07-03 21:46 ` [Regression report] Weekly regression report WW27 Jairo Miramontes
2016-07-10 21:04 ` [Regression report] Weekly regression report WW28 Jairo Miramontes
2016-07-18 5:04 ` [Regression report] Weekly regression report WW29 Jairo Miramontes
2016-07-18 5:11 ` Jairo Miramontes
2016-07-25 0:50 ` [Regression report] Weekly regression report WW30 Jairo Miramontes
2016-08-01 2:30 ` [Regression report] Weekly regression report WW31 Jairo Miramontes
2016-08-08 5:57 ` [Regression report] Weekly regression report WW32 Jairo Miramontes
2016-08-15 2:30 ` [Regression report] Weekly regression report WW33 Jairo Miramontes
2016-08-22 0:11 ` [Regression report] Weekly regression report WW34 Jairo Miramontes
2016-08-28 23:35 ` [Regression report] Weekly regression report WW35 Jairo Miramontes
2016-09-05 6:01 ` [Regression report] Weekly regression report WW36 Jairo Miramontes
2016-09-12 0:47 ` [Regression report] Weekly regression report WW37 Jairo Miramontes
2016-09-18 21:58 ` [Regression report] Weekly regression report WW38 Jairo Miramontes
2016-09-26 2:31 ` [Regression report] Weekly regression report WW39 Jairo Miramontes
2016-10-03 3:26 ` [Regression report] Weekly regression report WW40 Jairo Miramontes
2016-10-05 12:54 ` Jani Nikula
2016-10-05 15:29 ` Argotti, Yann
2016-10-05 15:39 ` Argotti, Yann [this message]
2016-10-06 10:11 ` Jani Nikula
2016-10-06 10:26 ` Conselvan De Oliveira, Ander
2016-10-06 10:42 ` Martin Peres
2016-10-06 11:37 ` Argotti, Yann
2016-10-10 3:58 ` [Regression report] Weekly regression report WW41 Jairo Miramontes
2016-10-10 8:48 ` Jani Nikula
2016-10-17 4:13 ` [Regression report] Weekly regression report WW42 Jairo Miramontes
2016-10-18 8:20 ` Jani Nikula
2016-10-18 13:32 ` Vega, Ricardo
2016-10-18 14:13 ` Jani Nikula
2016-10-18 15:45 ` Jairo Miramontes
2016-10-24 13:42 ` [Regression report] Weekly regression report WW43 Jairo Miramontes
2016-10-31 3:20 ` [Regression report] Weekly regression report WW44 Jairo Miramontes
2016-11-06 23:15 ` [Regression report] Weekly regression report WW45 Jairo Miramontes
2016-11-22 5:48 ` [Regression report] Weekly regression report WW47 Jairo Miramontes
2016-11-28 2:21 ` [Regression report] Weekly regression report WW48 Jairo Miramontes
2016-11-28 9:41 ` Jani Nikula
2016-11-30 17:04 ` Miramontes Caton, Jairo Daniel
2016-12-05 5:08 ` [Regression report] Weekly regression report WW49 Jairo Miramontes
2016-12-18 22:27 ` [Regression report] Weekly regression report WW51 Jairo Miramontes
2017-01-08 21:28 ` [Regression report] Weekly regression report WW02 Jairo Miramontes
2017-01-16 2:50 ` [Regression report] Weekly regression report WW03 Jairo Miramontes
2017-01-23 5:04 ` Jairo Miramontes
2017-01-28 23:21 ` [Regression report] Weekly regression report WW04 Jairo Miramontes
2017-02-13 4:21 ` [Regression report] Weekly regression report WW06 Jairo Miramontes
2017-03-25 0:14 ` [Regression report] Weekly regression report WW12 Jairo Miramontes
2017-04-02 22:21 ` [Regression report] Weekly regression report WW13 Jairo Miramontes
2017-04-24 21:23 ` [Regression report] Weekly regression report WW16 Jairo Miramontes
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=59BBB0A1A3BECC4BA75F1465F36C66AC3736C014@IRSMSX103.ger.corp.intel.com \
--to=yann.argotti@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jairo.daniel.miramontes.caton@linux.intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=otc.gfx.qa@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 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.