[AutoQA] #311: Improve Koji call performance with koji.ClientSession.multiCall
by fedora-badges
#311: Improve Koji call performance with koji.ClientSession.multiCall
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
We use koji calls quite extensively in watchers/tests/libraries. Some of
the calls may be sped up substantially by using multicalls (executing
multiple calls at once and waiting for a grouped result). See docstring at
koji.!ClientSession.multiCall:
{{{
Execute a multicall (multiple function calls passed to the server
and executed at the same time, with results being returned in a
batch).
Before calling this method, the self.multicall field must have
been set to True, and then one or more methods must have been called
on
the current session (those method calls will return None). On
executing
the multicall, the self.multicall field will be reset to False
(so subsequent method calls will be executed immediately)
and results will be returned in a list. The list will contain one
element
for each method added to the multicall, in the order it was added to
the multicall.
Each element of the list will be either a one-element list containing
the result of the
method call, or a map containing "faultCode" and "faultString" keys,
describing the
error that occurred during the method call.
}}}
Go through our code and re-write standard Koji calls to multicalls
whenever possible.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/311>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 2 months
rats_install test updated for review
by Hongqing Yang
Greeting,
The rats_install test has been updated to adapt the F16 release and to use rsyslog to get logs,
--initrd-inject is used to attach the ks file instead of to compress the ks file into initrd.img manually.
The source codes can be found in branch rats_install
http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;h=refs/heads/rats_in...
irb is not configured currently.
some functions there are not used by rats_install, I just leave them there for future ISO installation. They will
not affect other parts of the autoqa, just leave them there.please kindly review it and give me your feedback. Thanks.
Hongqing
12 years, 2 months
[AutoQA] #404: Crashed watchers/scheduler is not logged
by fedora-badges
#404: Crashed watchers/scheduler is not logged
--------------------------+-------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Finger Food
Component: core | Keywords:
Blocked By: | Blocking:
--------------------------+-------------------------
We currently log all sorts of errors into /var/log/autoqa. But when our
watchers or the autoqa harness crashes hard, we get no feedback. We should
fix that.
Our scripts should make sure that the exception is logged even when it
causes program crash. In Java there is a possibility to specify a default
exception handler that gets triggered if the exception is not caught. I
suppose there should be a similar facility in Python.
So, let's define a default exception handler somewhere in our library.
This exception handler should log the exception into autoqa.log with big
fat font and re-raise the exception, that's all. And all our scripts that
get executed on the server side (watchers/autoqa harness) should make use
of this default handler.
Simple enough? Or maybe there's a better way?
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/404>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 2 months
