Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-06 Thread Argotti, Yann
> 
> On 06/10/16 13:26, Conselvan De Oliveira, Ander wrote:
> > On Thu, 2016-10-06 at 13:11 +0300, Jani Nikula wrote:
> >> On Wed, 05 Oct 2016, "Argotti, Yann"  wrote:
> >>>
> 
> >
> > On Mon, 03 Oct 2016, Jairo Miramontes
> >  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.
> >> I think it should be enough, at least for a start (or should I say
> >> re-start), to freely use "regression" when things worked in the past
> >> but do not work anymore. We can then drop the keyword if it's not
> >> proven to be a regression.
> >>
> >> No strong feelings on "regression_pending", though. But I don't think
> >> you can add keywords at will, I think the field only accepts a
> >> predefined set of keywords. So you'd need to talk to Ander or Martin
> >> (Cc'd) to get the new one to bugzilla.
> >
> > I don't have admin access in bugzilla, so I would just forward such
> > requests to Martin.
> 
> Just tell me what you need when you all agree on the name :)
Thanks Martin.

Ok, so let use what it is already set, "re-starting" with "regression" key word 
but ensuring that use of this keyword is done simultaneously with good & bad 
commit id to brace that statement.
Yann 
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-06 Thread Martin Peres

On 06/10/16 13:26, Conselvan De Oliveira, Ander wrote:

On Thu, 2016-10-06 at 13:11 +0300, Jani Nikula wrote:

On Wed, 05 Oct 2016, "Argotti, Yann"  wrote:






On Mon, 03 Oct 2016, Jairo Miramontes
 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.

I think it should be enough, at least for a start (or should I say
re-start), to freely use "regression" when things worked in the past but
do not work anymore. We can then drop the keyword if it's not proven to
be a regression.

No strong feelings on "regression_pending", though. But I don't think
you can add keywords at will, I think the field only accepts a
predefined set of keywords. So you'd need to talk to Ander or Martin
(Cc'd) to get the new one to bugzilla.


I don't have admin access in bugzilla, so I would just forward such requests to
Martin.


Just tell me what you need when you all agree on the name :)

-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 


