<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 27, 2013 at 10:26 AM, Alex Gaynor <span dir="ltr"><<a href="mailto:alex.gaynor@gmail.com" target="_blank">alex.gaynor@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.</div>
</blockquote><div> </div><div class="gmail_default" style="font-family:'courier new',monospace">I think we kinda already have that, the recheck list and the bug ID assigned to it no? Automatically scanning said list and doing the recheck automatically seems like overkill in my opinion. At some point human though/interaction is required and I don't think it's too much to ask a technical contributor to simply LOOK at the output from the test runs against their patches and help out a bit. At the very least if you didn't test your patch yourself and waited for Jenkins to tell you it's broken I would hope that a submitter would at least be motivated to fix their own issue that they introduced.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><br>
</div><div>Alex</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Tue, Aug 27, 2013 at 9:18 AM, John Griffith <span dir="ltr"><<a href="mailto:john.griffith@solidfire.com" target="_blank">john.griffith@solidfire.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div style="font-family:courier new,monospace">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.</div>
<div style="font-family:courier new,monospace"><br></div><div style="font-family:courier new,monospace">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".</div>
<div style="font-family:courier new,monospace"><br></div><div style="font-family:courier new,monospace">Thanks,</div><div style="font-family:courier new,monospace">
John</div></div>
<br></div></div>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div dir="ltr">"I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)<br>
"The people's good is the highest law." -- Cicero<br><div>GPG Key fingerprint: 125F 5C67 DFE9 4084</div></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>