On Thu, 2016-04-07 at 15:33 -0700, Adam Williamson wrote: > > ## What doesn't it do? > > 1. Produce the driver disk image, or install.img (you can build the > driver disk and place it in openQA's 'hdds' location; install.img > test is not handled) > 2. Produce the test repos (you are expected to do that, make them > available, and feed the locations to the converter) > 3. Work with a few tests (all probably fixable, but at this point I > don't want to invest more time without a few decisions) > 4. Give you an openQA instance or actually run the tests (you're > expected to bring your own instance and trigger the tests) Sorry, thought of one more item for this list: 5. Build images. That's not openQA's job. This whole effort doesn't speak to the also-live topic of 'how do we get images built when we want to test them' at all. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
