[AutoQA] #396: bodhi_util: Could not connect to bodhi!
by fedora-badges
#396: bodhi_util: Could not connect to bodhi!
---------------------+------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: core | Keywords:
Blocked By: | Blocking:
---------------------+------------------------
There seems to be some problem when trying to submit certain results to
Bodhi:
{{{
12/22 07:10:13 INFO | test:0478| Submitting results (log, email,
bodhi) for: depcheck: PASSED; 66 PASSED for kde-
l10n-4.7.4-1.fc16,PyKDE4-4.7.4-1.fc16,blinken-4.7.4-1.fc16,cantor-4.7.4-1.fc16,gwenview-4.7.4-1.fc16,kalgebra-4.7.4-1.fc16,kalzium-4.7.4-1.fc16,kamera-4.7.4-1.fc16,kanagram-4.7.4-1.fc16,kate-4.7.4-1.fc16,kbruch-4.7.4-1.fc16,kcolorchooser-4.7.4-1.fc16
,kde-
wallpapers-4.7.4-1.fc16,kdeaccessibility-4.7.4-1.fc16,kdeadmin-4.7.4-1.fc16,kdeartwork-4.7.4-1.fc16,kdebase-4.7.4-2.fc16
,kdebase-runtime-4.7.4-2.fc16,kdebase-
workspace-4.7.4-5.fc16,kdeedu-4.7.4-1.fc16,kdegames-4.7.4-1.fc16,kdegraphics-4.7.4-1.fc16
,kdegraphics-strigi-analyzer-4.7.4-1.fc16,kdegraphics-
thumbnailers-4.7.4-1.fc16,kdelibs-4.7.4-1.fc16,kdemultimedia-4.7.4-2.fc16,kdenetwork-4.7.4-1.fc16,kdepim-4.7.4-1.fc16
,kdepim-runtime-4.7.4-1.fc16,kdepimlibs-4.7.4-2.fc16,kdeplasma-
addons-4.7.4-1.fc16,kdesdk-4.7.4-1.fc16,kdetoys-4.7.4-1.fc16,kdeutils-4.7.4-1.fc16,kgamma-4.7.4-1.fc16,kgeography-4.7.4-1.fc16,khangman-4.7.4-1.fc16,kig-4.7.4-1.fc16,kiten-4.7.4-1.fc16,klettres-4.7.4-1.fc16,kmplot-4.7.4-1.fc16,kolourpaint-4.7.4-1.fc16,konsole-4.7.4-1.fc16
,kross-
interpreters-4.7.4-1.fc16,kruler-4.7.4-1.fc16,ksaneplugin-4.7.4-1.fc16,ksnapshot-4.7.4-1.fc16,kstars-4.7.4-1.fc16,ktouch-4.7.4-1.fc16,kturtle-4.7.4-1.fc16,kwordquiz-4.7.4-1.fc16,libkdcraw-4.7.4-1.fc16,libkdeedu-4.7.4-1.fc16,libkexiv2-4.7.4-1.fc16,libkipi-4.7.4-1.fc16,libksane-4.7.4-1.fc16,marble-4.7.4-1.fc16,okular-4.7.4-1.fc16
,oxygen-icon-
theme-4.7.4-1.fc16,parley-4.7.4-1.fc16,rocs-4.7.4-1.fc16,smokegen-4.7.4-1.fc16,smokekde-4.7.4-1.fc16,smokeqt-4.7.4-1.fc16,step-4.7.4-1.fc16,svgpart-4.7.4-1.fc16
12/22 07:10:13 INFO | test:0361| Log created:
/usr/share/autotest/results/default/depcheck/results/kde-
l10n-4.7.4-1.fc1.html
12/22 07:10:13 INFO | test:0307| Email not sent: "depcheck: PASSED;
66 PASSED for kde-
l10n-4.7.4-1.fc16,PyKDE4-4.7.4-1.fc16,blinken-4.7.4-1.fc16,cantor-4.7.4-1.fc16,gwenview-4.7.4-1.fc16,kalgebra-4.7.4-1.fc16,kalzium-4.7.4-1.fc16,kamera-4.7.4-1.fc16,kanagram-4.7.4-1.fc16,kate-4.7.4-1.fc16,kbruch-4.7.4-1.fc16,kcolorchooser-4.7.4-1.fc16
,kde-
wallpapers-4.7.4-1.fc16,kdeaccessibility-4.7.4-1.fc16,kdeadmin-4.7.4-1.fc16,kdeartwork-4.7.4-1.fc16,kdebase-4.7.4-2.fc16
,kdebase-runtime-4.7.4-2.fc16,kdebase-
workspace-4.7.4-5.fc16,kdeedu-4.7.4-1.fc16,kdegames-4.7.4-1.fc16,kdegraphics-4.7.4-1.fc16
,kdegraphics-strigi-analyzer-4.7.4-1.fc16,kdegraphics-
thumbnailers-4.7.4-1.fc16,kdelibs-4.7.4-1.fc16,kdemultimedia-4.7.4-2.fc16,kdenetwork-4.7.4-1.fc16,kdepim-4.7.4-1.fc16
,kdepim-runtime-4.7.4-1.fc16,kdepimlibs-4.7.4-2.fc16,kdeplasma-
addons-4.7.4-1.fc16,kdesdk-4.7.4-1.fc16,kdetoys-4.7.4-1.fc16,kdeutils-4.7.4-1.fc16,kgamma-4.7.4-1.fc16,kgeography-4.7.4-1.fc16,khangman-4.7.4-1.fc16,kig-4.7.4-1.fc16,kiten-4.7.4-1.fc16,klettres-4.7.4-1.fc16,kmplot-4.7.4-1.fc16,kolourpaint-4.7.4-1.fc16,konsole-4.7.4-1.fc16
,kross-
interpreters-4.7.4-1.fc16,kruler-4.7.4-1.fc16,ksaneplugin-4.7.4-1.fc16,ksnapshot-4.7.4-1.fc16,kstars-4.7.4-1.fc16,ktouch-4.7.4-1.fc16,kturtle-4.7.4-1.fc16,kwordquiz-4.7.4-1.fc16,libkdcraw-4.7.4-1.fc16,libkdeedu-4.7.4-1.fc16,libkexiv2-4.7.4-1.fc16,libkipi-4.7.4-1.fc16,libksane-4.7.4-1.fc16,marble-4.7.4-1.fc16,okular-4.7.4-1.fc16
,oxygen-icon-
theme-4.7.4-1.fc16,parley-4.7.4-1.fc16,rocs-4.7.4-1.fc16,smokegen-4.7.4-1.fc16,smokekde-4.7.4-1.fc16,smokeqt-4.7.4-1.fc16,step-4.7.4-1.fc16,svgpart-4.7.4-1.fc16"
12/22 07:10:17 ERROR|bodhi_util:0278| An error occured:
ServerError(http://aqd/bodhi/list, 500, Internal Server Error)
12/22 07:10:17 ERROR|bodhi_util:0279| Could not connect to bodhi!
12/22 07:10:17 ERROR|bodhi_util:0279| Could not post a comment to bodhi
}}}
This is running on my development machine when using mock_fedorainfra
tool. I haven't spotted it yet on either production or staging machine.
That indicates that this could be a problem inside the mock_fedorainfra
tool. I have seen this bug happening several times, always only for
updates consisting of several builds.
Investigate whether this is really a problem in mock_fedorainfra and then
act on accordingly (fix the problem/report in upstream).
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/396>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 10 months
Rebooting Autoqa Hosts
by Tim Flink
As a heads up, infra wants to update and reboot the virthost for
autoqa01 and autoqa-stg01 so I'm in the process of stopping jobs,
updating the VMs and will be shutting them down for a little bit.
I'll send out another email when everything is done.
Tim
11 years, 11 months
Re: AutoQA project status
by Kamil Paral
Replying to correct list, replies below.
> rats_install:
>
> rats_install has been updated to install packages fedora,
> fedora+updates,
> fedora+updates+updates-testing respectively. But it does not work
> since
> bug 820106
I have commented this in ticket 414.
https://fedorahosted.org/autoqa/ticket/414#comment:9
>
> iso watcher:
>
> watcher.py in directory watchers/iso/, written by James Laska
> originally,
> watches all the ISO at dl.fedoraproject.org/pub/alt/stage/. It will
> download
> all the ISOs released there.
Several times we have agreed there is no point in watcher downloading ISOs. The watcher and the test client do not run on the same machine. The watcher must pass just the URL.
>
> mediakit_sanity:
>
> mediakit sanity is used to test the sanity of all the ISOs.it has
> been
> finished. It will download all ISOs and check the size, md5sum, repo
> closure
> and file conflicts. the reasonable size of the Spins need to be
> adjusted.
If it has been finished, can you post a patch into ReviewBoard? Thanks.
>
> anaconda_install:
>
> anaconda_install will test all the ISO installation. Now it can run
> with
> single kickstart file. In order to cover all the test cases, all the
> ksfiles
> should be iterated, this can be implemented in the host with extra
> args or
> in the control file.
What's the status of this one?
>
> upgrade:
>
> upgrade will test the upgrade. First the older release should be
> installed,
> then reboot the system from the current release with kickstart
> 'upgrade' option.
> Since the libvirt 0.8 cannot attach CDROM, it is hang. Now libvirt
> 0.9 is released,
> the detail should be investigated.
This is news to me, I didn't know you've been working on this as well. Is that just a future plan or you have some code already?
Thanks,
Kamil
11 years, 11 months
[AutoQA] #423: Add contact information to emails
by fedora-badges
#423: Add contact information to emails
--------------------------+-------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: trivial | Milestone: Finger Food
Component: core | Keywords:
Blocked By: | Blocking:
--------------------------+-------------------------
Bastien Nocera complaint that emails sent by AutoQA didn't have any footer
with contact information.
You can currently click through the included link to the test report and
then you can find link to AutoQA wiki page, but it's true we could improve
that situation by adding a link to the wiki page directly to the email.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/423>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 11 months
Playing around with Sikuli
by Tim Flink
I've been wanting to try out Sikuli (http://www.sikuli.org) for a while
now and finally got around to making it build and work on Fedora.
The basic concept is to create GUI test cases based on images instead of
absolute (x,y) coordinates (like selenium), scripted key sequences
(openqa) or using an accessability layer (like dogtail).
I've put together a tarball with source and build scripts if anyone
else wants to try it out:
http://tflink.fedorapeople.org/tools/sikuli/README_build-sikuli.txt
http://tflink.fedorapeople.org/tools/sikuli/fedora-sikuli-20120220.tar.gz
The distribution method is a really dirty hack but I've been able to
build on both F15 and F16 after installing a huge number of -devel
dependencies and building all of Sikuli's direct dependencies from
source. Xpresser (https://wiki.ubuntu.com/Xpresser) might be another
option - it's a re-implementation of the concepts from Sikuli. It seems
to be missing some of Sikuli's features but would likely be quite a bit
easier to build and integrate.
One of the things I have in mind is to attempt automating at least some
of the installation test cases because a lot of them pass most of the
time and they can be a bit mind-numbing to do over and over again. I'm
of the opinion that our human resources could be put to better use than
monkey-button-pushing their way through simple test cases.
A non-trivial amount of work would be needed before we could fully
utilize this (fixing the code so that it is package-able, better
integration with VNC etc.) but I'm wondering if it could be a good
candidate for automating some of the installation test cases.
I've written two test cases for Sikuli thus far: a simple DVD graphical
install and graphical firstboot. I had to workaround some timing issues
due to occasional lag in the VM's VNC interface but they seem to be
working well with F17 Alpha RC2 for now.
F17 DVD Basic Graphical Install:
http://tflink.fedorapeople.org/tools/sikuli/f17-basicGraphicalDVD_sikuli....
F17 Graphical Firstboot:
http://tflink.fedorapeople.org/tools/sikuli/f17-graphicalFirstboot_sikuli...
- NOTE: This only works some of the time due to rhbz#750527 which was
closed with no bug comment by the developers. I'm going to bug them
about this but will likely update the test case to work with
unpredictable order of the firstboot screens.
To run those test cases, extract them somewhere and point the Sikuli
IDE at the extracted directories.
I'm going to be running my basic graphical install testcase for
different F17 releases to get an initial feel for how fragile the test
cases are and how much effort would be required to maintain these kinds
of test cases over a release.
Anyhow, long email over. Any thoughts on whether this might be worth
investigating farther?
Tim
11 years, 11 months
