QA/Meetings/20091026

= Attendees =

People present (lines said)


 * jlaska (160)
 * wwoods (58)
 * adamw (46)
 * Oxf13 (35)
 * Viking-Ice (24)
 * kparal (17)
 * jwb (7)
 * jeff_hann (4)
 * mether (3)
 * zodbot (3)
 * buggbot (2)
 * Jeff_S (2)
 * skvidal (1)

Regrets:
 * User:Liam
 * User:rhe

= Agenda =


 * Proposed meeting agenda
 * meetbot summary

Previous meeting follow-up
See https://fedoraproject.org/wiki/QA/Meetings/20091019#Action_items


 * jlaska to rename other debug pages (see https://fedoraproject.org/wiki/Category:Debugging) to be consistent with "How to debug problems". Update back-links also

I believe this task is complete. See Category:Debugging for feedback. I've also organized the pages by the component name.

Remaining Question - What do folks want to do with ... KernelBugTriage? Should this change to How to debug kernel problems

Viking_Ice locale test suggestion
Background - https://www.redhat.com/archives/fedora-test-list/2009-October/msg00503.html

Viking-Ice posted a sample script to demonstrate what an automated test should do (see http://pastie.org/671497). Some discussion followed on where best to implement this additional automated test in AutoQA. The group felt that adding the test to Israwhidebroken.com_Proposal was not appropriate. Jlaska felt that this test would be best suited for the QA:Fedora_12_Install_Test_Plan, is it currently is light on i18n verification. Viking-Ice took an action item to create a test case and propose adding it to the test plan. Once added, that test can be included in upcoming automation efforts User:Liam and User:Rhe are investigating.

Milos Jakubicek suggestion on FTBFS bugs
Background - Milos Jakubicek suggested a day/project to work on filing FTBFS(fails-to-build-from-scratch) bugs for all remaining packages that failed to build in F12 mass rebuild (see http://mjakubicek.fedorapeople.org/need-rebuild.html). Some discussion followed on what a QA effort around this might look like. F13 indicated he would have no problems tagging FTBFS rebuilds for F12. Mether provided a link to an existing effort (see FTBFS).

Unfortunately, Milos was not available during the meeting. Adamw took an action item to follow-up with Milos for next weeks meeting (or on fedora-test-list).

Marcela Maslanova test day proposal
Marcela Maslanova sent a test day proposal for including all tests in a package (see http://jvcelak.fedorapeople.org/testday-091022/testday-pm-0.6-1.fc12.src.rpm). Marcela was not present for the meeting, and Jlaska indicated further power management test day feedback was expected from Phil Knirsch soon. Jlaska wanted to highlight that this was the first test day that included a test day rpm which provided scripts to automate test cases and test results collection.

Some outstanding questions for the group:
 * 1) Is there anything we need to be thinking or doing to support this type of work in the future?
 * 2) Where should the test scripts used to in test day packages live?

AutoQA Updates from wwoods and kparal
autoqa-devel list now active Wwoods reminded the group that the autoqa development mailing list for patch review, autoqa progress and test development. Join the autoqa-devel list and contribute today!.

RpmGuard update Kparal directed the group to a blog post detailing his current status on the rpmguard effort. Kparal received some feedback from the post, including:
 * skvidal directed kparal towards a potentially useful script -- http://skvidal.fedorapeople.org/misc/mungingdiff.py
 * alexey torkhov suggested leveraging (see https://fedorahosted.org/autoqa/ticket/75 for tracking)

The next task for Kparal is to investigate the koji-build watcher wwoods is working on and integrate rpmguard into autoqa to have it up and running.

Post-koji-build watcher Wwoods provided a brief update on the post-koji-build which picks up every new build in a set of koji tags specified by autoqa. Some discussion followed on between kparal and wwoods on how to pass data between the tests and the watcher script. Wwoods indicated his current post-koji-build watcher would be landing in autoqa.git soon.

AutoQA library Wwoods indicated a library would also be landing in git soon that takes a package NVR and a koji tag, and returns the previous released versions of that package. Wwoods also noted a plan to create a general purpose autoqa library for use by all tests with helpers for koji interaction and virt guest creation.

Critical Path Package List Due to recent questions around the current critical path package list, wwoods reminded the group about the script http://wwoods.fedorapeople.org/files/critical-path/critpath.py. This script will solve the critical path package set and write output to. Jwb notified the group that he would be incorporating this script into the rawhide compose process. Future rawhide composes will include a critpath.txt file (e.g. http://kojipkgs.fedoraproject.org/mash/rawhide-20091027/logs/critpath.txt).

FUDCon Attendees
F13 asked who was planning to attend FUDCon. Since wwoods was planning for an AutoQA talk on how maintainers could add tests into PkgCVS, F13 would focus on the messagebus talk.

= Upcoming QA events =


 * 2009-10-29 - i18n Test Day - https://fedoraproject.org/wiki/Test_Day:2009-10-29


 * 2009-10-30 - Blocker Bug Day (F12Blocker) #2

= Action items =


 * adamw will ask Milos to follow-up at next week's meeting or on the list on the FTBFS topic
 * Viking-Ice investigating creating a test case for bug#530452 ... and adding to F12 install matrix
 * wwoods to add roadmap/tickets for reworking shared autoqa code (watchers, test helper methods, etc) into a proper library

= IRC Transcript =

Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at mg.pov.lt!