Filing a JIRA for a flaky test just checked in is not really what motivated my original mail. Let me just say if we think opening JIRAs simply for Jenkins test failures is good practice, then we should simply automate it and have Jenkins do it. My opinion is without detail, analysis, or patches such JIRAs are noise, they don't add anything to reports we can pull from build result mails.
On Friday, March 22, 2013, Sergey Shelukhin wrote: > I think filing JIRAs for recently added/recently broken tests that became > flaky (outside of jenkins) should be ok, I filed one some time ago :) > Otherwise it's ok to commit a flaky test and then not fix it yourself > because whoever raises a JIRA has to provide a patch himself.. > > On Thu, Mar 21, 2013 at 6:57 AM, Andrew Purtell > <[email protected]<javascript:;>> > wrote: > > > Can we refrain from filing JIRAs for failed ASF Jenkins tests until the > > builds are running faster? At least, let's confirm the test also fails > > locally. Preferably the filer also has a patch that fixes the problem. > > > > I may go into JIRA and reap a bunch of issues which do not meet the above > > criteria. Please let me know if you have concerns about that. > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
