On Thu, Mar 12, 2020 at 11:38:56AM -0600, Tim Flink wrote:
I brought this up in the last ci meeting but as I'm learning more, I think this topic could use a broader discussion to be more sure that I and maybe others aren't misunderstanding what the broader plan is.
Below, I've written up a summary of my understanding of what's going on around generic checks. I figure that's the fastest way to see what I'm
Are generic checks the Automated Tests in bodhi that are run even if the packages does not configure any tests/tests.yml? If yes, could the Automated Test Results page show (links to) some description of what the test is supposed to be testing, as well as links to sources and configuration of the tests?
When I look at the Automated Test Results page of random Fedora update, for example
https://bodhi.fedoraproject.org/updates/FEDORA-2020-a7ca62459a
I see a bunch of dist.rpm* tests ... but clicking for example the dist.rpmgrill.buld-log or dist.rpmgrill.setxid lines brings me in both cases to
https://taskotron.fedoraproject.org/artifacts/all/56cc7402-316c-11ea-8436-52...
where I see
{ "module" : "Setxid", "order" : 91, "results" : [], "run_time" : 0, "status" : "completed" }, { "module" : "BuildLog", "order" : 92, "results" : [], "run_time" : 0, "status" : "completed" },
but with no indication what that test actually did and tested.