T151 - proper job status usage in resultsdb directive
ClosedPublic

Authored by tflink on Apr 29 2014, 4:33 PM.

Details

Summary

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.

Test Plan

NaN

Diff Detail

Lint
Lint Skipped
Unit
Unit Tests Skipped
tflink commandeered this revision.Apr 29 2014, 7:21 PM
tflink edited reviewers, added: jskladan; removed: tflink.

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

tflink updated this revision.Apr 29 2014, 7:21 PM
  • fixing unit tests to work with changed resultsdb code
jskladan accepted this revision.Apr 30 2014, 7:52 AM

Thanks for the tests! Everything looks good to me.

tflink closed this revision.Apr 30 2014, 3:57 PM

Closed by commit rLTRN92fce8c04096 (authored by @jskladan, committed by @tflink).