autoqa-devel August 2011

autoqa-devel@lists.fedorahosted.org

8 participants
75 discussions

A depcheck that got away ...
by James Laska 05 Aug '11

05 Aug '11

Greetings gang, While testing some TC1 installations this morning, I came across a dependency problem that depcheck didn't hit. Thought this might be an interesting case-study. https://admin.fedoraproject.org/updates/libtevent-0.9.13-1.fc16,libldb-1.1.… I'm not entirely sure why depcheck passed, but testing highlighted the following dependency problems: sssd-1.6.0-2.fc16.x86_64 requires libtevent.so.0(TEVENT_0.9.9)(64bit) sssd-1.6.0-2.fc16.x86_64 requires libldb = 1.1.0 The build was updated to include a version of libtevent and libldb to resolve the dependency problem above. Looking through the logs it seems to be searching for deps to satisfy the issues above, but I'm not able to find where it finds them. Thanks, James

2 2

autoqa-0.6.0 released
by James Laska 04 Aug '11

04 Aug '11

Greetings gang, I finished building and deploying autoqa-0.6.0 to production a short while ago. I suspect a wider announcement might be more appropriate, but for now I wanted to let folks know in case any issues surface. Congratulations autoqa team on another release!!! https://fedorahosted.org/autoqa/wiki/Planning060series Thanks, James

1 0

[AutoQA] #330: upgradepath: improve behavior when pushing update to multiple releases
by fedora-badges 04 Aug '11

04 Aug '11

#330: upgradepath: improve behavior when pushing update to multiple releases -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.5.0 Component: tests | Keywords: -------------------------+-------------------------------------------------- This ticket stems from my talk to mcepl and our following discussion: https://fedorahosted.org/pipermail/autoqa-devel/2011-May/002215.html Package maintainers usually push fixes to many Fedora releases at once. Upgradepath usually fails for all but the highest one. We should improve the output. 1. If upgradepath passes, no changes. 2. If upgradepath fails, check update-pending repos for the failed sections and determine whether the same proposed update is available there. If it is, check upgradepath again and determine whether test would pass if all those proposed updates for all releases were pushed at the same time. Inform the user about it. 3. If the condition in 2) is valid, change FAIL result to NEEDS_INSPECTION. I'll gladly take this ticket when I finish my current work. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/330> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 14

0.6 release readiness
by Kamil Paral 04 Aug '11

04 Aug '11

Hello, we have finished working on some important tickets. I want to discuss the readiness to release AutoQA 0.6.0. See the current tickets: https://fedorahosted.org/autoqa/milestone/0.6.0 Please note that ticket #330, albeit not yet closed, is also finished. I just want to amend the documentation only closely before the release. Important finished tickets that I'd like to see in production soon: * Depcheck - prefilter the list of packages passed to yum instance's rpmdb https://fedorahosted.org/autoqa/ticket/349 * upgradepath: improve behavior when pushing update to multiple releases https://fedorahosted.org/autoqa/ticket/330 Almost finished tickets: * Custom 404 page for autoqa.fp.o https://fedorahosted.org/autoqa/ticket/354 The rest of the tickets will probably take some more time and are not ready yet. I think that #354 is easy enough to be finished in a day. I propose waiting for that one and then releasing 0.6.0. That means that 0.6.0 would be released some day this week. The rest of the tickets would move to 0.7 (or more precisely - we'll discuss that at 0.7 planning stage). Comments?

4 7

stray pending builds in Bodhi
by Kamil Paral 04 Aug '11

04 Aug '11

Hello Luke, again we find quite a lot incorrectly tagged builds in Bodhi (still in pending, but same or newer version is already available in stable repos). Can you please find the bug? Stray builds I found in the last 10 minutes: ibus-1.3.99.20110419-2.fc15 in dist-f15-updates-pending icedtea-web-1.0.4-1.fc15 in dist-f15-updates-pending wordpress-3.1.3-3.fc15 in dist-f15-updates-pending wordpress-3.1.3-3.fc14 in dist-f14-updates-pending Thank you, Kamil

1 0

[AutoQA] #348: anaconda upgrade test
by fedora-badges 04 Aug '11

04 Aug '11

#348: anaconda upgrade test ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: core | Keywords: ----------------------+----------------------------------------------------- To implement test case: https://fedoraproject.org/wiki/QA:Testcase_Anaconda_Upgrade_New_Bootloader . we have already implemented Fedora installation automation from DVD, next step we will upgrade the previous release. "virsh' will be used to operate on the guest. [[BR]] The tasks include:[[BR]] * define upgrade steps [[BR]] * install previous release [[BR]] * modify guest xml to boot from new release[[BR]] * upgrade -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/348> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

F16 test clients available
by James Laska 03 Aug '11

03 Aug '11

Greetings folks, Just a quick heads up, I just added two new virt test clients to our production instance. With Fedora 16 branched, these new F16 clients should help handle some test load. Installing these systems required significant workarounds. While I expect things are working properly, let me know if you're seeing any strange results from these systems. $ atest host list -b fc16 Host Status Locked Platform Labels 10.5.124.163 Ready False i386 fc16, virt 10.5.124.164 Ready False x86_64 fc16, virt Thanks, James

1 0

[AutoQA] #354: Custom 404 page for autoqa.fp.o
by fedora-badges 03 Aug '11

03 Aug '11

#354: Custom 404 page for autoqa.fp.o ----------------------+----------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: minor | Milestone: 0.6.0 Component: autotest | Keywords: ----------------------+----------------------------------------------------- Quoting tflink: For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o? Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains: - Explanation of log retention policy - Relevant AutoQA or FedoraQA links It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :) https://fedorahosted.org/pipermail/autoqa-devel/2011-July/002546.html -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/354> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 11

[AutoQA] #102: post-iso-build hook
by fedora-badges 03 Aug '11

03 Aug '11

#102: post-iso-build hook ----------------------+----------------------------------------------------- Reporter: wwoods | Owner: Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: watchers | Version: 1.0 Keywords: | ----------------------+----------------------------------------------------- We need one (or more) standard locations where new iso images get posted for testing, and a watcher that can monitor for new iso images and launch appropriate installation/sanity tests. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/102> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #369: use watcher.py to download iso images to local nfs server
by fedora-badges 02 Aug '11

02 Aug '11

#369: use watcher.py to download iso images to local nfs server ----------------------+----------------------------------------------------- Reporter: hongqing | Owner: hongqing Type: task | Status: new Priority: major | Milestone: Automate installation test plan Component: core | Keywords: ----------------------+----------------------------------------------------- since the different time zone, the Fedora releases are usually published at night, and the download speed is limited in China office, it usually cost the more than half a day to download the images. luckily, watcher.py can watch the iso images on dl.fp.o, so it can be used to download the remote images to local nfs server. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/369> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel August 2011