autoqa-devel April 2010

autoqa-devel@lists.fedorahosted.org

7 participants
65 discussions

[AutoQA] #118: New test proposal: Python debugability
by fedora-badges 06 Aug '10

06 Aug '10

#118: New test proposal: Python debugability --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: minor | Milestone: Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- From Adam Williamson: I've cut some of the context, but basically David wants to write a test case for checking whether Python debugging is possible as intended, and I asked exactly how he wanted it to be used. {{{ On Tue, 2010-01-26 at 15:30 -0500, David Malcolm wrote: > > > Can I request a test case to cover debuggability of the Python > runtime > > > please (both in Fedora and in RHEL). > > > > > > This is in relation to: > > > https://bugzilla.redhat.com/show_bug.cgi?id=556975 > > > https://bugzilla.redhat.com/show_bug.cgi?id=558977 > > > https://bugzilla.redhat.com/show_bug.cgi?id=557772 > > > > > > as there seem to be gcc and gdb issues, which are conspiring to > make > > > python impossible to debug. > > > > > > > > > The requirement is: within "gdb python", I must be able to select > a > > > PyEval_EvalFrameEx frame, and have the following work: > > > (gdb) print co > > > (gdb) print f > > > > > > rather that have <variable optimized out> > > > > > > so that I can do this: > > > (gdb) print (char*)(((PyStringObject*)co->co_name)->ob_sval) > > > to get the function name > > > > > > (gdb) print (char*)(((PyStringObject*)co->co_filename)->ob_sval) > > > to get the source filename > > > > > > and > > > > > > (gdb) print f->f_lineno > > > to get the approximate source line number. > > > > > > If the above isn't working, it becomes extremely hard to > meaningfully > > > debug any issues that arise inside Python. > This is probably scriptable, and a good candidate for AutoQA and foe > RHTS. > }}} -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/118> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #107: writing a python test (modeled similarly to install.py)
by fedora-badges 23 Jul '10

23 Jul '10

#107: writing a python test (modeled similarly to install.py) -------------------+-------------------------------------------------------- Reporter: liam | Owner: Type: task | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: | -------------------+-------------------------------------------------------- write a python test (modeled similarly to install.py) that takes as input: * a URL to a kickstart file (URL can be local (e.g. file://) or remote (e.g. http://, ftp://, nfs:// ...) ... but start with easy case first. * a URL for the install media (again, keep this simple for now and assume file:///var/lib/libvirt/images/Fedora-12-x86_64-DVD.iso) * a URL to a configuration file that describes the environment - again, perhaps optional for now. But eventually we'll need something that tells the test to create a guest with 4 NICs vs 1 NIC, 3 SCSI drives etc... Don't worry about being fancy at first ... just take the defaults. This is just where I might see it headed in 6+ months. Copy from the kvm autotest project if you like. At beginning, we focus on the basics and something that gets things far enough along so we can review, adjust and repeat. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/107> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 10

[AutoQA] #115: Update post-tree-compose to recognize new stage2 URL
by fedora-badges 21 Jul '10

21 Jul '10

#115: Update post-tree-compose to recognize new stage2 URL -------------------------+-------------------------------------------------- Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: major | Milestone: Automate installation test plan Component: watchers | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- During Fedora 13, release engineering will provide schedule drops of rawhide for automated testing against rats_install. The provided data will include a compose tree (without packages). For proper automated testing of these images, post-tree-compose will need to monitor a new URL for testing (likely candidate is http://alt.fedoraproject.org/pub/alt/stage/rawhide-testing) In addition, rats_install will need to support installing with stage2 and the package repo in different locations. That will be tracked in another ticket. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/115> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #129: create auto install test script which maps 1x1 to the install method.
by fedora-badges 21 Jul '10

21 Jul '10

