It is, but... Our CI infra was being overloaded by the amount of review submissions. To 'throttle' things a bit, I tweaked the CI job dispatcher (zuul) to require code-review +2 before starting jobs.
Just get your diff reviewed, and then it will work its way through the system. But a side note tho, you have an email from David Peet, and it applies to a couple of your reviews... they seem to be stuck because they have a dependency on a review that has merged. If you can manually remove the dependency from your review, that would be best. But you might need to rebase your diff to 'notice' the fact that your dependency has already been merged. > On Feb 12, 2016, at 1:14 AM, Édouard Thuleau <[email protected]> wrote: > > Hi Karl, > > it is no longer possible to do a 'recheck no bug' on our review? > > Édouard. > > On Wed, Feb 3, 2016 at 11:48 PM, Karl Klashinsky <[email protected]> wrote: > Sorry, I should have sent out an update earlier. > > Our CI is back to normal, and the backlog has been mostly processed. There are > still some outstanding performance issues on hypervisor that hosts > *.opencontrail.org > machines, but we are operational. > > Please report any issues via CI alias (cc:'d) or #general channel in > Opencontrail Slack team. > > -- > Klash > > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org > -- Klash _______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
