autoqa-devel January 2010

autoqa-devel@lists.fedorahosted.org

5 participants
50 discussions

[AutoQA] #101: install testing: allow different locations for storing the kickstart file
by fedora-badges 29 Mar '10

29 Mar '10

#101: install testing: allow different locations for storing the kickstart file --------------------+------------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- current virguest.py passes the kickstart into the guest as part of the initrd; some of the cases in the installation test plan use other methods to pass the kickstart. see: * https://fedoraproject.org/wiki/QA/TestCases/KickstartKsFilePathKsCfg * https://fedoraproject.org/wiki/QA/TestCases/KickstartKsHdDevicePathKsCfg * https://fedoraproject.org/wiki/QA/TestCases/KickstartKsHttpServerKsCfg * https://fedoraproject.org/wiki/QA/TestCases/KickstartKsNfsServerPathKsCfg virtguest.py (or some other test/setup code) should be able to set up these environments and perform these test cases. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/101> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

DVD auto install test script
by Li Ming 03 Feb '10

03 Feb '10

Hi, I write a very simple DVD auto install test script by referring Will Woods's install script.Many thanks for Will.:) This is my first Python script,it is definitely not good. I will take this script as a starting-point,hope can write some high-qualified scripts in the future. This script only supports DVD + kickstart install. If you want to try it,please modify the attached ks.cfg to specify install source first. this kickstart file can be accessed by http or ftp. Before run it, you need to install virtualization,python-virtinst... Run the script like this: mount -o loop DVDImage.iso /InstallTree ./dvd_install.py -k http://server/ks.cfg -a i386 -d /InstallTree |tee test.log I did not put it to git because some account issues. I will upload later. See the attachments. Thanks Liam

2 7

Re: autoinstall script
by Kamil Paral 29 Jan '10

29 Jan '10

----- "Li Ming" <lili(a)redhat.com> wrote: > > I put a public SSH key to my accounts today, but get this error: > [liam@localhost autoqa]$ git push > ssh://liam@git.fedorahosted.org/autoqa.git master > Enter passphrase for key '/home/liam/.ssh/id_rsa': > fatal: protocol error: bad line length character I don't know if the URL is correct. Looking at the FAQ: https://fedorahosted.org/web/faq and to my .git/config the URL should be: ssh://git.fedorahosted.org/git/autoqa.git What about $ ssh liam(a)fedorapeople.org does it work? I believe it should use the same mechanism: http://fedoraproject.org/wiki/Infrastructure/fedorapeople.org > > Thanks > Liam > > _______________________________________________ > autoqa-devel mailing list > autoqa-devel(a)lists.fedorahosted.org > https://fedorahosted.org/mailman/listinfo/autoqa-devel

2 2

Re: autoinstall script
by James Laska 29 Jan '10

29 Jan '10

On Tue, 2010-01-26 at 16:17 +0800, Li Ming wrote: > I use git push to summit my script,but I have no permission to > access the server, do you know who I can get help from? Will woods or > someone else? Responding to the list ... Will or Kamil, do you have a preference or a new committer hazing ritual? Liam has an early working copy of a new install test. If I understand, he'd like to create a branch and begin pushing changes to that branch. Thanks, James

3 5

[AutoQA] #117: Support boot and install.img located in different location
by fedora-badges 28 Jan '10

28 Jan '10

#117: Support boot and install.img located in different location -------------------------+-------------------------------------------------- Reporter: jlaska | Owner: jlaska Type: enhancement | Status: new Priority: major | Milestone: israwhidebroken.com Component: tests | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Rawhide boot and install images are being built and provided for testing in a different location. These images do not contain packages or repodata. For example, http://alt.fedoraproject.org/pub/alt/stage /rawhide-testing/ contains the boot and install images. However, http://download.fedoraproject.org/pub/fedora/linux/development/ is the typical location for packages and repodata. Rats_install must support downloading boot and install images from the rawhide-testing location, but direct anaconda to install packages from the normal rawhide repo. A [https://fedorahosted.org/pipermail/autoqa- devel/2010-January/000164.html patch] has been sent to the list for review. This ticket will be closed after review and changes have been committed. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/117> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #116: koji_watcher: Pass ENVR instead of NVR
by fedora-badges 28 Jan '10

