QA (public) » openQA Project (public)

cdywan wrote:

• Restarting older jobs requires some knowledge of the tests
• Assets / images are gone
• Prerequisite test modules need to be triggered to re-create the assets before re-running the failed module.

I guess you mean "parent jobs" instead of "test modules", right? Because an openQA webUI user can't trigger individual test modules unless you are talking about http://open.qa/docs/#_defining_a_custom_test_schedule_or_custom_test_modules

• The Skip restarting OK children appears to help with this

• Idea, maybe the job can define the dependency to always do the right thing?

Can we let openQA figure out prerequisite modules that have to run for a job to provide all necessary setup steps?

Do you mean necessary assets provided by parent jobs? Like a qcow image containing the installation? In that case there should already be a dialog when trying to restart a job that misses assets that will tell you that this is likely not going to work. Would you expect the job to automatically start the parent along with it automatically without asking or with asking?

As there lately were further changes regarding the re-running of tests let's assume that this was done in the meantime :)