burn down all the 'wait' stuff
ClosedPublic

Authored by adamwill on Apr 16 2016, 12:09 AM.

Details

Summary

Thanks to the glories of fedmsg, we no longer need the 'wait
for jobs to complete' stuff. Kill wait_and_report, make report_
results accept job IDs or build, use report_results instead of
wait_and_report everywhere, and drop the 'wait' config stuff.
Note this requires 1.1 of the openQA client.

Test Plan

Check that reporting results both manually and via
the fedmsg consumer works.

Diff Detail

Repository
rOPENQA fedora_openqa
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to burn down all the 'wait' stuff.Apr 16 2016, 12:09 AM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: jskladan, garretraziel.

I'm generally okay with this stuff, but just to be sure - this disables "run scheduler from terminal, it will schedule tasks and it will wait for them to finish and reports them" scenario, am I right? I'm scheduling tasks using scheduler by hand from time to time, but I don't need it to report results to wiki, so I don't mind.

adamwill added a comment.EditedApr 18 2016, 2:57 PM

Yes it does, scheduling jobs from CLI will just return as soon as the jobs are sent. I'm not using the 'wait for the jobs to complete and report them' part of that feature any more either, I don't think we need it. If you really need to report results manually in some unusual situation it's easy to do with just report (compose id) subcommand these days.

Your comment did make me realize there's one bug in this (the CLI 'schedule' command shouldn't try to report results immediately after scheduling the jobs, duh) and some other bits I should improve (I don't think -ns report is doing what we intended it to do at present, but it wasn't before this change either). I'll tweak it a bit more today.

adamwill updated this revision to Diff 2084.Apr 18 2016, 3:10 PM

CLI schedule: just print job IDs and exit after submitting

There's no sense in running report_results after scheduling
jobs, as they won't have finished yet; it only made sense for
wait_and_report. So instead of that, just print the scheduled
job IDs and exit successfully.

OK, so logging of results when submitting is actually working fine, I just forgot where it was done. So I just had to fix the compose subcommand not to try and report results after submitting jobs.

garretraziel accepted this revision.Apr 19 2016, 9:34 AM

Works without problem.

This revision is now accepted and ready to land.Apr 19 2016, 9:34 AM
This revision was automatically updated to reflect the committed changes.