Full irc transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20090831
= Attendees =
People Present (lines said):
* James Laska - jlaska (169)
* Will Woods - wwoods (59)
* Adam Williamson - adamw (45)
* David Pravec - dpravec (31)
* Kamil Paral - kparal (20)
* Jesse Keating - Oxf13 (20)
* fenris02 (16)
* Sebastian Dziallas - sdziallas (14)
* Iarly Selbir - iarlyy (13)
* Petr Šplíchal - psss (13)
* Edware Kirk - tk009 (6)
* Kevin Fenzi - nirik (5)
* Mike McGrath - mmcgrath (1)
* Southern_Gentlem (1)
Regrets:
* Liam Li (lili)
* He Rui (rhe)
= Agenda =
*
[https://www.redhat.com/archives/fedora-test-list/2009-August/msg00903.html Proposed meeting agenda]
*
[http://meetbot.fedoraproject.org/fedora-meeting/2009-08-31/fedora-meeting.2… meetbot summary]
== Previous meeting follow-up ==
* [dpravec] - investigate creating fedora-test-announce mailing list for
Test Days, other test events, schedule updates
mailing list test-announce is ready to be used. Adamw asked if
fedora-test-list was subscribed to test-announce.
* [jlaska] - talk with Liam about how we can make the current install
test plan more attainable/achievable in the given time frames
Haven't brainstormed with Liam yet on changes for the installation test
plan
for F-12-Beta. Keep this action item on the list, will try to organize
my
thoughts and sync up with Liam.
* [jlaska] - cleanup remaining test cases for dracut and send
announcement
See announcement at
https://www.redhat.com/archives/fedora-test-list/2009-August/msg00659.html
* [jlaska] - discuss bandwith implications of hosting nightly rawhide
live images with fedora-infrastructure
spoke to mmcgrath on the fedora-admin briefly a little bit ago on the
alt.fp.org bandwith. the summary is that there haven't been any issues
reported yet, and he'd like to be kept in the loop when new milestone
drops land. Mmcgrath did note that they're interested in building a
mirror to host content should any issues surface on that one system.
Adamw asked if any download numbers were available for nightly builds?
* [Oxf13] - will do a build of the new autotest version for testing.
Packages posted and awaiting test feedback (see
https://fedorahosted.org/autoqa/ticket/9#comment:38)
* [jlaska + wwoods] to test latest autotest build
Intend to gather results early this week. Spent time last week
documenting
install and setup instructions on wiki (see
https://fedoraproject.org/wiki/Install_and_configure_autotest)
* '''UNASSIGNED''' - include a xorg-x11-drv matrix in F-12-Beta test
matrix for nouveau, intel and radeon
== AutoQA update from wwoods ==
Wwoods notifed the group that last week was official known as ''DOCS
WEEK''. For example, see the autoqa wiki category
http://fedoraproject.org/wiki/Category:AutoQA
* http://fedoraproject.org/wiki/AutoQA is the main page for the Fedora
AutoQA project
* http://fedoraproject.org/wiki/Autotest has specific info about
autotest and how we use it in AutoQA
* http://fedoraproject.org/wiki/Writing_AutoQA_Hooks and
http://fedoraproject.org/wiki/Writing_AutoQA_Tests explain how to write
autoqa hooks and tests
* http://fedoraproject.org/wiki/Install_and_configure_autotest talks a
bit about setting up your own autotest instance if you wanted to run the
autoqa code on your own
The important AutoQA lesson of the meeting was ...
<wwoods> write the test(s) first
With a written test, you can later worry about
# Deciding when the test should run
# Integrating the existing test + trigger/watch into autoqa
Psss joined the meeting to get some guidance on how to get started with
a
fedora package sanity implementation that would use autoqa. The
original idea
came from Ondrej Hudlicky: to prevent dependency problems. While
looking
around, Psss came across the autoqa project. Psss asked for guidance on
how
to get started. Wwoods reiterated the AutoQA lesson of the day ...
<wwoods> write the test(s) first
Jlaska noted that kparal and psss might have an opportunity for
collaboration
when the time is right for creating a watcher script. Wwoods commented
that
it's much easier to write watchers once you have a '''working'''
test(s).
Once you have the test, you'll know what parameters and environmental
needs
your test has. For example wwoods noted:
obviously a post-koji-build watcher is going to need.. a URL to the new
package(s). But there might be other things you haven't thought of
yet. So
try writing the tests and then you'll have some concrete examples of
what the
tests need to know and hopefully
https://fedoraproject.org/wiki/Writing_AutoQA_Tests is a bit clearer
now about
the fact that you don't need any special knowledge or code from
autoqa/autotest.
Dpravec asked for the location for the updated autotest packages.
Jkeating
pointed to http://jkeating.fedorapeople.org/infra/
Wwoods indicated the plans for the upcoming week ...
# figuring out how to get data back out of the autotest frontend/RPC
code so we can populate forms for israwhidebroken.com or similar things
# minor cleanup of std{out,err} of existing RATS test results
== Test Day updates ==
=== dracut ===
Dracut test day wiki - [[Test_Day:2009-08-27]]
Last week was the dracut test day. Jlaska has an open action item to
send the
test day summary to the list.
=== sectool ===
Sectool test day wiki - [[Test_Day:2009-09-01_Sectool]]
Eduard Beneš and Ondrej Hudlicky will host the sectool test day on
Tuesday,
Sept 1, 2009.
Fenris02 asked ...
* whether should it suggest pam_tally2 instead of _tally?
* should a default install pass level 5 ?
Adamw noted the test day wiki had some gaps and would reply to the list
with feedback.
=== Sugar-on-a-stick ===
SoaS test day wiki - [[Test_Day:2009-09-03]]
Sebastian noted he was working with Mel Chua and test cases should
arriveon
the semantic infrastructure wiki on Wednesday
Jlaska expressed excitement on using the semantic mediawiki for Soas,
and
asked whether specific hardware was needed to test. Sdziallas noted
that any
system that can run Fedora should be capable of running SoaS.
=== Xorg-x11-drv week ===
Xorg-x11-drv-* test day wiki:
* Radeon - coming soon
* Nouveau - coming soon
* Intel - coming soon
Adamw noted that wiki pages haven't yet been pulled together, however
progress would happen soon. The test day events will be similar to the
f11 days - just general testing of the drivers' capabilities, find out
where we're at, particularly with newer stuff like nouveau modesetting
== Open discussion ==
=== kparal - Using zsync to improve ISO downloads ===
http://zsync.moria.org.uk/
Kparal asked whether zsync could be used to improve downloads of large
files
(ISO's) of fedora. Discussion followed, and the group seemed to think
that
the benefits would be minimal for live image ISO's ... since they are
just a
single squashfs file.
Wwoods suggested it would be good to confirm that theory. Kparal would
try to
test downloads against live images ... and report back.
=== dpravec - New test-announce list ===
https://admin.fedoraproject.org/mailman/listinfo/test-announce
Dpravec reminded folks to sign up for test-announce mailing list. A low
traffic moderated list intended for notification about QA related test
events.
Fedora-test-list is currently a member, so any events will be sent to
fedora-test-list(a)redhat.com as well.
=== fenris02 - Features/LowerProcessCapabilities ===
Fenris02 asked for status on the F12 Feature
[[Features/LowerProcessCapabilities]].
Fenris noted it hasn't changed recently and isn't complete in F12 Alpha.
The
group agreed that any features passed the feature freeze needs to be
planned
for Fedora 13. Adamw thought there was some plan on implementing a
subset in
F12, and the remaining features in F13.
Fenris02 volunteed to check-in with sgrubb for thoughts on next steps.
=== <your topic here> ===
= Upcoming QA events =
* 2009-09-01 - [[BugZappers/Meetings]]
* 2009-09-01 - [[Test_Day:2009-09-01_Sectool|sectool test day]]
* 2009-09-03 - [[Test_Day:2009-09-03|Sugar on a stick]]
= Action items =
* adamw - to reply to sectool test day with some test day wiki
improvements
* dpravec will subscribe fedora-test-list to test-announce
* fenris02 - check-in w/ sgrubb on devel status of
https://fedoraproject.org/wiki/Features/LowerProcessCapabilities
* jlaska - catch up with lili on some test plan changes for the upcoming
F-12-Beta milestones
* jlaska - complete autotest setup doc and post autotest-0.11 test
feedback
* jlaska - send dracut test day summary to fedora-test-list
* kparal to test download zsync downloads
* UNASSIGNED - include a xorg-x11-drv matrix in F-12-Beta test matrix
for nouveau, intel and radeon