28 Jan '10

#116: koji_watcher: Pass ENVR instead of NVR ---------------------+------------------------------------------------------ Reporter: kparal | Owner: kparal Type: defect | Status: new Priority: major | Milestone: Component: harness | Version: 1.0 Keywords: | ---------------------+------------------------------------------------------ I have found a problem with current koji_watcher implementation. It passes package NVR to its tests. But if I want to limit max EVR in rpmguard test using koji_utils.list_previous_release(), I have no way to find out the current epoch of the received package. Which causes limitation to work incorrectly. Therefore I think the watcher should be changed to provide its tests with the whole ENVR in format '1:pidgin-2.5-1.fc12' or 'zip-0.4-2.fc12' (assuming epoch 0). -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/116> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 4

Rename directory lib/python -> lib/autoqa
by James Laska 28 Jan '10

28 Jan '10

Hey folks, I've found that while testing locally, it is beneficial to have the 'lib/python' directory renamed to 'lib/autoqa' so that scripts can pull in any needed imports. For example ... # PYTHONPATH="../../lib" install.py -a x86_64 http://download.fedoraproject.org/pub/fedora/linux/development/x86_64/os Any objections or alternatives? Thanks, James

2 1

rats_install improvements
by James Laska 27 Jan '10

27 Jan '10

Greetings, I've incorporated the earlier patch feedback on install.py and adjusted it slightly to accomodate how images are landing for RATS drops now. These compose trees contain only boot and install images, and no packages or repodata. I've modified rats.py, rats_install.py and install.py to accomodate installing using the images and packages in different locations. I've tested locally and it works well. This addresses ticket#115. Also included in the patch is install.py support for adding boot arguments (e.g. updates=http://.../updates.img) as well as support for accepting this information from the control file in rats_install.py. This address ticket#103. The next step will be adjusting post-tree-compose to watch this additional RATS drop location. But for now, I'm comfortable manually scheduling these tests to work out the kinks. Please let me know if there are any corrections or suggestions. Thanks, James

1 1

Re: rpmguard: comparing identical packages
by Kamil Paral 27 Jan '10

27 Jan '10

----- "Kamil Paral" <kparal(a)redhat.com> wrote: > As I have mentioned, it is currently possible for a package to "fly > under our radar" by simply moving to official repositories (stable, > updates, updates-testing) too soon. It caused by our current strategy > to compare the package against its most recent version in official > repositories. > > > Solution #2: Re-implement "search for latest" strategy > I have been playing with koji command and it seems to be able > to list all the history of builds with particular tag, not just > the latest build. You can try it yourself: > $ koji list-tag-history --package=PackageKit > $ koji list-tagged dist-f12-updates PackageKit > Therefore we can re-implement/add a new method to our library > that would not just provide the latest build of a package, but > all of them from the history. Then we would pick the one that > suits us most. The API clearly offers this capabilities. > > > There is also one question that is directly connected to this topic. > Which tags do we want to search through when looking for previous > builds? > c) Or the other way round, would it be better to search through only > stable and -updates (skip -updates-testing)? > When more builds are in testing repo, the differences would be > displayed always against the latest build in stable repos (stable or > -updates). > As mentioned in ticket #114 [1], I have implemented solution #2c). Only publicly available repos and searched through now bu default (can be changed) and searching for most recent package should work now correctly, you can specify maximum allowed EVR (exclusive). No more fare dodgers! :) [1] https://fedorahosted.org/autoqa/ticket/114

1 0

[AutoQA] #114: koji_utils: list latest release fix
by fedora-badges 27 Jan '10

27 Jan '10

#114: koji_utils: list latest release fix ---------------------+------------------------------------------------------ Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Component: harness | Version: 1.0 Keywords: | ---------------------+------------------------------------------------------ As discussed on [https://fedorahosted.org/pipermail/autoqa- devel/2010-January/000143.html autoqa-devel], the list_previous_releases() method should be modified to support setting an optional supremum, so then it just returns releases with NVR lesser then specified supremum. Also an option should exist to allow us to look only in the "publicly available" parent repositories (stable and -updates, skip -updates-testing and -updates-candidate), since we need that for our tests. Alternatively, another method with similar name can be created. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/114> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel January 2010