openQA: run 'all' nightly instead of 'current'?

2015-08-17 Thread Adam Williamson
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 thi

Re: openQA: run 'all' nightly instead of 'current'?

2015-08-17 Thread Matthew Miller
On Mon, Aug 17, 2015 at 09:08:31AM -0700, Adam Williamson wrote: > 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? +1; do it! > compose. I think it'd be nice to have an idea every day if Rawhide

Re: openQA: run 'all' nightly instead of 'current'?

2015-08-17 Thread Adam Williamson
On Mon, 2015-08-17 at 15:31 -0400, Matthew Miller wrote: > On Mon, Aug 17, 2015 at 09:08:31AM -0700, Adam Williamson wrote: > > 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? > > +1; do it!

Re: openQA: run 'all' nightly instead of 'current'?

2015-08-17 Thread Jan Sedlak
I'm all for it. BOS is idle most of the time anyway and if we look at it from time to time, perhaps we will notice that our tests are broken sooner than later. But it raises a question (and I've talked about it with Kamil before): Where are we gonna put results of tests that aren't in test matrice