#103 Running/Queued state is not reflected in Bodhi
Opened 11 months ago by mvadkert. Modified 9 months ago

As a user I would like to to know if my test is queued or running (more important), so I have insight into what is happening. Currently the gating only show missing, passed or failed tests.

In RHEL we provide this additional information from our kai database (CI dashboard), but that is not available yet upstream. We could store the running/queued states in resultsdb (ideally with some cleanup later on?) and make greenwave recognize these states, so bodhi shows them.

Another possibility it to have CI dashboard in upstream, but yeah :) that will take most probably more time


@pingou what do you think, can bodhi support this? I think resultsdb already process the queue/running topics.

It looks like this comes down to the listener submitting an outcome of 'QUEUED' which is not valid for this resultsdb instance:
[resultsdb_listener.consumer INFO] PipelineConsumerFedoraMessaging: Got a message 'org.centos.prod.ci.koji-build.test.queued': '2020-422cc0a6-c1aa-45cd-ad15-50c395405bed' [resultsdb_listener.senders ERROR] An error occured while uploading to resultsdb Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/resultsdb_listener/senders.py", line 107, in send **result File "/usr/lib/python3.7/site-packages/resultsdb_api.py", line 204, in create_result r = self.session.post(url, data=json.dumps(data), headers=headers) File "/usr/lib/python3.7/site-packages/resultsdb_api.py", line 113, in post return self.__resultsdb_raise_on_error(r) File "/usr/lib/python3.7/site-packages/resultsdb_api.py", line 82, in __resultsdb_raise_on_error '%s (HTTP %s)' % (r.json()['message'], r.status_code), r) resultsdb_api.ResultsDBapiException: "outcome must be one of ('PASSED', 'INFO', 'FAILED', 'NEEDS_INSPECTION', 'CRASHED') (HTTP 400)" [resultsdb_listener.consumer INFO] PipelineConsumerFedoraMessaging: Done [fedora_messaging.twisted.protocol INFO] Successfully consumed message from topic org.centos.prod.ci.koji-build.test.queued (message id 2020-422cc0a6-c1aa-45cd-ad15-50c395405bed)

Thanks, I see: https://taskotron.fedoraproject.org/resultsdb_api/api/v2.0/

I'm not sure how we can add the QUEUED and RUNNING as supported outcome.

They're added via configuration file on the resultsdb instance

Login to comment on this ticket.

Metadata