autoqa-devel April 2011

autoqa-devel@lists.fedorahosted.org

10 participants
99 discussions

[AutoQA] #301: Reverse execute logic in control.autoqa
by fedora-badges 11 Apr '11

11 Apr '11

#301: Reverse execute logic in control.autoqa -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Finger Food Component: core | Keywords: -------------------------+-------------------------------------------------- The 'execute' variable is True by default and the test must specify execute=False in control.autoqa if it doesn't want to be run. That leads to constructs as: {{{ if event not in ['post-bodhi-update-batch']: execute = False }}} This would be more comprehensible: {{{ # execute = False by default if event in ['post-bodhi-update-batch']: execute = True }}} I.e. we would convert negative logic (saying when it should not run) into positive logic (saying when it should run). Do this change and make corresponding changes in all tests. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/301> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 7

AutoQA 0.4.6 released
by Kamil Paral 11 Apr '11

11 Apr '11

AutoQA 0.4.6 has been released. Congratulation to tflink and jlaska who own 50% of the new release changes each :-) https://fedorahosted.org/autoqa/milestone/0.4.6 Changelog: - Ticket#293 - CmdError: No more mirrors to try (tflink) - autoqa-git-hook: Improved error detection and bad input handling (jlaska)

1 0

[AutoQA] #293: CmdError: No more mirrors to try
by fedora-badges 11 Apr '11

11 Apr '11

#293: CmdError: No more mirrors to try ------------------------+--------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: production | Keywords: ------------------------+--------------------------------------------------- Occasionally (more often recently) some test ends with "CRASHED: CmdError ... returned non-zero exit status" and the cause is Yum Exception "No more mirrors to try". Usually I see this error when my network connection is down. The question is: 1. if this is the case 2. how did we receive the log results back in that case 3. why it is happening Search for CmdError here for examples: https://fedorahosted.org/pipermail/autoqa-results/2011-March/thread.html And a concrete example: https://fedorahosted.org/pipermail/autoqa-results/2011-March/087278.html [[BR]] https://fedorahosted.org/pipermail/autoqa-results/2011-March/096910.html -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/293> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 12

stale tags in koji
by Tim Flink 11 Apr '11

11 Apr '11

All, I happened to be going through the upgradepath results for F15 today and I'm seeing a lot of builds with stale tags (~50 so far and I'm not done). If we re-enable comments before these builds are taken care of, we're going to be adding a lot more comments to old builds again. This is why spot-checking (like I did before) isn't enough, I suppose. Anyhow, I sent an email to lmacken with my initial list and I'm planning to write a script to check for stale tags tomorrow. Tim

3 6

[AutoQA] #218: re-use fedora-qa script for checking PackageReviewGuidelines
by fedora-badges 07 Apr '11

07 Apr '11

#218: re-use fedora-qa script for checking PackageReviewGuidelines --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: Future test cases Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- Aurélien Bompard has written a "fedora-qa" tool, which checks all the MUST items in !PackageReviewGuidelines that are not covered by rpmlint. http://fedoraproject.org/wiki/AurelienBompard#QA There's a high possibility that we could re-use parts of his code for several new AutoQA test cases. Worth investigating. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/218> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[Fwd: Fedora SPEC Review Tool]
by James Laska 07 Apr '11

07 Apr '11

Hey gang, Anything finger-food worthy with this new spec_checks tool? Thanks, James

3 3

AutoQA 0.4.5 coming - please test
by Kamil Paral 07 Apr '11

07 Apr '11

I believe we have AutoQA 0.4.5 ready: https://fedorahosted.org/autoqa/milestone/0.4.5 There are a few hot issues remaining, but I don't think we should wait for them: #293 CmdError: No more mirrors to try - tflink working on this one - can be really difficult - doesn't produce bad results, just sometimes produces no result at all, not blocker #284 depcheck does not produce output for some pending updates - may be related to the above one - doesn't produce bad results, just sometimes produces no result at all, not blocker #289 Missing autotest debug logs - this may take some time to debug and solve So, I want to ask anyone interested to checkout "stable" branch a run a few tests (depcheck and upgradepath are top priorities) and report any problems found. If everything works as expected, we will publish a new release any day now. Thanks.

