Open Stack

Thanks, Aaron did that for me. Thanks, Aaron!

However, for some reason, the NSX CI has not been triggered. The error is
still linked to the last test on August 31st
http://208.91.1.172/logs/neutron/116094/4/416303/

Aaron, could the vmware NSX CI be down?

Thanks!
Weidong


On Tue, Sep 2, 2014 at 11:13 PM, Sukhdev Kapur <sukhdevkapur at gmail.com>
wrote:

> Please try recheck-vmware
>
> Others seem to use this to force recheck.
>
> regards..
> -Sukhdev
>
>
>
> On Tue, Sep 2, 2014 at 7:35 PM, Weidong Shao <weidongshao at gmail.com>
> wrote:
>
>>
>> Hi,
>>
>> I have a CL (https://review.openstack.org/#/c/116094/) that fails in
>> VMWare NSX CI. I could not figure out the proper way to do a recheck on
>> that.  On the error log page, there is a link to the team's wiki, from
>> which this instruction is given:
>>     "To issue a recheck, submit a comment with the following text:
>> vmware-recheck"
>>
>> I did that but it did not trigger a recheck.
>> Could someone help me on this?
>>
>>
>> *A related note on NSX CI:*
>>
>> Apparently, the VMWare CI does not follow the guideline from
>> http://ci.openstack.org/third_party.html to include contacts, recheck
>> instruction etc. Some other CIs provide better messages on failure. e.g,
>>
>> A10
>>
>> Contact: a10-openstack-ci at a10networks.com
>>
>> Additional information:
>> https://wiki.openstack.org/wiki/ThirdPartySystems/A10_Networks_CI
>>
>> Or from RYU CI
>>
>> "Build failed. Leave a comment with 'recheck-ryu' to rerun a check.
>> ('recheck' will be ignored.)"
>>
>> Could someone from the NSX/Openstack team make the necessary changes?
>>
>> Thanks,
>> Wei
>>
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20140902/e33e9476/attachment.html>