#129: create auto install test script which maps 1x1 to the install method. -------------------+-------------------------------------------------------- Reporter: liam | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | -------------------+-------------------------------------------------------- Each install method should have an install test script, For example: * Single ISO install - dvd_install.py * Multi ISO install - cd_install.py * Hard Drive ISO install - hdiso_install.py * NFS install - nfs_install.py * NFS ISO install - nfsiso_install.py * HTTP/FTP install - url_install.py <-- similar to rats_install.py now we need to create these scripts, but each of the script should share code as much as possible. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/129> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 5

[AutoQA] #136: ResultsDB: Study MediaWiki RPC mechanism
by fedora-badges 28 Jun '10

28 Jun '10

#136: ResultsDB: Study MediaWiki RPC mechanism ----------------------------+----------------------------------------------- Reporter: jskladan | Owner: wwoods Type: task | Status: new Priority: major | Milestone: Resultdb Component: infrastructure | Version: 1.0 Keywords: | ----------------------------+----------------------------------------------- We want to store metadata about tests on our wiki. To grab the information back, we'll need a way to 'query' wiki for certain page/sub-page. Investigate on the MediaWiki RPC mechanism and propose a way to use it. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/136> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #109: post-bodhi-update watcher
by fedora-badges 25 Jun '10

25 Jun '10

#109: post-bodhi-update watcher ----------------------+----------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: autoqa depcheck Component: watchers | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- the post-bodhi-update hook (see ticket #87) will require a post-bodhi- update watcher. This should use the bodhi API to get info about newly- created/changed updates and fire tests. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/109> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 8

[AutoQA] #126: pst: Create script for Package Sanity Testing
by fedora-badges 09 Jun '10

09 Jun '10

#126: pst: Create script for Package Sanity Testing -----------------------+---------------------------------------------------- Reporter: kparal | Owner: psss Type: task | Status: new Priority: major | Milestone: Package Sanity Tests Component: docs/wiki | Version: 1.0 Keywords: pst | -----------------------+---------------------------------------------------- Create script that will perform actual package sanity testing. It should accept some command-line options denoting which packages to test and return a result whether sanity tests passed or failed, together with more detailed output. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/126> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

No more reboots ...
by James Laska 03 Jun '10

03 Jun '10

Greetings, Just a heads up, as you know we have a lot more tests running now in our internal autoqa instance. Anyone watching autoqa-results can see the activity. Our 3 test clients were having a hard time keeping up, especially since one system seems to no longer grab a DHCP IP upon reboot. As a temporary measure, I've updated the /usr/bin/autoqa script on the server to not reboot the test systems before or after a test is run on the client. This allowed 3 systems to work down the backlog of over 200 jobs in one evening. The patch is attached, I'm not ready to send this out for review yet. However, I did want to let you know in case you observe any side-effects from no longer rebooting after every test. Thanks, James

1 1

[AutoQA] #130: ResultsDB: getting autotest test-ID on the client
by fedora-badges 24 May '10

24 May '10

#130: ResultsDB: getting autotest test-ID on the client ----------------------+----------------------------------------------------- Reporter: jskladan | Owner: jskladan Type: task | Status: new Priority: major | Milestone: Resultdb Component: tests | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- According to the information from lmr(a)redhat.com <https://fedorahosted.org/pipermail/autoqa-devel/2010-March/000326.html> it should be possible to get the test ID from some variable, while creating the control file. Install testing autotest-autoqa environment and give it a try. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/130> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 5

[AutoQA] #106: create disk images for tests requiring pre-existing disk data
by fedora-badges 19 May '10

19 May '10

#106: create disk images for tests requiring pre-existing disk data --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Some installation tests require existing disks with some data - either an old version of Fedora to upgrade, or certain disk partitions to be reused/replaced. For example: * https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_New_Bootloader * https://fedoraproject.org/wiki/QA:Testcase_Preupgrade * https://fedoraproject.org/wiki/QA/TestCases/PartitioningPreExistingLvm2Lvm2 etc. We should either have a library of methods for creating these disks, or keep stock disk images for this purpose. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/106> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel April 2010