Hi Joe, manual rechecks are possible for mine sweeper. The new syntax is vmware-recheck-patch. I found out vmware-recheck still triggered upstream zuul.
I think it should be possible to submit a batch job with all the patches that need to be rechecked without having to trigger the recheck from gerrit. At the end of each run the job should produce a vote. I think however Gary sent this email just to inform people that there were some nova patches that might use a recheck because the nova driver was broken by a commit now reverted. Salvatore On 19 August 2014 19:38, Joe Gordon <[email protected]> wrote: > > > > On Tue, Aug 19, 2014 at 4:22 AM, Gary Kotton <[email protected]> wrote: > >> Hi, >> Minesweeper is back up and running – this is now called “Vmware NSX CI”. >> A patch for the deprecation of the ESX driver resulted in endless >> Minesweeper failures (https://review.openstack.org/#/c/108854/). These >> were resolved by a number of patches, the last being >> https://review.openstack.org/#/c/113923/. >> So if you would like a MS +1 then please make sure that you have rebased >> your code – any code posted prior to the 14th August may not get a+1 from >> MS. >> > > Can't you guys just trigger minesweeper (vmware NSX CI) to run on code > posted prior to Aug 14th without any rebasing? And what about a recheck > command? > > >> Thanks >> Gary >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