4 10

[AutoQA] #294: Detect required Fedora releases correctly
by fedora-badges 06 Apr '11

06 Apr '11

#294: Detect required Fedora releases correctly --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: minor | Milestone: 0.5.0 Component: core | Keywords: --------------------+------------------------------------------------------- Currently we use this approach in control.autoqa to require a specific Fedora release for a test run: {{{ # if we want to install the package, we must have this test running on # Fedora release corresponding to the package; thus the autotest label of the # correct distribution must be present (like 'fc13'); let's strip it from the # NVR (last part) if autoqa_args.has_key('nvr'): labels.append(autoqa_args['nvr'].split('.')[-1]) }}} That is incorrect, because the package may look like foo-1.1-1.i686.fc15.1 . We have to use a different way. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/294> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 5

[AutoQA] #302: depcheck should use correct version of yum for packages under test
by fedora-badges 06 Apr '11

06 Apr '11

#302: depcheck should use correct version of yum for packages under test -------------------------+-------------------------------------------------- Reporter: tflink | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: Future tasks Component: tests | Keywords: -------------------------+-------------------------------------------------- == Description == I don't think that this is a problem yet but I figured that I would file a ticket before I forgot. When I was digging through the depcheck and yum code today, it occurred to me that we rely on the test host's yum installation for depcheck and we don't specify the version of fedora to use when scheduling the tests. Since each version of fedora has a different version of yum, this could cause problems in the future if there are yum metadata format changes or other forward/backward-incompatible changes in yum. == Possible Solutions == 1. schedule depcheck jobs to match the fedora version under test * This is the simplest fix 2. Use virtualenvs * While more complicated, this would allow depcheck scheduling on any version of fedora and multiple depcheck jobs on the same host if we ever figure out a way to get around the validity of concurrent jobs. Personally, I'm all for the scheduling change for a fix since I can't really see enough benefit to using virtualenv to justify the cost of implementing it right now. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/302> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[PATCH] Update to 0.4.4-0.2.pre
by James Laska 05 Apr '11

05 Apr '11

--- autoqa.spec | 14 +++++++++++++- 1 files changed, 13 insertions(+), 1 deletions(-) diff --git a/autoqa.spec b/autoqa.spec index 73ae957..ffe22c2 100644 --- a/autoqa.spec +++ b/autoqa.spec @@ -6,7 +6,7 @@ Name: autoqa Summary: Automated quality assurance framework Version: 0.4.4 -Release: 0.1.pre%{?dist} +Release: 0.2.pre%{?dist} Source0: http://fedorahosted.org/autoqa/releases/%{name}-%{version}.tar.gz License: GPLv2+ Group: Applications/Internet @@ -65,6 +65,18 @@ rm -rf $RPM_BUILD_ROOT %changelog +* Tue Mar 08 2011 James Laska <jlaska(a)redhat.com> - 0.4.4-0.2.pre +- upgradepath: run on post-bodhi-update-batch, test all updates, send bodhi + comments (kparal) +- depcheck: enable scheduling for -batch event (jskladan) +- Stop using epoch in NVR variables (kparal, jskladan) +- Replace old bodhi watcher with new koji watcher (jskladan) +- Ticket#269 - update repoinfo.conf for Fedora 15 branch (jlaska) +- Add a setup method to the no-swap-lvm test suite. (clumens) +- Update documentation in testclass template regarding email subject (kparal) +- bodhi_already_commented() does not require user arg anymore (kparal) +- New test - depcheck (wwoods) + * Tue Jan 25 2011 James Laska <jlaska(a)redhat.com> - 0.4.4-0.1.pre - Add BuildRequire: autotest (jlaska) - Copy config files to clients in a better way (jlaska) -- 1.7.4.1

2 14

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel April 2011