Re: New automated test coverage: openQA tests of critical path updates

On Thu, 2017-03-02 at 04:31 -0500, Kamil Paral wrote: > > The job can - and already does - log the exact packages it actually > > got, but I don't think there's an easy way for it to take the > > 'last_modified' date for the update at the time it does the download. > > I don't know how you

Re: New automated test coverage: openQA tests of critical path updates

> > There's one important thing we need to do first, though. Bodhi ID > > doesn't identify the thing tested uniquely, because Bodhi updates are > > mutable (and the ID is kept). So Bodhi (or any gating tools) can't > > rely on just retrieving the latest result for a particular Bodhi ID > > and

Re: New automated test coverage: openQA tests of critical path updates

2017-03-01 18:04 GMT+01:00 Adam Williamson : > I'm not so sure it's really necessary, and doing it is actually tricky > for openQA. Only the openQA job itself knows what packages it actually > tested, and it doesn't have an easy way to get the associated > timestamp.