Open Stack

I believe we have more to lose by leaving the job with verification permissions than we do
by revoking them, then reinstating them at a later point, since I-2 is at the end of this month.

That way patches that are passing the gate and all other third party tests can start being
reviewed by more reviewers and core members who have verification set as a filter in their queue,

Sean M. Collins

________________________________________
From: Anita Kuno [anteaya at anteaya.info]
Sent: Monday, January 06, 2014 8:44 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs

Let me know what you consider a reasonable amount of time to continue
waiting for Tail-F NCS Jenkins before we remove verification permissions
from the account. We were just talking about this a few hours ago at a
Birds of a Feather session. We can get permissions removed from this
account. I'd just like to see agreement that we have given this account
holder a reasonable amount of time to respond prior to doing so.

If the account holder of this account is reading this email, responding
to it would certainly be a good idea.

Thanks,
Anita.


On 01/06/2014 08:36 PM, Collins, Sean wrote:
> +1 to this, there are IPv6 patches that have been -1'd by this system that I believe prevents them
> from being reviewed, since most people skip over changes that have a -1 from Jenkins jobs.
>
> I also attempted to Reach out mid December to the owner of Tail-F, but have not yet received
> a response. It is possible that he/she did reply and it got filed in the wrong folder, and I hope
> this is the case.
>
> https://review.openstack.org/#/q/topic:bp/dnsmasq-mode-keyword,n,z
>
> Sean M. Collins
>
> ________________________________________
> From: Dave Cahill [dcahill at midokura.com]
> Sent: Monday, January 06, 2014 4:36 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: tobbe at tail-f.com
> Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs
>
> Hi,
>
> "Tail-F NCS Jenkins" seems to still be causing issues. It voted -1 on some
> patches today [1][2] which seem to be fine according to all other jobs. It gives
> no information on what went wrong, so it's essentially a dead end.
>
> I've CCed the owner of the job according to the list Anita posted [3], so
> hopefully they can disable voting. Salvatore mentioned on IRC that it might
> make sense to ask the infra team to nullify the access credentials for the job
> if no response is forthcoming from the job owner.
>
> Thanks,
> Dave.
>
> [1] https://review.openstack.org/#/c/48574/
> [2] https://review.openstack.org/#/c/53052/
> [3] https://review.openstack.org/#/admin/groups/91,members
>
>
> On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon <joe.gordon0 at gmail.com<mailto:joe.gordon0 at gmail.com>> wrote:
>
>
>
> On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague <sean at dague.net<mailto:sean at dague.net>> wrote:
> On 12/23/2013 12:10 PM, Collins, Sean wrote:
>> On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote:
>>> I would suggest that external jobs should not vote until logs are publicly
>>> accessible, otherwise contributors would have no reason to understand where
>>> the negative vote came from.
>>
>> +1
>>
>> I've had Tail-F NCS Jenkins -1 some things that the OpenStack
>> Jenkins has +1'd, and other times where I've seen it +1 things that
>> OpenStack Jenkins -1'd.
>
> Agreed.
>
> I also think we need to have these systems prove themselves on
> reliability before they post votes back. A mis configured CI system can
> easily -1 the entire patch stream, and many of us use -Verified-1 as a
> filter criteria on reviews, which effectively makes that a DOS attack.
>
> Detailed public results need to come first. After those look reliable,
> voting can be allowed.
>
>
>
> FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/
>
>         -Sean
>
> --
> Sean Dague
> Samsung Research America
> sean at dague.net<mailto:sean at dague.net> / sean.dague at samsung.com<mailto:sean.dague at samsung.com>
> http://dague.net
>
>
> _______________________________________________
> 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<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
>


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev