autoqa-devel January 2012

autoqa-devel@lists.fedorahosted.org

7 participants
40 discussions

[AutoQA] #363: depcheck: don't require specific release
by fedora-badges 15 Feb '12

15 Feb '12

#363: depcheck: don't require specific release -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Finger Food Component: tests | Keywords: -------------------------+-------------------------------------------------- Depcheck currently requires machine with a specific Fedora release installed to test matching repositories. From tests/depcheck/control.autoqa: {{{ # because we simulate installing packages, the autotest label of the correct distribution # must be present (like 'fc13') If proper label is not found the test will not execute if autoqa_args.has_key('nvrs'): from autoqa.util import get_distro distro = get_distro(autoqa_args['nvrs'][0]) labels.append(distro) }}} Josef says it's possible to cancel this constraint. That would allow us to test arbitrary repository on arbitrary machine (improving performance and maybe allowing us to have less machines). There is one thing worth mentioning: Depcheck is tightly tied to yum, and any weird behavior might be caused by yum. If we cancel above-mentioned constraint, we can no longer suppose that "depcheck crashed on f15-updates, therefore I should try to reproduce it on my F15 machine". It will be necessary to look which machine the test was executed on and try to reproduce it in the same environment if possible. The goal of this ticket is test properly whether cancelling the requirement works correctly. That means to test executing depcheck for F15 repos on F14 machine, or vice versa, and comparing the results with behavior prior to this change. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/363> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #401: Tests crash when querying Bodhi for nss-softokn-3.13.1-15.fc15
by fedora-badges 14 Feb '12

14 Feb '12

#401: Tests crash when querying Bodhi for nss-softokn-3.13.1-15.fc15 ---------------------+------------------------ Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: core | Keywords: Blocked By: | Blocking: ---------------------+------------------------ Found here: https://fedorahosted.org/pipermail/autoqa-results/Week-of- Mon-20120109/571191.html The problem is reported in upstream: https://fedorahosted.org/bodhi/ticket/660 This probably influences production. We should decide whether we will catch these errors and how we will behave in that case. Lets leave this open until the upstream bug is solved and/or we have some good workaround (what sort of?). -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/401> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #335: autotest_server autodetection fails
by fedora-badges 10 Feb '12

10 Feb '12

#335: autotest_server autodetection fails --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: minor | Milestone: Finger Food Component: core | Keywords: --------------------+------------------------------------------------------- Currently if we want to have working hyperlinks to logs, we have to fill in 'autotest_server' in autoqa.conf, because autodetection from hostname get's overwritten by empty value from the log. The links then look like this: http:///results/20-root/brutus.test.redhat.com/helloworld/results/full.log /autoqa: {{{ # Hardcoded defaults for the 'general' section conf = { 'local': 'false', 'testdir': '/usr/share/autotest/client/site_tests', 'eventdir': '/usr/share/autoqa/events', 'notification_email': '', 'autotest_server': socket.gethostname(), } conf = autoqa_conf.get_section('general', conf) conf = autoqa_conf.get_section('notifications', conf) # FIXME: conf['autotest_server'] gets overwritten here by empty value coming # from autoqa_conf }}} We can solve this by some easy hack or more properly by solving ticket #255. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/335> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #397: upgradepath: pending builds checking is broken
by fedora-badges 09 Feb '12

09 Feb '12

#397: upgradepath: pending builds checking is broken ---------------------+------------------------ Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: tests | Keywords: Blocked By: | Blocking: ---------------------+------------------------ I found these weird reports in upgradepath output: {{{ 13:18:04 INFO | ============================================================ 13:18:04 INFO | drupal7-views-3.0-1.fc15 into dist-f15-updates 13:18:04 INFO | ============================================================ 13:18:05 INFO | [ OK ] dist-f15 13:18:05 INFO | Latest package: None 13:18:08 INFO | [FAIL] f16 + f16-updates 13:18:08 INFO | Latest package: drupal7-views-3.0-0.1.rc3.fc16 13:18:08 INFO | Latest pending package: drupal7-views-3.0-1.el5 13:18:08 INFO | Error: Tested package must be less than or equal to the latest (pending) package. 13:18:08 INFO | [FAIL] f17 13:18:08 INFO | Latest package: drupal7-views-3.0-0.1.rc3.fc17 13:18:08 INFO | Latest pending package: None 13:18:08 INFO | Error: Tested package must be less than or equal to the latest (pending) package. 13:18:08 INFO | RESULT: FAILED }}} Pending package is .el5, instead of .fc16. Or: {{{ 13:27:58 INFO | ============================================================ 13:27:58 INFO | gdb-7.3.1-47.fc15 into dist-f15-updates 13:27:58 INFO | ============================================================ 13:27:59 INFO | [ OK ] dist-f15 13:27:59 INFO | Latest package: gdb-7.2.90.20110429-36.fc15 13:28:03 INFO | [ OK ] f16 + f16-updates 13:28:03 INFO | Latest package: gdb-7.3.50.20110722-10.fc16 13:28:03 INFO | Latest pending package: gdb-7.3.1-47.fc15 13:28:04 INFO | [ OK ] f17 13:28:04 INFO | Latest package: gdb-7.4.50.20120103-4.fc17 13:28:04 INFO | Latest pending package: None 13:28:04 INFO | RESULT: PASSED }}} Pending package is .fc15 instead of .fc16. After some manual attempts it seems that this is a bug in the Bodhi client library. Reported upstream: https://fedorahosted.org/bodhi/ticket/657 Let's have this ticket open until the upstream bug is fixed. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/397> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

another set of incorrectly tagged builds
by Kamil Paral 07 Feb '12

07 Feb '12

Hey Luke, here is another batch. Some of them are from Oct 2011, which is really weird. I understand it might be hard to find the actual bugs that cause invalid tagging. Can we at least as a partial remedy set up that tag-sanity-checking script of yours to run periodically and automatically fix problems it finds (like builds being tagged into -updates and -updates-pending at the same time)? Thanks, Kamil $ koji list-tag-history --build firefox-7.0.1-3.fc15 Mon Oct 24 16:44:58 2011: firefox-7.0.1-3.fc15 tagged into dist-f15-updates-candidate by stransky Mon Oct 24 16:52:53 2011: firefox-7.0.1-3.fc15 tagged into dist-f15-updates-testing-pending by bodhi Thu Oct 27 01:17:38 2011: firefox-7.0.1-3.fc15 untagged from dist-f15-updates-candidate by bodhi Thu Oct 27 01:17:38 2011: firefox-7.0.1-3.fc15 tagged into dist-f15-updates-testing by bodhi Thu Oct 27 01:23:17 2011: firefox-7.0.1-3.fc15 untagged from dist-f15-updates-testing-pending by bodhi Fri Oct 28 16:33:52 2011: firefox-7.0.1-3.fc15 tagged into dist-f15-updates-pending by bodhi [still active] Fri Oct 28 18:44:07 2011: firefox-7.0.1-3.fc15 tagged into dist-f15-updates by ausil [still active] Thu Jan 19 05:15:16 2012: firefox-7.0.1-3.fc15 untagged from dist-f15-updates-testing by oscar $ koji list-tag-history --build kernel-2.6.41.9-1.fc15 Fri Jan 13 19:11:42 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-candidate by jwboyer Fri Jan 13 20:03:34 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-testing-pending by bodhi Fri Jan 13 20:06:53 2012: kernel-2.6.41.9-1.fc15 untagged from dist-f15-updates-testing-pending by bodhi Fri Jan 13 20:06:53 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-testing-pending by bodhi Fri Jan 13 20:07:46 2012: kernel-2.6.41.9-1.fc15 untagged from dist-f15-updates-testing-pending by bodhi Fri Jan 13 20:07:46 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-testing-pending by bodhi Sat Jan 14 00:40:32 2012: kernel-2.6.41.9-1.fc15 untagged from dist-f15-updates-candidate by bodhi Sat Jan 14 00:40:32 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-testing by bodhi Sat Jan 14 00:48:36 2012: kernel-2.6.41.9-1.fc15 untagged from dist-f15-updates-testing-pending by bodhi Sat Jan 14 21:33:47 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates-pending by bodhi [still active] Sun Jan 15 16:19:04 2012: kernel-2.6.41.9-1.fc15 untagged from dist-f15-updates-testing by lmacken Sun Jan 15 16:19:04 2012: kernel-2.6.41.9-1.fc15 tagged into dist-f15-updates by lmacken [still active] $ koji list-tag-history --build kernel-3.1.9-1.fc16 Fri Jan 13 19:42:54 2012: kernel-3.1.9-1.fc16 tagged into f16-updates-candidate by jwboyer Fri Jan 13 21:58:19 2012: kernel-3.1.9-1.fc16 tagged into f16-updates-testing-pending by bodhi Sat Jan 14 00:40:41 2012: kernel-3.1.9-1.fc16 untagged from f16-updates-candidate by bodhi Sat Jan 14 00:40:41 2012: kernel-3.1.9-1.fc16 tagged into f16-updates-testing by bodhi Sat Jan 14 00:48:36 2012: kernel-3.1.9-1.fc16 untagged from f16-updates-testing-pending by bodhi Sun Jan 15 11:30:57 2012: kernel-3.1.9-1.fc16 tagged into f16-updates-pending by bodhi [still active] Sun Jan 15 16:19:21 2012: kernel-3.1.9-1.fc16 untagged from f16-updates-testing by lmacken Sun Jan 15 16:19:21 2012: kernel-3.1.9-1.fc16 tagged into f16-updates by lmacken [still active] $ koji list-tag-history --build mod_revocator-1.0.3-7.fc16 Tue Oct 25 03:07:59 2011: mod_revocator-1.0.3-7.fc16 tagged into f16-updates-candidate by kwright Tue Oct 25 03:13:47 2011: mod_revocator-1.0.3-7.fc16 tagged into f16-updates-testing-pending by bodhi Tue Oct 25 03:33:38 2011: mod_revocator-1.0.3-7.fc16 untagged from f16-updates-candidate by bodhi Tue Oct 25 03:33:38 2011: mod_revocator-1.0.3-7.fc16 tagged into f16-updates-testing by bodhi Tue Oct 25 03:39:10 2011: mod_revocator-1.0.3-7.fc16 untagged from f16-updates-testing-pending by bodhi Fri Oct 28 02:58:22 2011: mod_revocator-1.0.3-7.fc16 untagged from f16-updates-testing by bodhi Wed Nov 2 14:00:32 2011: mod_revocator-1.0.3-7.fc16 tagged into trashcan by oscar Wed Nov 2 18:43:56 2011: mod_revocator-1.0.3-7.fc16 tagged into f16-updates-pending by bodhi [still active] Thu Nov 3 09:25:51 2011: mod_revocator-1.0.3-7.fc16 untagged from trashcan by oscar $ koji list-tag-history --build mozilla-adblockplus-1.3.10-4.fc16 Thu Jan 19 20:44:29 2012: mozilla-adblockplus-1.3.10-4.fc16 tagged into f16-updates-candidate by niveusluna Fri Jan 20 18:34:42 2012: mozilla-adblockplus-1.3.10-4.fc16 tagged into f16-updates-testing-pending by bodhi Fri Jan 20 21:09:24 2012: mozilla-adblockplus-1.3.10-4.fc16 untagged from f16-updates-candidate by bodhi Fri Jan 20 21:09:24 2012: mozilla-adblockplus-1.3.10-4.fc16 tagged into f16-updates-testing by bodhi [still active] Fri Jan 20 21:14:58 2012: mozilla-adblockplus-1.3.10-4.fc16 untagged from f16-updates-testing-pending by bodhi Fri Jan 20 23:43:49 2012: mozilla-adblockplus-1.3.10-4.fc16 tagged into f16-updates-pending by bodhi [still active] Sat Jan 21 04:57:30 2012: mozilla-adblockplus-1.3.10-4.fc16 tagged into f16-updates by ausil [still active]

