autoqa-devel August 2010

autoqa-devel@lists.fedorahosted.org

7 participants
87 discussions

Re: [AutoQA] #41: Automate test case - Basic Functionality / X startup/basic display configuration
by fedora-badges 06 Aug '10

06 Aug '10

#41: Automate test case - Basic Functionality / X startup/basic display configuration ---------------------+------------------------------------------------------ Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Future test cases Component: tests | Version: 1.0 Resolution: | Keywords: ---------------------+------------------------------------------------------ Changes (by kparal): * milestone: => Future test cases -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/41#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 0

[AutoQA] #190: Test idea - ABI compatability check
by fedora-badges 06 Aug '10

06 Aug '10

#190: Test idea - ABI compatability check -------------------------+-------------------------------------------------- Reporter: jlaska | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: tests | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Remi Collet posted a blog article on how to use the [http://ispras.linux- foundation.org/index.php/ABI_compliance_checker ABI compliance checker] to ensure that ABI is maintained during updated releases of a package (this could be used to compare versions changes as well). See the full post at http://blog.famillecollet.com/post/2010/06/20/ABI -:-stability-check -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/190> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

Re: [AutoQA] #31: Test for unowned directories
by fedora-badges 06 Aug '10

06 Aug '10

#31: Test for unowned directories ----------------------+----------------------------------------------------- Reporter: dgregor | Owner: Type: task | Status: new Priority: minor | Milestone: Future test cases Component: tests | Version: 1.0 Resolution: | Keywords: ----------------------+----------------------------------------------------- Changes (by kparal): * milestone: => Future test cases -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/31#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 0

Re: [AutoQA] #59: Add debugrepo check
by fedora-badges 06 Aug '10

06 Aug '10

#59: Add debugrepo check --------------------+------------------------------------------------------- Reporter: scop | Owner: Type: task | Status: new Priority: minor | Milestone: Future test cases Component: tests | Version: Resolution: | Keywords: --------------------+------------------------------------------------------- Changes (by kparal): * milestone: => Future test cases -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/59#comment:1> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 0

Re: [AutoQA] #92: Adapt font tests for autoqa
by fedora-badges 06 Aug '10

06 Aug '10

#92: Adapt font tests for autoqa ---------------------+------------------------------------------------------ Reporter: wwoods | Owner: Type: task | Status: new Priority: minor | Milestone: Future test cases Component: tests | Version: 1.0 Resolution: | Keywords: ---------------------+------------------------------------------------------ Changes (by kparal): * milestone: => Future test cases -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/92#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 0

[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

[PATCH 1/2] add repoinfo.getreleases() and get_bodhi_releases()
by Will Woods 05 Aug '10

05 Aug '10

--- lib/python/repoinfo.py | 6 ++++++ repoinfo.conf | 4 ++++ 2 files changed, 10 insertions(+), 0 deletions(-) diff --git a/lib/python/repoinfo.py b/lib/python/repoinfo.py index 420becc..3a8c1f8 100644 --- a/lib/python/repoinfo.py +++ b/lib/python/repoinfo.py @@ -39,6 +39,12 @@ class RepoinfoConfig(object): return [t.strip() for t in itemlist.split(',')] def getarches(self, name): return self._getlist(name, 'arches') + def getreleases(self): + '''Return the list of known, non-EOL releases.''' + return [r for r in repoinfo.repos() if self.config.get(r,'isactiverelease')] + def get_bodhi_releases(self): + '''Return the list of releases known to Bodhi.''' + return [r.upper() for r in self.getreleases()] def getparents(self, name): '''Given a repo name, give the names of its parent repos e.g.: getparents('f13-updates-testing') -> ['f13','f13-updates]''' diff --git a/repoinfo.conf b/repoinfo.conf index 3241044..d36dd93 100644 --- a/repoinfo.conf +++ b/repoinfo.conf @@ -8,6 +8,7 @@ baseurl = http://download.fedoraproject.org/pub/fedora/linux goldurl = %(baseurl)s/releases/%(path)s/Everything/%(arch)s/os updatesurl = %(baseurl)s/updates/%(path)s/%(arch)s rawhideurl = %(baseurl)s/%(path)s/%(arch)s/os +isactiverelease = # Rawhide [rawhide] @@ -19,6 +20,7 @@ collection_name = devel # Fedora 14 [f14] +isactiverelease = yes path = development/14 url = %(rawhideurl)s collection_name = F-14 @@ -37,6 +39,7 @@ collection_name = F-14 # Fedora 13 [f13] +isactiverelease = yes path = 13 url = %(goldurl)s collection_name = F-13 @@ -55,6 +58,7 @@ collection_name = F-13 # Fedora 12 [f12] +isactiverelease = yes path = 12 url = %(goldurl)s collection_name = F-12 -- 1.7.2

2 3

[PATCH] post-bodhi-update watcher: a few fixes
by Kamil Paral 05 Aug '10

05 Aug '10

These two patches fix some issues with post-bodhi-update watcher, as discussed on IRC. I haven't really studied working with repoinfo.conf-style config files, so please review if it is correct. Thanks. It is tested and it works.

2 5

[PUSHED] post-bodhi-update: fix hook to conform to control.autoqa patchset
by Kamil Paral 04 Aug '10

04 Aug '10

This was an obvious omission of the control.autoqa patchset, I forgot to fix post-bodhi-update hook. I pushed it straightaway. http://git.fedorahosted.org/git/?p=autoqa.git;a=commit;h=4dff3d9761eaafca3e…

1 0

[PATCH] deprecate email opt-in for koji watcher
by Kamil Paral 04 Aug '10

04 Aug '10

I'm not sure about all consequences of this patch. But it seems to me that we don't need collection_name and email opt-in anymore. What do you think, Will?

2 4

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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel August 2010