----- "AutoQA" trac@fedorahosted.org wrote:
#110: rpmlint, rpmguard: Send results to mailing list ------------------------------+--------------------------------------------- Rpmlint and rpmguard tests must be modified to send results to autoqa- results. -- Ticket URL: https://fedorahosted.org/autoqa/ticket/110
There is a small nuisance when enabling this, it means several dozen emails a day. Do you think it's a problem? If not, it is easy to implement. If you do, we can for example try to just save the log somehow and send it concatenated once a day? There would have to be some modifications then.
Anyway, we should probably think a little ahead. The test results should be stored somewhere, sending them to a mailing list is not good enough. From a short introspection I believe irb front-end does already have some database where it stores results received from autotest-server (do I say it correctly?). I think the results database should not be tied to a front-end. If we have it separated, we can instruct the tests to send all the results to that results server. Then we can collect those results (in any time interval we want) and send them to the mailing list. It also allows us to have several different front-ends (because some modifications will be needed to display results from rpmlint or rpmguard, it's not really pass or fail). Another thing, we can query the results server remotely. That means we can display the results even in external tools (koji can display rpmlint's results for a package when it is available).
Ideas? Have I got something wrong?
On Mon, 2010-01-11 at 10:09 -0500, Kamil Paral wrote:
----- "AutoQA" trac@fedorahosted.org wrote:
#110: rpmlint, rpmguard: Send results to mailing list ------------------------------+--------------------------------------------- Rpmlint and rpmguard tests must be modified to send results to autoqa- results. -- Ticket URL: https://fedorahosted.org/autoqa/ticket/110
There is a small nuisance when enabling this, it means several dozen emails a day. Do you think it's a problem? If not, it is easy to implement. If you do, we can for example try to just save the log somehow and send it concatenated once a day? There would have to be some modifications then.
Anyway, we should probably think a little ahead. The test results should be stored somewhere, sending them to a mailing list is not good enough. From a short introspection I believe irb front-end does already have some database where it stores results received from autotest-server (do I say it correctly?). I think the results database should not be tied to a front-end. If we have it separated, we can instruct the tests to send all the results to that results server. Then we can collect those results (in any time interval we want) and send them to the mailing list. It also allows us to have several different front-ends (because some modifications will be needed to display results from rpmlint or rpmguard, it's not really pass or fail).
Right on Kamil. I believe the initial idea was to have multiple front-ends for different classes of test results. The class of "package update tests" seems to be distinct enough from the installer matrix and israwhidebroken that it warrants it's own front-end. Not sure what you have in mind, but what I'd love to see is a single page that has a test matrix for each package update (either koji or bodhi ... we'd have to decide). We'd also need to decide what the test plan for a package update entails.
Another thing, we can query the results server remotely. That means we can display the results even in external tools (koji can display rpmlint's results for a package when it is available).
Ideas? Have I got something wrong?
Having the results repository able to feed data into other tools seems pretty compelling. Perhaps there are some hand-wavy type things here for the eventual message bus.
Thanks, James
autoqa-devel@lists.fedorahosted.org