Open Stack

On Wed, Sep 17, 2014 at 8:03 AM, Matt Riedemann <mriedem at linux.vnet.ibm.com>
wrote:

>
>
> On 9/16/2014 1:01 PM, Joe Gordon wrote:
>
>>
>> On Sep 15, 2014 8:31 PM, "Jay Pipes" <jaypipes at gmail.com
>> <mailto:jaypipes at gmail.com>> wrote:
>>  >
>>  > On 09/15/2014 08:07 PM, Jeremy Stanley wrote:
>>  >>
>>  >> On 2014-09-15 17:59:10 -0400 (-0400), Jay Pipes wrote:
>>  >> [...]
>>  >>>
>>  >>> Sometimes it's pretty hard to determine whether something in the
>>  >>> E-R check page is due to something in the infra scripts, some
>>  >>> transient issue in the upstream CI platform (or part of it), or
>>  >>> actually a bug in one or more of the OpenStack projects.
>>  >>
>>  >> [...]
>>  >>
>>  >> Sounds like an NP-complete problem, but if you manage to solve it
>>  >> let me know and I'll turn it into the first line of triage for Infra
>>  >> bugs. ;)
>>  >
>>  >
>>  > LOL, thanks for making me take the last hour reading Wikipedia pages
>> about computational complexity theory! :P
>>  >
>>  > No, in all seriousness, I wasn't actually asking anyone to boil the
>> ocean, mathematically. I think doing a couple things just making the
>> categorization more obvious (a UI thing, really) and doing some
>> (hopefully simple?) inspection of some control group of patches that we
>> know do not introduce any code changes themselves and comparing to
>> another group of patches that we know *do* introduce code changes to
>> Nova, and then seeing if there are a set of E-R issues that consistently
>> appear in *both* groups. That set of E-R issues has a higher likelihood
>> of not being due to Nova, right?
>>
>> We use launchpad's affected projects listings on the elastic recheck
>> page to say what may be causing the bug.  Tagging projects to bugs is a
>> manual process, but one that works pretty well.
>>
>> UI: The elastic recheck UI definitely could use some improvements. I am
>> very poor at writing UIs, so patches welcome!
>>
>>  >
>>  > OK, so perhaps it's not the most scientific or well-thought out plan,
>> but hey, it's a spark for thought... ;)
>>  >
>>  > Best,
>>  > -jay
>>  >
>>  >
>>  > _______________________________________________
>>  > OpenStack-dev mailing list
>>  > OpenStack-dev at lists.openstack.org
>> <mailto:OpenStack-dev at lists.openstack.org>
>>  > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> I'm not great with UIs either but would a dropdown of the affected
> projects be helpful and then people can filter on their "favorite" project
> and then the page is sorted by top offenders as we have today?
>
> There are times when the top bugs are infra issues (pip timeouts for
> exapmle) so you have to scroll a ways before finding something for your
> project (nova isn't the only one).



I think that would be helpful.


>
>
> --
>
> Thanks,
>
> Matt Riedemann
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140929/ad873fd7/attachment.html>