On Wed, 2010-01-13 at 13:35 -0500, James Laska wrote:
On Wed, 2010-01-13 at 12:44 -0500, James Laska wrote:
> On Tue, 2010-01-12 at 08:48 -0500, James Laska wrote:
> > > James, will you install the updated code to our test server so
> > > we can see it in action,
> >
> > Certainly, I can build and install the autoqa package from git head to
> > the autotest client systems. There are a few other patches out for
> > review on the list ... do we want those included?
>
> autoqa-0.3-3 tagged [1] and been deployed.
It doesn't appear that rpmguard tests are being scheduled alongside
rpmlint tests. I think one issue I saw was that the version of autotest
we're using might not have the utf8 fix that you sent upstream.
Despite that, I think something else might be lurking.
Investigating ...
Trying to figure out how to gather information from the scheduler. It
seems to be rejecting job creation for rpmguard tests. What I've tried
so far ...
1) First, mimic how the watcher would schedule any tests...
# su -c 'autoqa post-koji-build --name python-sphinx --kojitag
dist-f12-updates-candidate --arch x86_64 python-sphinx-0.6.4-1.fc12' -
autotest
Created job:
post-koji-build:rpmlint.x86_64 (id 4537)
Error received from web server:
HTTP Error 500: Internal Server Error
ERROR: failed to schedule job post-koji-build:rpmguard.x86_64
2) Now, this prepares the control file and calls 'atest' as noted
below ...
# /usr/bin/atest job create -m *x86_64 post-koji-build:rpmguard.x86_64
-f /tmp/autoqa-control.sR24-A
Error received from web server:
HTTP Error 500: Internal Server Error
I've got some tips from the #autotest folks, will try to get more
information shortly.
Thanks,
James