RATS tests still running against F17?
by Adam Williamson
So I took a quick look at the resultsdb and noticed that the RATS tests
- rats_sanity and rats_install - still seem to be being run against F17,
which isn't much use. (And they invariably fail). Is there a plan to
switch them to Rawhide? Do we need some kind of release-transition SOP
for AutoQA tests, to ensure they're bumped from Rawhide to Branched and
then back to Rawhide after the stable release, in a timely manner?
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
11 years, 9 months
[AutoQA] #329: implement RPM checksum verification
by fedora-badges
#329: implement RPM checksum verification
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
Currently this method is in autoqa.util module:
{{{
261 def valid_rpm(rpm_file):
262 '''Check that RPM file is valid.
263 Note: This currently only extracts RPM header and presumes the
file is
264 OK if that succeeds. Full RPM hashsum check would be nice to
have
265 implemented too (FIXME).
266 @param rpm_file RPM file path
267 @return True if file seems OK or False if there is some
problem (file
268 can't be read, RPM header is corrupt)
269 '''
...
}}}
We would like to have full RPM checksum verification, not just reading the
header and saying that it's OK. Find out how to do it and change the
method accordingly. It would be nice to have a method argument to enable
full checksum verification/fall back to original header verification,
because it can be performance intensive operation and it may not be
suitable for all our use cases).
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/329>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 9 months
Short AutoQA Downtime Today
by Tim Flink
Infra has requested a reboot of the virthost that is running autoqa01
and autoqa-stg01. Since I don't foresee a huge impact, I'm going to
start updating those hosts in preparation for a reboot.
I'll send out another email when I'm done with the updates.
Tim
11 years, 9 months
[AutoQA] #426: depcheck: "No more mirrors to try" or "Cannot retrieve repository metadata"
by fedora-badges
#426: depcheck: "No more mirrors to try" or "Cannot retrieve repository metadata"
---------------------+------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Keywords:
Blocked By: | Blocking:
---------------------+------------------------
We have quite a lot of depcheck crashes on our autoqa-stg server:
http://autoqa-
stg.fedoraproject.org/resultsdb/frontend/search?envr=&testcase=depcheck&r...
The reason is either:
{{{
yum.Errors.NoMoreMirrorsRepoError: failure:
repodata/7eb7bbf110ca81c7f6513873b352e678203e20ab2915d895067726680382cbd9-filelists.sqlite.bz2
from f16-updates: [Errno 256] No more mirrors to try.
}}}
or
{{{
yum.Errors.RepoError: Cannot retrieve repository metadata (repomd.xml) for
repository: f17. Please verify its path and try again
}}}
The weird thing is that it happens on autoqa-stg only, but not on autoqa-
production.
Up to date, I tried to put 'http_caching=none' to /etc/yum.conf and
replace mirrorlist= address with baseurl= address of the infrastructure
repository in .repo files. Neither helped.
Another idea is to have a look at #413, which dealt with similar issues,
and maybe resolve the yum repository beforehand before sticking it into
the yum config object.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/426>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
11 years, 10 months
[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