autoqa-devel November 2010

autoqa-devel@lists.fedorahosted.org

8 participants
85 discussions

[AutoQA] #228: Rewrite post-bodhi-update watch to rely on koji -pending tags
by fedora-badges 25 Jan '11

25 Jan '11

#228: Rewrite post-bodhi-update watch to rely on koji -pending tags ----------------------------+----------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Component: infrastructure | Version: 1.0 Keywords: | ----------------------------+----------------------------------------------- Per discussion from [https://fedorahosted.org/pipermail/autoqa- devel/2010-September/001175.html autoqa-devel meeting], the ''post-bodhi- update'' watcher will eventually need to be replaced by a watcher that monitors koji ''-pending'' tags instead. The current implementation is deemed fragile, and may no longer function properly after bodhi-2.0 upgrade. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/228> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 5

[AutoQA] #242: autotest fails to build against dist-f14
by fedora-badges 20 Jan '11

20 Jan '11

#242: autotest fails to build against dist-f14 -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: blocker | Milestone: Packaging, Review, & Deployment Component: packaging | Keywords: -----------------------+---------------------------------------------------- {{{ DEBUG: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qLW1rH DEBUG: + umask 022 DEBUG: + cd /builddir/build/BUILD DEBUG: + cd autotest-notests-0.12.0 DEBUG: + LANG=C DEBUG: + export LANG DEBUG: + unset DISPLAY DEBUG: + python utils/compile_gwt_clients.py -a DEBUG: /builddir/build/BUILD/autotest- notests-0.12.0/client/common_lib/logging_manager.py:84: UserWarning: This module has not been reviewed for Python 2.7 (r27:82500, Sep 16 2010, 18:02:00) DEBUG: [GCC 4.5.1 20100907 (Red Hat 4.5.1-3)] DEBUG: sys.version) DEBUG: 09:56:22 INFO | Compiling client autotest.TkoClient DEBUG: 09:56:22 DEBUG| Running 'java -Xmx512M -cp "/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/src:/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/bin:/usr/share/gwt/gwt- user.jar:/usr/share/gwt/gwt-dev.jar" -Djava.awt.headless=true com.google.gwt.dev.Compiler -war "/builddir/build/BUILD/autotest- notests-0.12.0/frontend/client/www.new" autotest.TkoClient' DEBUG: 09:56:22 INFO | Error compiling autotest.TkoClient, leaving old client DEBUG: 09:56:22 INFO | Compiling client autotest.EmbeddedTkoClient DEBUG: 09:56:22 DEBUG| Running 'java -Xmx512M -cp "/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/src:/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/bin:/usr/share/gwt/gwt- user.jar:/usr/share/gwt/gwt-dev.jar" -Djava.awt.headless=true com.google.gwt.dev.Compiler -war "/builddir/build/BUILD/autotest- notests-0.12.0/frontend/client/www.new" autotest.EmbeddedTkoClient' DEBUG: 09:56:22 INFO | Error compiling autotest.EmbeddedTkoClient, leaving old client DEBUG: 09:56:22 INFO | Compiling client autotest.AfeClient DEBUG: 09:56:22 DEBUG| Running 'java -Xmx512M -cp "/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/src:/builddir/build/BUILD /autotest-notests-0.12.0/frontend/client/bin:/usr/share/gwt/gwt- user.jar:/usr/share/gwt/gwt-dev.jar" -Djava.awt.headless=true com.google.gwt.dev.Compiler -war "/builddir/build/BUILD/autotest- notests-0.12.0/frontend/client/www.new" autotest.AfeClient' DEBUG: 09:56:23 INFO | Error compiling autotest.AfeClient, leaving old client DEBUG: Error: The following clients failed: autotest.TkoClient DEBUG: autotest.EmbeddedTkoClient DEBUG: autotest.AfeClient DEBUG: RPM build errors: DEBUG: error: Bad exit status from /var/tmp/rpm-tmp.qLW1rH (%build) DEBUG: Bad exit status from /var/tmp/rpm-tmp.qLW1rH (%build) DEBUG: Child returncode was: 1 INFO: EXCEPTION: Command failed. See logs for output. }}} -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/242> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #241: Add support for a staging server
by fedora-badges 10 Jan '11