This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-06 Thread Conselvan De Oliveira, Ander
On Thu, 2016-10-06 at 13:11 +0300, Jani Nikula wrote:
> On Wed, 05 Oct 2016, "Argotti, Yann"  wrote:
> > 
> > > 
> > > > 
> > > > On Mon, 03 Oct 2016, Jairo Miramontes
> > > >  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.
> I think it should be enough, at least for a start (or should I say
> re-start), to freely use "regression" when things worked in the past but
> do not work anymore. We can then drop the keyword if it's not proven to
> be a regression.
> 
> No strong feelings on "regression_pending", though. But I don't think
> you can add keywords at will, I think the field only accepts a
> predefined set of keywords. So you'd need to talk to Ander or Martin
> (Cc'd) to get the new one to bugzilla.

I don't have admin access in bugzilla, so I would just forward such requests to
Martin.

Ander
-
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-06 Thread Jani Nikula
On Wed, 05 Oct 2016, "Argotti, Yann"  wrote:
>> > On Mon, 03 Oct 2016, Jairo Miramontes
>> >  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.

I think it should be enough, at least for a start (or should I say
re-start), to freely use "regression" when things worked in the past but
do not work anymore. We can then drop the keyword if it's not proven to
be a regression.

No strong feelings on "regression_pending", though. But I don't think
you can add keywords at will, I think the field only accepts a
predefined set of keywords. So you'd need to talk to Ander or Martin
(Cc'd) to get the new one to bugzilla.

> - either use of "regression" or "regression_pending" must be coming
> with good & bad commit when reporting the bug

Agreed.

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


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-05 Thread Argotti, Yann
> > On Mon, 03 Oct 2016, Jairo Miramontes
> >  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


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-05 Thread Argotti, Yann
> 
> On Mon, 03 Oct 2016, Jairo Miramontes
>  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

> 
> 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


Re: [Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-05 Thread Jani Nikula
On Mon, 03 Oct 2016, Jairo Miramontes 
 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?

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


[Intel-gfx] [Regression report] Weekly regression report WW40

2016-10-02 Thread Jairo Miramontes


This week regressions
+---+---+++
| BugId | Summary   | Created on | 
Bisect |

+---+---+++
| 97994 | [REGRESS] [BISECT] [i915] Monitor resolution  | 2016-09-30 | 
Yes|
| 97939 | [BYT] gem_fence_upload subtest thread-content | 2016-09-26 | 
No |
| 97991 | [i915, Surface Pro 4] Regression: No display  | 2016-09-30 | 
No |

+---+---+++


Previous Regressions
+---+---+++
| BugId | Summary   | Created on | 
Bisect |

+---+---+++
| 90112 | [BSW bisected] OglGSCloth/Lightsmark/CS/ Port | 2015-04-20 | 
Yes|
| 94590 | [KBL] igt/kms_fbcon_fbt/psr-suspend regressio | 2016-03-17 | 
No |
| 93263 | 945GM regression since 4.3| 2015-12-05 | 
No |
| 92237 | [SNB]Horrible noise (audio) via DisplayPort [ | 2015-10-02 | 
No |
| 72782 | [945GM bisected] screen blank on S3 resume on | 2013-12-17 | 
Yes|
| 97918 | [bdw regression 4.8] Severe graphics regressi | 2016-09-25 | 
No |
| 93486 | [HP Compaq dc7800 Small Form Factor PC][REGRE | 2015-12-23 | 
No |
| 92414 | [Intel-gfx] As of kernel 4.3-rc1 system will  | 2015-10-10 | 
Yes|
| 92050 | [regression]/bug introduced by commit [0e572f | 2015-09-19 | 
No |
| 93393 | Regression for Skylake modesetting in kernel  | 2015-12-16 | 
No |
| 93802 | [IVB bisected] switching to tty1 causes fifo  | 2016-01-20 | 
Yes|
| 95197 | [i915] regression in 4.6-rc5: GPU HANG: ecode | 2016-04-28 | 
No |
| 96800 | [regression] The drm-intel-nightly branch no  | 2016-07-04 | 
No |
| 95736 | [IVB bisected] *ERROR* uncleared fifo underru | 2016-05-24 | 
Yes|
| 89728 | [HSW/BDW bisected] igt / pm_rps / reset fails | 2015-03-23 | 
Yes|
| 89629 | [i965 regression]igt/kms_rotation_crc/sprite- | 2015-03-18 | 
No |
| 97878 | [SKL][REGRESSION][BISECTED] Dropped frames an | 2016-09-20 | 
Yes|
| 96938 | [HSW modeset regression] i915/drm locks up wh | 2016-07-15 | 
No |
| 87131 | [PNV regression] igt/gem_exec_lut_handle take | 2014-12-09 | 
No |
| 87726 | [BDW Bisected] OglDrvCtx performance reduced  | 2014-12-26 | 
Yes|
| 91974 | [bisected] unrecoverable black screen after k | 2015-09-11 | 
Yes|
| 96645 | [regression 4.7] [BISECT]Low package c-states | 2016-06-22 | 
Yes|
| 94430 | [HSW+nvidia] regression: display becomes "dis | 2016-03-07 | 
No |
| 97295 | Regression backlight control broken on Dell X | 2016-08-11 | 
No |
| 97888 | [regression] [i915] [SKL] Tearing / flickerin | 2016-09-21 | 
No |
| 97573 | [IVB/SNB/BYT/HSW/BDW] GuC boot kernel command | 2016-09-02 | 
No |
| 97596 | [SKL] [regression] Flickering artefact window | 2016-09-05 | 
No |
| 93971 | video framerate performance regression with U | 2016-02-02 | 
No |
| 89872 | [ HSW Bisected ] VGA was white screen when re | 2015-04-02 | 
Yes|
| 96428 | [IVB bisected] [drm:intel_dp_aux_ch] *ERROR*  | 2016-06-07 | 
Yes|
| 91959 | [865g Linux regression] GPU hang and disabled | 2015-09-10 | 
No |
| 95097 | [hdmi regression ilk] no signal to TV | 2016-04-24 | 
No |
| 97867 | [HSW][Regression] 4.6.7 and beyond causes scr | 2016-09-19 | 
No |
| 97450 | [SKL] [regression] Random display flickering  | 2016-08-23 | 
No |
| 87725 | [BDW Bisected] OglBatch7 performance reduced  | 2014-12-26 | 
Yes|
| 94337 | Linux 4.5 regression: FIFO underruns on Skyla | 2016-02-29 | 
No |
| 97820 | [BDW BYT SKL HSW IVB]Regression] [GPU Hang] w | 2016-09-15 | 
No |
| 97017 | [SKL GT3e guc bisected] ~10% performance drop | 2016-07-21 | 
Yes|
| 96916 | Regression: screen flashes with PSR enabled   | 2016-07-13 | 
No |
| 90368 | [SNB BSW SKL BXT KBL IVB] [Regression] bisect | 2015-05-08 | 
Yes|
| 94588 | [IVB/KBL/BSW/BXT/BDW] [Regression] igt/gem_re | 2016-03-17 | 
No |
| 96736 | kernel 4.6 regression: PSR causes screen to f | 2016-06-29 | 
No |
| 90134 | [BSW Bisected]GFXBench3_gl_driver/GFXBench3_g | 2015-04-22 | 
Yes|
| 96704 | kernel 4.6 regression: PSR on Haswell causes  | 2016-06-28 | 
No |
| 93782 | [i9xx TV][BISECT] vblank wait timeout on crtc | 2016-01-19 | 
Yes|
| 89632 | [i965 regression]igt/kms_universal_plane/univ | 2015-03-18 | 
No |

+---+---+++
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx