Hide Forgot
Description of problem: In the short term we are reporting results as Errata comments; see Bug 1403657 In the longer term, we will need to send rpmdeplint test results to ResultsDB in order to integrate with the Factory 2.0 workflow. http://threebean.org/blog/all-hail-resultsdb/
ResultsDB v1.0 allows PASSED, INFO, FAILED, ERROR, WAIVED, NEEDS_INSPECTION, v2.0 only allows PASSED, FAILED, INFO, NEEDS_INSPECTION but it is possible to add "note" and any number of "key=values" to the result. I assume we will stick to v2.0.
(In reply to Jan Hutař from comment #3) Might be off-topic for this bz, but I would suggest *not* to embed the name "rpm-test-trigger" in the test case name stored in ResultsDB. After all, rpm-test-trigger is just the thing *triggering* the test, it has nothing to do with the test that is actually being executed (which is really rpmdeplint and its various checks). You might reasonably imagine a future (not so distant) where someone insists that the tests be triggered in Jenkins instead of a standalone daemon. At which point rpm-test-trigger would not be needed.
I see. Makes perfect sense.
Removing needinfo for myself, since I'm not involved in Beaker/rpmdeplint, and I don't know anything about future plans for ResultsDB.