10 Jan '11

#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Keywords: --------------------+------------------------------------------------------- We want to be able to deploy AutoQA onto a staging server. Mainly it means we must be able to disable or redirect the produced test output. We want to be able to disable or redirect email sending (that includes standard results and also opt-in emails). We want to be able to disable posting Bodhi comments (or logging it somewhere else instead). We want to be able to use a different ResultDB instance. Make sure all the bits are in place and add required functionality if necessary. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/241> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 6

[AutoQA] #205: make depcheck submit karma/comments to bodhi
by fedora-badges 10 Jan '11

10 Jan '11

#205: make depcheck submit karma/comments to bodhi --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan - depcheck Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Modify the depcheck test so that it sends status info - karma, comments, whatever - to bodhi. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/205> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 10

Re: Re: Virtualization support
by Scott M Ferguson 07 Dec '10

07 Dec '10

> Message: 3 > Date: Tue, 9 Nov 2010 08:29:27 -0500 (EST) > From: Kamil Paral <kparal(a)redhat.com> > Subject: Re: Virtualization support > To: AutoQA development <autoqa-devel(a)lists.fedorahosted.org> > Message-ID: > <1532790094.383731289309367710.JavaMail.root(a)zmail03.collab.prod.int.phx2.redhat.com> > > Content-Type: text/plain; charset=utf-8 > > ----- "Scott M Ferguson" <smferguson(a)gmail.com> wrote: > >> Hey all, >> >> Joza was kinda enough to let me have a go at part of the >> virtualization support: enabling 2-way communication between a >> virt-host and virt-guests and I'm starting to dig into it. Per his >> suggestion I'm working on a generic api that can be tuned based on >> the >> needs of the project and I wanted to bring it up to the list. A few >> initial thoughts from Joza regarding communication were: >> >> Host->Guest - this needs to be able to select a certain virt guest >> 1) Is a test actually running? >> 2) Disconnect autotest-enabled eth >> 3) run a command >> >> Guest->Host >> 1) Test finished >> 2) Test crashed >> 3) Test running too long >> 4) Destructive test finished, revert me to 'safe' snapshot >> >> He also noted a management interface on the server might be >> interesting and James noted that it will need to play nice with >> autotest. >> >> I know this is a long-term goal, but I'd love to hear everyone's >> thoughts when time permits. > > Hey Scott, > > it absolutely great that you want to help us with this one. We really > appreciate it. I don't know how many details jskladan provided to you, > but here us some additional information about it: > > https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000642.html > https://fedorahosted.org/autoqa/milestone/Virtualization > > Don't hesitate to ask and consult anything related in here. > > Thanks, > Kamil > Thanks for the additional info. I'll definitely keep the list updated and likely have lots of questions. Best, Scott

1 1

plan for merging clumens branch onto master
by Chris Lumens 02 Dec '10

02 Dec '10

Hey everyone, as you may have noticed I have been working on tests for anaconda's storage code. With jlaska's help, I've got it in shape now where it runs just like I want. It does all the testing inside a VM and then communicates results to the outide world. My existing tests should cover the whole partitioning part of the test matrix, aside from resizing since we can't express that with kickstart. All of the code is on the clumens branch in tests/anaconda_storage/. Eventually, I'd like to move it into tests/anaconda/storage/ instead since we are adding some different anaconda tests on the branch as well. Anyway I would like to get this stuff merged to master soon (after I reorganize though) so it can be running and reporting results. What do I need to do to get this on the plan? - Chris

2 2

[PATCH] return non-zero exit status when job scheduling fails
by Kamil Paral 30 Nov '10

30 Nov '10

All the watchers and also the main autoqa script should return non-zero exit code when job scheduling fails. This patch fixes that. --- autoqa | 8 ++++++-- hooks/post-bodhi-update/watch-bodhi-requests.py | 12 +++++++++--- hooks/post-koji-build/watch-koji-builds.py | 9 ++++++++- hooks/post-repo-update/watch-repos.py | 7 ++++++- hooks/post-tree-compose/watch-composes.py | 7 ++++++- 5 files changed, 35 insertions(+), 8 deletions(-) diff --git a/autoqa b/autoqa index a4261ec..cb2d737 100755 --- a/autoqa +++ b/autoqa @@ -281,13 +281,13 @@ if opts.listtests: sys.exit(0) # We're ready to run/queue tests now. +exit_status = 0 for test in testlist: try: template = os.path.join(conf['testdir'], test, 'control') control = prep_controlfile(template, test_vars[test]['autoqa_args']) except IOError, e: - print "WARNING: could not process control file for %s: %s" % (test, - str(e)) + print "WARNING: could not process control file for %s: %s" % (test, str(e)) continue for arch in test_vars[test]['archs']: @@ -303,8 +303,12 @@ for test in testlist: labels=test_vars[test]['labels']) if retval != 0: print "ERROR: failed to schedule job %s" % testname + exit_status = 10 if opts.keep_control_file or opts.dryrun: print "keeping %s at user request" % control else: os.remove(control) + +sys.exit(exit_status) + diff --git a/hooks/post-bodhi-update/watch-bodhi-requests.py b/hooks/post-bodhi-update/watch-bodhi-requests.py index 593ba9d..1c5b3f4 100755 --- a/hooks/post-bodhi-update/watch-bodhi-requests.py +++ b/hooks/post-bodhi-update/watch-bodhi-requests.py @@ -53,7 +53,7 @@ import fedora.client import optparse import time -import os +import os, sys import subprocess from autoqa.repoinfo import repoinfo from autoqa.bodhi_utils import bodhitime, parse_bodhitime, bodhi_list @@ -247,15 +247,21 @@ when new requests are filed in bodhi') for u in updates['testing']: add_update_to_arglist(u, '-updates-testing') + exit_status = 0 for a in arglist: harnesscall = ['autoqa', 'post-bodhi-update'] + a if opts.dryrun: print " ".join(harnesscall) else: - subprocess.call(harnesscall) + retval = subprocess.call(harnesscall) + if retval != 0: + exit_status = 10 + + sys.exit(exit_status) if __name__ == '__main__': try: main() except KeyboardInterrupt: - print + print 'Exiting on keyboard interrupt...' + sys.exit(1) diff --git a/hooks/post-koji-build/watch-koji-builds.py b/hooks/post-koji-build/watch-koji-builds.py index 56a093f..4cc2d7f 100755 --- a/hooks/post-koji-build/watch-koji-builds.py +++ b/hooks/post-koji-build/watch-koji-builds.py @@ -129,6 +129,7 @@ tags for new builds and kick off tests when new builds/packages are found.') session = koji_utils.SimpleKojiClientSession(kojiserver, kojiopts) untagged_builds = [] tagged_builds = [] + exit_status = 0 try: session.ensure_connection() (tagged_builds, untagged_builds) = new_builds_since(session, @@ -156,6 +157,12 @@ tags for new builds and kick off tests when new builds/packages are found.') if opts.dryrun: print " ".join(harnesscall) continue - subprocess.call(harnesscall) + retval = subprocess.call(harnesscall) + if retval != 0: + exit_status = 10 + except KeyboardInterrupt: print "Exiting on keyboard interrupt." + sys.exit(1) + + sys.exit(exit_status) diff --git a/hooks/post-repo-update/watch-repos.py b/hooks/post-repo-update/watch-repos.py index d5e6d8f..0d3ce8f 100755 --- a/hooks/post-repo-update/watch-repos.py +++ b/hooks/post-repo-update/watch-repos.py @@ -76,6 +76,7 @@ for reponame in repoinfo.repos(): testable[reponame].append(arch) # Cycle through the testable repos and update the cache and launch harness +exit_status = 0 for reponame, arches in sorted(testable.items()): for arch in arches: repo = repodict[reponame] @@ -102,4 +103,8 @@ for reponame, arches in sorted(testable.items()): urlgrabber.urlgrab(urlpath, filename=output) # Call the autoqa tool for the post-repo-update harness - subprocess.call(harnesscall) + retval = subprocess.call(harnesscall) + if retval != 0: + exit_status = 10 + +sys.exit(exit_status) diff --git a/hooks/post-tree-compose/watch-composes.py b/hooks/post-tree-compose/watch-composes.py index 8966fc7..64a7fd3 100755 --- a/hooks/post-tree-compose/watch-composes.py +++ b/hooks/post-tree-compose/watch-composes.py @@ -81,6 +81,7 @@ for reponame in watchcomposes: testable[reponame].append(arch) # Cycle through the testable repos and update the cache and launch harness +exit_status = 0 for reponame, arches in sorted(testable.items()): for arch in arches: repo = repodict[reponame] @@ -102,4 +103,8 @@ for reponame, arches in sorted(testable.items()): urlgrabber.urlgrab(urlpath, filename=output) # launch tests - subprocess.call(harnesscall) + retval = subprocess.call(harnesscall) + if retval != 0: + exit_status = 10 + +sys.exit(exit_status) -- 1.7.3.2

