Hi folks! So I was wondering: what do folks think about running openQA's 'all' mode nightly (on the BOS deployment) instead of the 'current' mode?
'all' mode is the one I wrote a while back that tests each night's Rawhide and Branched composes in addition to the 'current' validation compose. I think it'd be nice to have an idea every day if Rawhide and/or Branched are broken. We could then actually write some kind of 'israwhidebroken.com' thing. Ideally we'd be doing this with fedmsg integration, but doing it nightly isn't too terrible. So can anyone see a reason we shouldn't? We have more tests now and it's taking longer, but we should still comfortably have enough time to do three complete test runs in a day, which would be the maximum. IIRC the 'current' tests get run first, so the nightly tests would not be delaying the more important validation tests (and if that's not the case it would be easy to change). The reason I don't do this on the happyassassin deployment is simply bandwidth - I'm already nearly at my monthly cap and downloading a bunch of images nightly would push me over. But I don't think that applies to bos. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel