Open Stack

I wonder if there's any sort of automation we can apply to this, for
example having known rechecks have "signatures" and if a failure matches
the signature it auto applies the recheck.

Alex


On Tue, Aug 27, 2013 at 9:18 AM, John Griffith
<john.griffith at solidfire.com>wrote:

> This message has gone out a number of times but I want to stress
> (particularly to those submitting to Cinder) the importance of logging
> accurate recheck information.  Please take the time to view the logs on a
> Jenkins fail before blindly entering "recheck no bug".  This is happening
> fairly frequently and quite frankly it does us no good if we don't look at
> the failure and capture things that might be going wrong in the tests.
>
> It's not hard, the CI team has put forth a good deal of effort to actually
> make it pretty easy.  There's even a "how to proceed" link provided upon
> failure to walk you through the steps.  The main thing is you have to look
> at the console output from your failed job.  Also just FYI, pep8 and
> py26/27 failures are very rarely "no bug" they are usually a real problem
> in your patch.  It would be good to pay particular attention to these
> before hitting "recheck no bug".
>
> Thanks,
> John
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130827/0dde03e2/attachment.html>