Weidong Shao <[email protected]> wrote on 09/02/2014 09:35:30 PM:
> From: > > Weidong Shao <[email protected]> > > Subject: > > [OpenStack-Infra] VMWare NSX CI - recheck info > > 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? As of today, all systems, project and third-party, should restart test jobs with just "recheck" comment. Including information after "recheck" doesn't break anything upstream. See: https://review.openstack.org/#/c/108724/ and the discussion at: https://review.openstack.org/#/c/100133/ and https://review.openstack.org/#/c/109565/ Since most third-party systems are actually supporting some form of "recheck-<system name>" I am proposing a new change to the comment syntax to accommodate the need for triggering specific third-party system rechecks. Kurt Taylor (krtaylor) > > 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: [email protected] > 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 [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
