Sean Dague <s...@dague.net> writes: > We're still working through kinks in the new system, which is why it's > not fully documented yet.
We did not intend to change the general operation of 'recheck' and 'reverify', however, we did have some bugs in the early stages where we missed a possible state-change. I believe they have been worked out now and at this point you should be able to leave 'reverify bug #' on a change that has failed the gate and it will have its check jobs re-run and then automatically re-enqueued in the gate pipeline if it gets a +1. -Jim _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
