Bug 1371750 - Publish test results on message bus
Summary: Publish test results on message bus
Keywords:
Status: NEW
Alias: None
Product: rpm-test-trigger
Classification: Community
Component: general
Version: unreleased
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1403972
TreeView+ depends on / blocked
 
Reported: 2016-08-31 02:35 UTC by Roman Joost
Modified: 2022-03-14 03:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Roman Joost 2016-08-31 02:35:01 UTC 
For a proper integration, we'll need to publish the test results on the message bus. Three things are needed:

* result status, i.e. good/bad/needs_inspection
* testrun id
* short message
Comment 1 Jan Hutař 2017-08-07 09:56:39 UTC 
Should this be done by rpm-test-trigger, or by rpmdeplint?

Are the statuses set currently? Do we have them described somehow? What about PASS / FAIL / ERROR (infrastructure failure - please fix infrastructure and rerun) / SKIP (test is not applicable for some case, can be considered as PASS) / WAIVED (test failed, but was wived and so it can be considered as PASS with link to WaiverDB).
Comment 2 Roman Joost 2017-08-08 01:13:06 UTC 
Dear Jan,

should be done by rpm-test-trigger so it can be picked up by Errata Tool. There are currently no statuses defined. From my perspective, things like SKIP and WAIVED aren't applicable here, but rather applicable to waiver DB (correct me if I'm wrong Dan). So the three you came up with sound fine: PASS, FAIL, ERROR. Now thinking of it, didn't we already define them in rpm-test-trigger?
Note You need to log in before you can comment on or make changes to this bug.