Comment 3 for bug 1201035

Hi David,

Based on what happens in the Gerrit review system, certain jobs in Zuul (http://ci.openstack.org/zuul.html) are run.

For docs, we run a job that tries to build the guide both on upload of a patch set, and after the merge has been approved to go ahead.

Sometimes this job can fail , and zuul/jenkins/gerrit is trained to re-perform the tests, if you leave a code review that contains the words "recheck no bug" or "recheck bug ####".

Essentially, if it works after a 'recheck', and is happening on several reviews, it means it's a intermittent issue that should be investigated ...

This is covered in https://wiki.openstack.org/wiki/GerritJenkinsGithub#Test_Failures