-Re: [DISCUSSION] Policy proposal for JIRAs opened for unit test failures without patches attached
I actually disagree -- jenkins doesn't maintain old logs forever. So, if
you open a JIRA for a failing test, please do attach the log of the failing
test, and hopefully the particular revision or git hash where it failed.
On our HDFS team here, we've started devoting days once a quarter or so as
"fixit days" -- where we all pick a small fixup task to work on and
hopefully knock down. Flaky tests are good ones for this - they don't
usually get prioritized during normal development, but when you batch them
together it's usually easy to burn them down. Having the JIRAs open and
with logs available makes it much easier to do so.
On Wed, Nov 7, 2012 at 4:26 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> There has been a recent uptick in JIRAs opened for unit test failures
> without patches attached. Since these merely duplicate information readily
> available on our Jenkins, we should institute a policy of closing them as
> Invalid if a patch is not attached to the JIRA in a timely manner (within
> hours). Simply pointing out a failing test is not
> a consequential contribution. We should also update the How To Contribute
> documentation accordingly.
> Best regards,
> - Andy
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
Software Engineer, Cloudera