do not submit CRASHED result to ResultsDB
ClosedPublic

Authored by kparal on Jul 4 2016, 2:04 PM.

Details

Summary

It seems better to only post functional results to ResultsDB (passed,
failed) and keep execution statuses in ExecDB only. By removing the
failsafe decorator, any error will crash the whole directive, which will
ensure that the crash is not sent to ResultsDB, but still reflected in
ExecDB.

Test Plan

tested manually

Diff Detail

Repository
rRPMGR task-rpmgrill
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kparal retitled this revision from to do not submit CRASHED result to ResultsDB.Jul 4 2016, 2:04 PM
kparal updated this object.
kparal edited the test plan for this revision. (Show Details)
mkrizek accepted this revision.Jul 7 2016, 9:00 AM

Agreed. LGTM

(I like the failsafe decorator though! ;)

This revision is now accepted and ready to land.Jul 7 2016, 9:00 AM
This revision was automatically updated to reflect the committed changes.