This uses the new generator function in openQA-python-client
for reporting results to the wiki. The main advantage is that
we'll report results to the wiki as each openQA test completes,
instead of reporting all results in a lump after every test
has completed. It's also somewhat simpler, as iterate_jobs can
operate on job_ids or build. Note for review: report_results
doesn't return anything, so the use of a return statement was
unnecessary, that's why I dropped it.
We may, at this point, want to switch back to reporting by ID
in 'compose' and 'current', but I think I'd at least want to
add a method to openQA-python-client for checking if jobs have
been cloned before doing that (so if we create jobs 1, 2 and
3, then job 3 is restarted for some reason as job 4, we would
report results from 1, 2 and 4).
I don't think that it's necessary to instantiate generator like that, I believe that you can do:
but nvm.