Open Stack

Oh, I see that "recheck varmour" did work. Thanks for pointing that out.

On Wed, Sep 17, 2014 at 4:12 PM, Gary Duan <gduan at varmour.com> wrote:

> We do support recheck already. "recheck varmour", "recheck no bug" etc
> should work. I updated the wiki page as well.
>
> Thanks,
> Gary
>
> On Wed, Sep 17, 2014 at 3:22 PM, Anita Kuno <anteaya at anteaya.info> wrote:
>
>> On 09/17/2014 05:38 PM, Kevin Benton wrote:
>> > I talked with Gary and he is planning on avoiding voting -1
>> automatically,
>> > so I'm happy with the account being re-enabled.
>> > Allowing 'recheck' isn't as big of a concern if it's not blocking
>> patches.
>>
>> Hi Kevin,
>>
>> Thanks for helping Gary, this has been the whole plan behind the third
>> party structure, operators helping operators, so I really appreciate you
>> stepping up and supporting his work. Thank you, Kevin.
>>
>> Well supporting recheck is part of the requirements for every ci:
>> http://ci.openstack.org/third_party.html#requirements So if this account
>> doesn't support this, I still don't understand how they ever had voting
>> permissions.
>>
>> Let's get recheck syntax supported please.
>>
>> Thanks,
>> Anita.
>> >
>> > On Wed, Sep 17, 2014 at 10:11 AM, Anita Kuno <anteaya at anteaya.info>
>> wrote:
>> >
>> >> On 09/17/2014 12:54 PM, Gary Duan wrote:
>> >>> Hi,
>> >>>
>> >>> I have looked into all the votes our CI system posted. It votes -1 for
>> >>> about one tenth of patches. Among these -1 votes, about 3/10 were
>> correct
>> >>> vote, and the rest were caused by same two test cases related to
>> ipv6. I
>> >>> have skipped these two cases.
>> >>>
>> >>> One thing I want to say is, among all CI systems, we probably run the
>> >> most
>> >>> test cases, more than 200 tempest tests.
>> >> I do encourage you to post verifiable data when you make assertions of
>> >> this nature.
>> >>
>> >>
>> >>> It runs and votes reliably for the
>> >>> past week, except those two IPv6 test cases.
>> >> Again, data would be great to see.
>> >>
>> >>>
>> >>> I am working with Kevin in the past a few days. I want to change the
>> >>> comment message format, so our result can show up on the right hand
>> side
>> >> of
>> >>> the page. We will not to vote -1 but only give an indication of
>> failure.
>> >>>
>> >>> Thanks,
>> >>> Gary
>> >> That's wonderful Gary, good work.
>> >>
>> >> When Kevin lets me know that his concerns outlined in this email:
>> >>
>> >>
>> http://lists.openstack.org/pipermail/third-party-announce/2014-September/000023.html
>> >> have been addressed you can be re-enabled and non-voting. Once you
>> >> follow the process outlined in the prior email to get Neutron to vouch
>> >> for your ability to vote responsibly, you may have voting permissions.
>> >>
>> >> Having a presence on irc would also be very helpful.
>> >>
>> >> Thank you,
>> >> Anita.
>> >>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Sep 16, 2014 at 2:50 PM, Anita Kuno <anteaya at anteaya.info>
>> >> wrote:
>> >>>
>> >>>> vArmour CI is having difficulty and has been disabled several times
>> >>>> recently. It is currently disabled.
>> >>>>
>> >>>> Once it is re-enabled it will have comment only permissions on most
>> >>>> repos and can vote on the sandbox repo.
>> >>>>
>> >>>> Please stabilize your ci and follow these instructions to get voting
>> >>>> permissions on your system:
>> >>>>
>> >>>>
>> >>
>> http://ci.openstack.org/third_party.html#permissions-on-your-third-party-system
>> >>>>
>> >>>> Thank you,
>> >>>> Anita.
>> >>>>
>> >>>> _______________________________________________
>> >>>> Third-party-announce mailing list
>> >>>> Third-party-announce at lists.openstack.org
>> >>>>
>> >>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Third-party-announce mailing list
>> >>> Third-party-announce at lists.openstack.org
>> >>>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>> >>>
>> >>
>> >>
>> >> _______________________________________________
>> >> Third-party-announce mailing list
>> >> Third-party-announce at lists.openstack.org
>> >>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>> >>
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Third-party-announce mailing list
>> > Third-party-announce at lists.openstack.org
>> >
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>> >
>>
>>
>> _______________________________________________
>> Third-party-announce mailing list
>> Third-party-announce at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>>
>
>
> This message is for the designated and authorized recipient only and may
> contain privileged, proprietary, confidential or otherwise private
> information relating to vArmour Networks, Inc. and is the sole property of
> vArmour Networks, Inc.  Any views or opinions expressed are solely those of
> the author and do not necessarily represent those of vArmour Networks, Inc.
> If you have received this message in error, or if you are not authorized to
> receive it, please notify the sender immediately and delete the original
> message and any attachments from your system immediately. If you are not a
> designated or authorized recipient, any other use or retention of this
> message or its contents is prohibited.
>
> _______________________________________________
> Third-party-announce mailing list
> Third-party-announce at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce
>
>


-- 
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/third-party-announce/attachments/20140917/374b38cd/attachment-0001.html>