Hey, folks. I was thinking this week that, in the context of the RATS discussion, it's probably worth looking at the big changes to lorax coming out of the treebuilder branch:
https://fedoraproject.org/wiki/Anaconda/Features/Lorax-TreeBuilder
I filed a ticket for the specific impact on the compose_tree test:
https://fedorahosted.org/autoqa/ticket/392
But I wondered if the change has any other impacts on AutoQA in general, and RATS. Does it make it more or less viable that we could simply automate the creation of boot.iso for RATS runs, and avoid asking releng to provide it for us? Or is this still something releng should own and we should co-ordinate with releng on?
I don't mind composing the boot.iso using AutoQA. But:
1. We need to upload it somewhere so that it can be detected and used by other tests (e.g. rats_install). It would be nice keep at least 7 last composes available, but we are very low on disk space. Also I imagine that not only our tests will want to use it after it is available, but other people will regularly download it too (similarly to daily desktop composes). Releng storage would be best to use here.
2. Who's going to tackle compose issues? If the compose fails, do we really want to debug that issue, find broken component, work on resolving it? Because at least for me the compose process is a black magic. /me votes no for further responsibilities.
Ideally releng should manage the test script and solve the issues, and we should just provide the automation and error reporting for them (if they don't have their own and better capabilities). But I don't know whether they are willing to do that, because there is probably no policy in current Fedora saying that Branched boot.iso should be composeable every day, so it's not strictly part of their job. Adam, maybe you have better information here?