The resultsdb job states transition have the automagical function of filling start/end_time. Until we change the workflow, let's use the currently designed one.
Details
Details
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Comment Actions
I tested this in my local env and after a few changes, it does produce results in resultsdb that sort properly as long as there aren't any unset times in the db.
Commandeering the review to update it with working code