2 1

Disable depcheck and anaconda tests
by James Laska 30 Nov '10

30 Nov '10

A small patch I'd like to apply to 'master' to cleanup output generated while scheduling jobs. * 0001-Disable-execution-of-depcheck-and-anaconda-until-the.patch Disable 'depcheck' and 'anaconda' tests. I think we ideally wouldn't want these tests in the git 'master' repo until they are complete. Either way, I'd like to disable execution of these tests since it fills up the logs with errors like the following. > Error: Can't evaluate test 'depcheck': [Errno 2] No such file or directory: > +'/usr/share/autotest/client/site_tests/depcheck/control.autoqa' > Error: Can't evaluate test 'anaconda': [Errno 2] No such file or directory: > +'/usr/share/autotest/client/site_tests/anaconda/control.autoqa' I'd prefer updating the method used by the 'autoqa' script to find applicable tests. My initial thought would be to adjust 'autoqa' so it finds all sub-directories under 'tests/' that contain a control (or control.autoqa) file. The current method only allows for one-level deep of tests. That will need to change at some point, but for now it's more invasive that I'd like. If no thoughts concerns, I'll push this into master later this week. Thanks, James

2 2

depcheck possibly not working
by Josef Skladanka 29 Nov '10

29 Nov '10

Hi gang, I've been playing around with depcheck, lately (the version from the depcheck branch in git), and no matter which packages I try to put on the depcheck's input, both y.tsInfo.pkgSack and y.tsInfo.localSack are always empty. Am I doing something wrong, or is this simply not working? Note: I'm testing with x86_64 packages on x86_64 machine, no multilib packages Joza

2 1

[AutoQA] #201: Add mash support to depcheck
by fedora-badges 29 Nov '10

29 Nov '10

#201: Add mash support to depcheck -----------------------+---------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Package Update Acceptance Test Plan - depcheck Component: docs/wiki | Version: 1.0 Keywords: | -----------------------+---------------------------------------------------- To properly handle possible multilib problems (e.g. the [https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000703.html nss-softokn problem] in June and the recent gfortran problem) we need to run mash on the set of proposed packages, to generate a proper multilibified repo to test against. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/201> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 14

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel November 2010