On Fri, Feb 13, 2015 at 10:34 PM, Loic Dachary <loic@xxxxxxxxxxx> wrote: > Hi Greg, > > I'm curious to know how you handle the flow of mails from QA runs. Here is a wild guess: > > * from time to time check that the nightlies run the suites that should be run Uh, I guess? > * read the ceph-qa reports daily Yeah > * for each failed job, either relate it to an issue or create one or declare it noise Yeah > * if a job fails on an existing ticket store a link to the job if it's rare occurrence and the cause is not yet known Yeah, or just to make clear it's still happening or whatever > * bi-weekly bug scrub makes sure no issue, old or new, is forgotten Hopefully! > * at release time you decide that it is ready based on: > ** the list of urgent/immediate issues that you can browse to ensure no issue is a blocker > ** the last run of each suite to ensure they are recent enough and environmental noise did not permanently shadow anything Yeah. Well, the last run alone isn't so important; we want to see a string of clean runs because a lot of issues aren't reproduced in every run. -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