2 1

[AutoQA] #311: Improve Koji call performance with koji.ClientSession.multiCall
by fedora-badges 03 Feb '12

03 Feb '12

#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

1 4

rats_install test updated for review
by Hongqing Yang 02 Feb '12

02 Feb '12

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_inst… 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

2 14

incorrectly tagged updates
by Kamil Paral 25 Jan '12

25 Jan '12

Hello Luke, some of our tests fail again due to incorrectly tagged updates [1] [2]. Here's the list: airsched-0.1.4-1.fc15 simfqt-0.1.3-1.fc15 airinv-0.1.2-1.fc15 1:kdeaccessibility-4.7.4-1.fc16 1:kdepim-runtime-4.7.4-1.fc16 1:marble-4.7.4-1.fc16 6:kdebase-4.7.4-2.fc16 6:kdegames-4.7.4-1.fc16 6:kdelibs-4.7.4-1.fc16 6:kdemultimedia-4.7.4-2.fc16 6:kdeutils-4.7.4-1.fc16 7:kdeadmin-4.7.4-1.fc16 7:kdegraphics-4.7.4-1.fc16 7:kdenetwork-4.7.4-1.fc16 7:kdepim-4.7.4-1.fc16 7:kdetoys-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-l10n-4.7.4-1.fc16 kde-wallpapers-4.7.4-1.fc16 kdeartwork-4.7.4-1.fc16 kdebase-runtime-4.7.4-2.fc16 kdebase-workspace-4.7.4-5.fc16 kdeedu-4.7.4-1.fc16 kdegraphics-strigi-analyzer-4.7.4-1.fc16 kdegraphics-thumbnailers-4.7.4-1.fc16 kdepimlibs-4.7.4-2.fc16 kdeplasma-addons-4.7.4-1.fc16 kdesdk-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 mod_revocator-1.0.3-9.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 6:kdelibs-4.6.5-8.fc15 firefox-8.0-3.fc15 Can you fix these by hand and ideally also find the bug in Bodhi? Thanks, Kamil [1] https://fedorahosted.org/pipermail/autoqa-results/Week-of-Mon-20120102/5672… [2] https://fedorahosted.org/pipermail/autoqa-results/Week-of-Mon-20120102/5672… [3] https://fedorahosted.org/pipermail/autoqa-results/Week-of-Mon-20120102/5672…

2 2

Rebooting Virtual Host for Production and Staging
by Tim Flink 25 Jan '12

25 Jan '12

Just as a heads up, the host for the production and staging VMs (autoqa01 and autoqa-stg01) needs to be rebooted so I've applied updates to the VMs and will be shutting them down shortly. Once they've been shut down, I expect to be starting them up again shortly. Tim

2 2

[PATCH] util.py: make downloads retry after socket timeout
by Martin Krizek 23 Jan '12

23 Jan '12

Could be also found in urlretry branch. --- lib/autoqa/util.py | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/lib/autoqa/util.py b/lib/autoqa/util.py index 1437976..86b76e5 100644 --- a/lib/autoqa/util.py +++ b/lib/autoqa/util.py @@ -339,7 +339,12 @@ def download(url, dest, overwrite=False): print 'Downloading: %s' % url try: - url_grabber = urlgrabber.grabber.URLGrabber(retry=3) + url_grabber = urlgrabber.grabber.URLGrabber(retry=3,timeout=120) + + # retry on socket timeout + if 12 not in url_grabber.opts.retrycodes: + url_grabber.opts.retrycodes.append(12) + url_grabber.urlgrab(url, dest) except urlgrabber.grabber.URLGrabError, e: print >> sys.stderr, 'Download error: %s' % e -- 1.7.7.5

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel January 2012