You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You query ResultsDB for all the results available for the particular update. That is not "wrong" per-se, but when an update is changed, after the tests are finished, you might be showing (e.g.) PASSED result for Depcheck, although it is more like "not tested yet".
ResultsDB's query engine supports since param, that takes a timestamp in ISO8601(YYYY-MM-DDTHH:MM:SS) format, and when used ResultsDB only returns results that are newer than the datetime specified.
I'm not sure if the update has something like "last modified" value, but if the last-modified is anything else than "created at", I'd suggest using the since param, to ensure the right information is shown.
The text was updated successfully, but these errors were encountered:
ralphbean
added
Composer
Issues related to the composer
API
Issues related to Bodhi's REST API
JS
Issues pertaining to Bodhi's JavaScript code
labels
Aug 25, 2015
You query ResultsDB for all the results available for the particular update. That is not "wrong" per-se, but when an update is changed, after the tests are finished, you might be showing (e.g.) PASSED result for Depcheck, although it is more like "not tested yet".
ResultsDB's query engine supports
since
param, that takes a timestamp in ISO8601(YYYY-MM-DDTHH:MM:SS) format, and when used ResultsDB only returns results that are newer than the datetime specified.I'm not sure if the update has something like "last modified" value, but if the last-modified is anything else than "created at", I'd suggest using the
since
param, to ensure the right information is shown.The text was updated successfully, but these errors were encountered: