Apr 29 09:01:35 ---	jlaska has changed the topic to: Fedora QA Meeting | gathering
Apr 29 09:02:20 <jlaska>	show of $appendage for those in attendance
Apr 29 09:02:37 *	wwoods waggles an elbow
Apr 29 09:02:45 -->	christi (n=gigi@81.180.234.249) has joined #fedora-meeting
Apr 29 09:03:06 *	jlaska will need to learn that trick
Apr 29 09:04:14 <jlaska>	adamw: around?
Apr 29 09:04:45 <adamw>	ypupers
Apr 29 09:04:55 <adamw>	just busy with some hockey trash talk
Apr 29 09:04:56 <adamw>	:P
Apr 29 09:05:00 <jlaska>	:)
Apr 29 09:05:18 <jlaska>	okay, anyone else joining for teh QA meeting, say 'hi' for the logs
Apr 29 09:05:36 -->	k0k (n=k0k@201.210.101.227) has joined #fedora-meeting
Apr 29 09:06:05 <--	Matias_Arg has quit ("Leaving.")
Apr 29 09:06:06 ---	jlaska has changed the topic to: Fedora QA Meeting | agenda (https://www.redhat.com/archives/fedora-test-list/2009-April/msg01699.html)
Apr 29 09:06:36 <jlaska>	okay, posted the agenda ... but would like to sprinkle the previous meeting follow up with some current events folks have been following
Apr 29 09:06:41 <jlaska>	agenda - https://www.redhat.com/archives/fedora-test-list/2009-April/msg01699.html
Apr 29 09:06:52 <jlaska>	minutes will be posted to - https://fedoraproject.org/wiki/QA/Meetings/20090429
Apr 29 09:07:15 ---	jlaska has changed the topic to: Fedora QA Meeting | previous meeting follow-up
Apr 29 09:07:29 <jlaska>	adamw: I've got you down for the only action item I recorded from last weeks transcript
Apr 29 09:07:31 <--	ReneP has quit (Read error: 113 (No route to host))
Apr 29 09:07:31 ---	mbonnet_ is now known as mbonnet
Apr 29 09:07:32 <jlaska>	[adamw] - post to fedora forums asking for feedback on pulseaudio issues
Apr 29 09:07:46 <jlaska>	I think you've knocked this out of the park (and then some)
Apr 29 09:08:00 <adamw>	oh, that's kinda separate from the mixer crap
Apr 29 09:08:10 <jlaska>	or another analogy ... scored 2 goals in the final 2 minutes of the 3rd period of game 7
Apr 29 09:08:23 <adamw>	THIS would be: http://forums.fedoraforum.org/showthread.php?t=220343
Apr 29 09:08:30 <adamw>	wow, you'd almost think that analogy came from somewhere specific! :)
Apr 29 09:08:42 <jlaska>	;)
Apr 29 09:08:46 <adamw>	that's the thread asking for pulse feedback - it's actually remarkably positive, no major issues
Apr 29 09:09:00 <adamw>	so that's good news
Apr 29 09:09:03 <jlaska>	interesting
Apr 29 09:09:10 <jlaska>	yes definitely!
Apr 29 09:09:49 <adamw>	not a lot of people took part in the thread, but that's quite normal - most don't bother to report success
Apr 29 09:09:59 <adamw>	so the fact there's not a bunch of people complaining is a positive sign
Apr 29 09:10:09 <wwoods>	yeah, I think those intel-8x0/intel-hda issues are about 95% squashed, with some mutant hardware remaining
Apr 29 09:10:39 <jlaska>	staying on a similar topic, but moving into the "recent events" category ...
Apr 29 09:10:46 -->	ReneP (i=ReneP@a190119.studnetz.uni-leipzig.de) has joined #fedora-meeting
Apr 29 09:10:49 <jlaska>	does this tie into the audio tracker bug?
Apr 29 09:10:52 <wwoods>	still working with jaroslav on intel8x0 and we've got a reporter who's still getting weirdness with -hda, but his hardware has other problems too, so.. everything seems mostly better
Apr 29 09:11:11 <adamw>	jlaska: AlsaVolume? not really
Apr 29 09:11:30 <adamw>	AlsaVolume is for a very particular type of bug related to the Great Mixer Debate
Apr 29 09:11:40 <jlaska>	heh, well titled
Apr 29 09:12:06 <jlaska>	wwoods: anything else on the intel8x0 front that needs chasing down?
Apr 29 09:12:24 <adamw>	if you have a card where maxing out all the volumes in gnome-volume-control still doesn't get you audio at a decent level, but dropping to alsamixer or something and adjusting a mixer element there solves the problem - that's an AlsaVolume bug
Apr 29 09:12:27 <adamw>	anything else, no.
Apr 29 09:12:45 <jlaska>	gotcha
Apr 29 09:12:56 <wwoods>	jlaska: still working on some corner cases, but I had two test machines - one died, and the laptop HD appears to be failing
Apr 29 09:13:03 <wwoods>	so I may hit a wall on this
Apr 29 09:13:22 <adamw>	well, you can replace laptop hard disks usually..
Apr 29 09:13:42 <wwoods>	although the laptop HD might turn out to be a bug in the new SMART monitoring stuff
Apr 29 09:14:26 *	jlaska makes a topic note "failing drive applet"
Apr 29 09:14:59 ---	mbonnet is now known as mbonnet_
Apr 29 09:15:31 <jlaska>	any other follow-up from last week?
Apr 29 09:15:33 <wwoods>	I'm definitely not the only one seeing that applet pop up and then noticing some ridiculous failure values - but I don't want to sidetrack things here. just a note that we need to investigate that further.
Apr 29 09:15:45 <jlaska>	wwoods: yeah you're not ... I've seen it too
Apr 29 09:16:01 <jlaska>	wwoods: I'm going to add that as an open-discussion topic, just to make sure someone is looking at it
Apr 29 09:16:30 -->	tc141516 (i=blewis@fedora/tc1415) has joined #fedora-meeting
Apr 29 09:17:09 <jlaska>	okay, going to quick run through the agenda and we can come back to this
Apr 29 09:17:19 ---	jlaska has changed the topic to: Fedora QA Meeting | autoqa update
Apr 29 09:17:49 <jlaska>	wwoods: jds2001 enabled the trac space on the autoqa hosted site today (thanks jds2001!)
Apr 29 09:18:02 <jlaska>	I've stubbed out a real *basic* start page ... https://fedorahosted.org/autoqa/
Apr 29 09:18:44 <wwoods>	I haven't touched the code since last meeting, sadly
Apr 29 09:18:44 <jlaska>	I'd like to begin getting tickets in and creating milestones for the issues you, f13 and I outlined last week
Apr 29 09:18:51 <wwoods>	definitely
Apr 29 09:19:22 <jlaska>	we're sooooo close to getting automated mails sent to the results list
Apr 29 09:19:23 <wwoods>	the TODO in the source tree is a good starting point, but you'll probably need my help in decoding those to useful tickets
Apr 29 09:19:58 <jlaska>	wwoods: okay, I'll get a basic milestone targetting completion before F-11-GA ... and start adding in what we discusse
Apr 29 09:20:10 <jlaska>	wwoods: you can definitely add in specific tasks/bugs too
Apr 29 09:20:20 <wwoods>	right
Apr 29 09:21:20 <jlaska>	the tasks we outlined seemed achievable for F-11-GA ... but if I'm aiming too aggressive, feel free to say so
Apr 29 09:21:38 <jlaska>	since you've got the code know-how
Apr 29 09:21:39 <wwoods>	remind me of what tasks those were?
Apr 29 09:22:06 <jlaska>	   > Next steps:
Apr 29 09:22:06 <jlaska>	     * [wwoods+jkeating] - update tests to consolidate mails (autoqa and watcher-* changes needed)
Apr 29 09:22:09 <jlaska>	     * [jkeating] - setup cronjob for checking out autoqa.git
Apr 29 09:22:11 <jlaska>	     * [jkeating] - setup cronjob for running 'watcher-*' scripts
Apr 29 09:22:14 <jlaska>	     * [jlaska] - update mailing list to accept mail from $USER
Apr 29 09:22:16 <jlaska>	       > create puppet managed local user
Apr 29 09:22:19 <jlaska>	     * [wwoods] - send patches to beaker-devel@ for rhtslib changes
Apr 29 09:22:21 <jlaska>	 
Apr 29 09:23:01 <jlaska>	so for the cronjob parts, we may need to beg f13 for some cycles (which I gather the F-11-Preview sucked up)
Apr 29 09:23:24 <jlaska>	but having them in trac will at least make it easier to see what's left/next etc...
Apr 29 09:23:37 <wwoods>	right
Apr 29 09:23:41 <wwoods>	yeah that all sounds reasonable
Apr 29 09:24:02 <jlaska>	okay ... moving on for now ...
Apr 29 09:24:05 <wwoods>	2 weeks 'til the first RC
Apr 29 09:24:20 <wwoods>	all I really have from now 'til then is autoqa and preupgrade
Apr 29 09:24:22 ---	jlaska has changed the topic to: Fedora QA Meeting | F-11-GA Prep
Apr 29 09:24:38 <jlaska>	wwoods: what's queued up on the preupgrade front/
Apr 29 09:25:04 ---	tibbs_ is now known as tibbs|h
Apr 29 09:25:14 <wwoods>	new version (1.1.0), some new code, lots of bugfixes
Apr 29 09:25:29 <wwoods>	it now attempts to enable new versions of every repo on your system
Apr 29 09:25:35 <wwoods>	err, every enabled repo
Apr 29 09:25:47 <wwoods>	so you should get upgrades with updates + rpmfusion
Apr 29 09:26:13 <jlaska>	nice!
Apr 29 09:26:23 <wwoods>	but this will require lots of testing, of course.
Apr 29 09:26:35 <wwoods>	also we're rejecting /boot on mdraid now, since that never actually made any sense
Apr 29 09:26:46 <wwoods>	current preupgrade code will require F11 Beta or later (which is fine with me)
Apr 29 09:26:57 <wwoods>	so you can't preupgrade to F10 anymore
Apr 29 09:27:07 <wwoods>	at least, not with the 1.1.x code
Apr 29 09:27:28 <jlaska>	is this outlined on the preupgrade project page?
Apr 29 09:27:37 <wwoods>	no
Apr 29 09:27:47 <wwoods>	I'm not really sure where I'd put it
Apr 29 09:28:04 <--	tc1415 has quit (Read error: 110 (Connection timed out))
Apr 29 09:28:16 <wwoods>	I'll put in tickets for TODO items and such when I have some time
Apr 29 09:28:32 <jlaska>	sounds like a worthwhile update to announce, perhaps blog or a announce to fedora-test-list@
Apr 29 09:28:34 <wwoods>	oh, it switched from bzr to git (thanks jds2001)
Apr 29 09:28:58 <wwoods>	yeah, as soon as I have something worth testing
Apr 29 09:29:05 <jlaska>	okay ... swinging back to F-11-GA
Apr 29 09:29:29 <jlaska>	as wwoods said, just about 2 weeks until the schedule has a possible RC tree landing
Apr 29 09:29:29 -->	RadicalRo (n=radical@77.36.4.49) has joined #fedora-meeting
Apr 29 09:29:34 *	jlaska looking at http://poelstra.fedorapeople.org/schedules/f-11/f-11-releng-tasks.html
Apr 29 09:30:02 <jlaska>	there's a big window there for "prepare and test" 05-12 - 05-21
Apr 29 09:31:07 <jlaska>	I'd like to try and get a more specific date when we can expect a drop ... but that's somethign I'll need to ask for f13 for feedback on
Apr 29 09:32:15 <wwoods>	that probably depends on the blocker list
Apr 29 09:32:33 -->	itami (n=itami@h219-110-132-244.catv02.itscom.jp) has joined #fedora-meeting
Apr 29 09:32:42 <--	Pikachu_2014 has quit (Read error: 60 (Operation timed out))
Apr 29 09:32:43 <wwoods>	there's not a lot of point in spending a day building images if you're just going to have to do it again the next day to pull in 5 blocker fixes
Apr 29 09:32:53 <wwoods>	so that really needs to get cut down to size ASAP
Apr 29 09:33:00 <jlaska>	yeah I agree
Apr 29 09:33:15 <adamw>	weren't we going to have a blocker list review meeting?
Apr 29 09:33:16 <jlaska>	if testing of the RC is needed, we need to reserve time to do it
Apr 29 09:33:34 <wwoods>	the blocker list stands at 74 bugs right now
Apr 29 09:33:40 <wwoods>	that's almost too long for a meeting
Apr 29 09:33:41 <jlaska>	adamw: there are 2 blocker bug review days (2009-05-11 - 2009-05-12)
Apr 29 09:33:46 <adamw>	some of which are actually other tracker bugs...
Apr 29 09:34:03 <adamw>	jlaska: ah k
Apr 29 09:34:24 <wwoods>	yes, 7/74, which still leaves 67 actual proposed blockers
Apr 29 09:34:40 <adamw>	i mean, it's *more* than 74, not fewer
Apr 29 09:34:40 <jlaska>	adamw: but I'm with wwoods, it's fairly difficult to set aside time to review the list during a 'meeting'
Apr 29 09:34:57 <adamw>	sure, days is fine
Apr 29 09:34:57 <jlaska>	Are there other strategies to divide/conquer the list?
Apr 29 09:35:11 <wwoods>	round up by topic or sub-blocker - anaconda blicker, Xorg bugs, etc
Apr 29 09:35:20 <wwoods>	(blicker?)
Apr 29 09:35:39 -->	spoleeba (n=one@fedora/Jef) has joined #fedora-meeting
Apr 29 09:35:46 <jlaska>	yeah the blocker bug theme has been used out the wazzoo so that might be a good approach
Apr 29 09:36:08 <jlaska>	certainly let's one target a component set they might be most familiar with
Apr 29 09:36:22 <--	linuxguru has quit (Read error: 110 (Connection timed out))
Apr 29 09:36:59 <jlaska>	a fair amount of MODIFIEDs on that list
Apr 29 09:37:45 <jlaska>	I don't mind taking the ancaonda blocker list ... it's near and dear for me :)
Apr 29 09:38:06 <adamw>	i just knocked one off the list, a dupe of the infamous grey-screen live usb bug
Apr 29 09:38:22 <jlaska>	that's the wrong livecd-creator bug?
Apr 29 09:38:26 <jlaska>	errr syslinux
Apr 29 09:38:28 <adamw>	yeah
Apr 29 09:38:32 <jlaska>	nice
Apr 29 09:38:51 <jlaska>	okay, so should we plan to reserve those 2 days to walk this list and divide up by component areas?
Apr 29 09:38:53 <--	neverho0d has quit (Read error: 113 (No route to host))
Apr 29 09:39:14 <adamw>	works for me
Apr 29 09:39:21 <jlaska>	should we ping for retesting of the MODIFIEDs now?
Apr 29 09:39:49 <adamw>	sounds sensible
Apr 29 09:40:21 -->	thomasj_ (n=thomasj@e180182152.adsl.alicedsl.de) has joined #fedora-meeting
Apr 29 09:40:22 <jlaska>	any other ideas/concerns ?
Apr 29 09:40:35 <jlaska>	what do we do with F11Target?
Apr 29 09:41:25 <jlaska>	it'd be great to have the bugs listed by F11 Feature
Apr 29 09:41:31 -->	neverho0d (n=psv@vpn-pool-78-139-211-170.tomtel.ru) has joined #fedora-meeting
Apr 29 09:41:38 <--	SMParrish has quit (Read error: 113 (No route to host))
Apr 29 09:42:11 <jlaska>	I guess that's essentially what the blocker bugs have become
Apr 29 09:42:13 <wwoods>	F11Target can probably use some triaging. Typically some of the bugs there can be fixed by F11 updates
Apr 29 09:42:14 <adamw>	what do we do with f11target? not worry about it until f11blocker is doing better :)
Apr 29 09:42:21 <--	Sonar_Gal has quit (Read error: 110 (Connection timed out))
Apr 29 09:42:24 <wwoods>	and some of them will need to be moved to F12Blocker or F12Target
Apr 29 09:42:27 <--	christi has quit ("leaving")
Apr 29 09:42:45 <jlaska>	wwoods: so Target is just the holding area for things that aren't Blockers?
Apr 29 09:42:53 <wwoods>	rarely do we move something from Target to Blocker, but I guess it's possible
Apr 29 09:42:53 <jlaska>	"nice to have" vs "must have"
Apr 29 09:42:56 <wwoods>	right
Apr 29 09:43:00 <jlaska>	gotcha
Apr 29 09:43:20 <wwoods>	"things we really really want fixed by F11". typically it means we'd be willing to break freeze for a fix for that bug
Apr 29 09:43:44 <wwoods>	but we wouldn't delay the release over it
Apr 29 09:44:13 <jlaska>	that's Target?
Apr 29 09:44:41 -->	moixs (n=chatzill@81.13.143.9) has joined #fedora-meeting
Apr 29 09:45:16 <wwoods>	yeah
Apr 29 09:45:29 *	jlaska wonders if we dropped 'Target' ... would people notice?
Apr 29 09:45:35 <wwoods>	Blocker is for things we'd actually delay the release over
Apr 29 09:45:43 <jlaska>	right, that makes sense
Apr 29 09:46:24 <--	thomasj has quit (Nick collision from services.)
Apr 29 09:46:35 <jlaska>	so I don't have any real action items out of this, but more just a heads up ... there's rougly 2 weeks until an release candidate tree will be provided by rel-eng
Apr 29 09:46:59 <jlaska>	I'll take an action item to walk the anaconda bugs on that list
Apr 29 09:47:06 <jlaska>	wwoods: you've already been monitoring sound issues
Apr 29 09:47:19 <wwoods>	well, some specific sound issues that cause pulseaudio to crash
Apr 29 09:47:27 <jlaska>	and adamw, you're pretty well plugged into X11 and the volume bugs
Apr 29 09:47:28 <wwoods>	adamw is all over the volume control issues
Apr 29 09:47:38 <--	giallu has quit (Read error: 110 (Connection timed out))
Apr 29 09:47:53 <adamw>	yeah, we should be good for the volume stuff
Apr 29 09:48:01 <adamw>	x bugs i am continuing to monitor
Apr 29 09:48:13 <jlaska>	eggsellent
Apr 29 09:48:21 <adamw>	i used nouveau as a little test platform for priority/severity - i graded all open nouveau rawhide bugs using those fields
Apr 29 09:48:33 <adamw>	so if you're interested you can do a search and order by priority or severity to see how that works out
Apr 29 09:48:41 <jlaska>	awesome
Apr 29 09:48:52 <jlaska>	did you get any feedback on that?
Apr 29 09:48:54 <adamw>	intel and radeon i just added appropriate bugs to the blocker
Apr 29 09:49:04 <adamw>	i mentioned it to ben, he says it's neat except he got a lot of emails
Apr 29 09:49:04 <wwoods>	I'll keep an eye on any selinux issues if that helps
Apr 29 09:49:13 <jlaska>	heh :)
Apr 29 09:49:16 <adamw>	so i need to test if an email gets sent out if i do nothing but change priority/severity (no comments)
Apr 29 09:49:23 <jlaska>	wwoods: ah good call, thanks (re: selinux)
Apr 29 09:49:44 <wwoods>	gotta check to see if there's a bug about this upgrade thing
Apr 29 09:49:51 ---	thomasj_ is now known as thomasj
Apr 29 09:49:51 <wwoods>	should be fixed in policy -23 but that's not in preview
Apr 29 09:50:07 <wwoods>	so we might get reports like "X stopped working after upgrade to Preview"
Apr 29 09:50:09 <adamw>	wwoods: btw, skvidal is very pissed about a bug which breaks yum upgrade from f10 to f11 within a gnome terminal
Apr 29 09:50:21 <adamw>	https://bugzilla.redhat.com/show_bug.cgi?id=494046
Apr 29 09:50:24 <buggbot>	Bug 494046: high, high, ---, besfahbo, ASSIGNED, updating fontconfig to rawhide then ANY font package causes gnome-terminal to segfault
Apr 29 09:50:24 <wwoods>	adamw: yeah, well, you know my policy on yum upgrades
Apr 29 09:50:34 <adamw>	i set it to blocker target rather than blocker because of your position on yum upgrades
Apr 29 09:50:37 <adamw>	but he didn't like that
Apr 29 09:50:41 <wwoods>	still worth fixing, but not a blocker
Apr 29 09:50:54 <adamw>	just wanted to give a heads-up in case you encounter him on the rampage :)
Apr 29 09:51:00 <wwoods>	also worth getting onto the f11 common bugs page until such time as we have a fix
Apr 29 09:51:02 -->	hpachas-PE (n=hpachas@200.37.120.18) has joined #fedora-meeting
Apr 29 09:51:18 <jlaska>	yeah that's a good candidate for that bz
Apr 29 09:51:31 <wwoods>	oh we had some words in #fedora-devel earlier. he says he'll get that bug onto the common bugs page and reassign all bugs about this to me
Apr 29 09:51:41 <wwoods>	which is fine, I'm happy to say "don't do yum upgrades" over and over
Apr 29 09:51:47 <jlaska>	is this caused by preupgrade?
Apr 29 09:51:51 <wwoods>	no, it's caused by a yum upgrade
Apr 29 09:52:03 <wwoods>	you have to be running the yum upgrade in gnome-terminal on a live system
Apr 29 09:52:10 <wwoods>	and then gnome-terminal will crash and mess up your upgrade
Apr 29 09:52:23 <wwoods>	certainly worth documenting and trying to fix
Apr 29 09:52:37 <wwoods>	definitely not going to recommend delaying the release over it
Apr 29 09:52:39 <jlaska>	do a _majority_ of people yum upgrade between major releases?
Apr 29 09:52:54 <wwoods>	I don't think we have any way of answering that question
Apr 29 09:52:54 <jlaska>	yeah that's seems very sane ... document the issue
Apr 29 09:53:02 <jlaska>	yeah fair point
Apr 29 09:53:19 -->	linuxguru (n=linuxgur@unaffiliated/linuxguru) has joined #fedora-meeting
Apr 29 09:53:21 <wwoods>	some people do, and it kinda works sometimes, except when things like this happen
Apr 29 09:53:40 <jlaska>	I've just never had an expectation that it would seemlessly work, so never really try
Apr 29 09:53:42 <wwoods>	we've explicitly told people that we don't support that method for years
Apr 29 09:53:50 <jlaska>	but sounds like there are some adventurous folks out there :)
Apr 29 09:53:53 <wwoods>	it's never seamless but it usually mostly works so people do it
Apr 29 09:53:53 <adamw>	skvidal's comment on that was "who is we" :)
Apr 29 09:54:22 <jlaska>	is a recommend path in the installation guide?
Apr 29 09:54:24 <wwoods>	everyone who works on the installer or upgrade tools - including seth - is on record as saying that yum upgrades are a really bad idea
Apr 29 09:54:44 <adamw>	good enough for me
Apr 29 09:54:48 <wwoods>	if it's in the installation guide I'd be very surprised
Apr 29 09:54:54 <jlaska>	http://docs.fedoraproject.org/install-guide/f10/en_US/sn-upgrade-tree.html
Apr 29 09:55:14 <jlaska>	afaict ... we only document anaconda upgrades
Apr 29 09:55:27 <jlaska>	we don't explicitly document *not* doing yum upgrades
Apr 29 09:55:32 <jlaska>	which we can't really document all the negatives
Apr 29 09:55:57 <jlaska>	is it worth requesting a blurb in the installation guide about "Upgrading Using yum"
Apr 29 09:56:00 <wwoods>	it's undocumented, not recommended, and QA/anaconda team policy has been "don't do that" for years and years
Apr 29 09:56:07 <jlaska>	with lots of cautionary text ... flames ... explosions etc..?
Apr 29 09:56:09 <wwoods>	hell no
Apr 29 09:56:55 <wwoods>	it's unofficial and undocumented and it should stay that way
Apr 29 09:57:11 <wwoods>	unless FESCo and/or the board mandate that this needs to be supported
Apr 29 09:57:24 <wwoods>	and write packaging policy for making scriptlets do the right thing in this case
Apr 29 09:57:51 <jlaska>	okay, we'll just keep the URL for the prefered documented upgrade method handy for any daring users :)
Apr 29 09:58:09 <jlaska>	any other thoughts on the upcoming F-11-GA?
Apr 29 09:58:21 *	jlaska going to change topic ...
Apr 29 09:58:27 <wwoods>	it's just not a supportable upgrade method. no other operating system allows anything of the sort
Apr 29 09:58:31 <wwoods>	that way lies madness
Apr 29 09:59:01 <jlaska>	wwoods: I agree 100% ... was just curious if it would be worth the effort to explicitly state it's a "buyer beware" method
Apr 29 09:59:03 <wwoods>	every moment spent on making that work instead of improving the usability and reliability of sane upgrade methods
Apr 29 09:59:06 <wwoods>	is a moment wasted, in my opinion
Apr 29 09:59:40 ---	jlaska has changed the topic to: Fedora QA Meeting | Upcoming events
Apr 29 09:59:54 <wwoods>	no, in my opinion it should remain an undocumented hack
Apr 29 10:00:00 <jlaska>	okay
Apr 29 10:00:15 <jlaska>	okay, didn't want to spend a lot of time on this, more just an FYI with an open question
Apr 29 10:00:20 <jlaska>	* SSSD - on track - https://fedoraproject.org/wiki/Test_Day:2009-04-30
Apr 29 10:00:39 <jlaska>	the SSSD test day for tomorrow is on track ... I'm reposting the live images now with corrected kickstart
Apr 29 10:00:45 <jlaska>	however ...
Apr 29 10:00:45 <jlaska>	 * Virtualization - needs QA -
Apr 29 10:00:45 <jlaska>	                https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization
Apr 29 10:01:02 <--	cassmodiah has quit (Remote closed the connection)
Apr 29 10:01:03 <jlaska>	I'm looking for volunteers to help organize test cases for the Virtualization test day next week
Apr 29 10:01:17 <adamw>	how do you mean exactly 'organize'?
Apr 29 10:01:53 -->	fhornain (n=fhornain@fwcirb.irisnet.be) has joined #fedora-meeting
Apr 29 10:02:08 <fhornain>	Belgian Guys ?
Apr 29 10:02:09 <wwoods>	as in "write"?
Apr 29 10:02:11 <jlaska>	we have a good list of high-level test areas
Apr 29 10:02:45 <jlaska>	I'm looking for volunteers to help identify some high-level test cases for those test areas on the wiki , or if willing, stub out some test cases
Apr 29 10:03:10 <jlaska>	doesn't necesarily have to be you guys, just open to ideas on how to solicit help
Apr 29 10:03:24 <adamw>	is there a virtualization list?
Apr 29 10:03:33 <adamw>	i know someone writes a virt section for fwn each week
Apr 29 10:03:41 <jlaska>	there is a fedora-virt list ... and most of those guys are signed up thanks to markmc for organizing that
Apr 29 10:03:47 <jlaska>	yeah that's markmc
Apr 29 10:03:50 <adamw>	could ask them for help with the test cases
Apr 29 10:04:01 <adamw>	otherwise it'd be the good old mail to fedora-test-list
Apr 29 10:04:41 <jlaska>	yeah, I think that's the next best thing ... just see if anyone is interested in volunteering
Apr 29 10:05:22 <jlaska>	alright, I'll drop something to the list to see if there are any takers
Apr 29 10:05:31 ---	jlaska has changed the topic to: Fedora QA Meeting | Open Discussion
Apr 29 10:05:46 <jlaska>	wwoods: do you want to talk about the failing disk icon?
Apr 29 10:05:59 <jlaska>	Reported on fedora-test-list (see https://www.redhat.com/archives/fedora-test-list/2009-April/msg01593.html)
Apr 29 10:06:19 -->	vincentvdk2 (n=vincent@ip-81-11-187-162.dsl.scarlet.be) has joined #fedora-meeting
Apr 29 10:06:40 <wwoods>	ah - spoleeba was just seeing this in #fedora-devel as well
Apr 29 10:06:44 <jlaska>	I no longer see the failing disk icon on my system
Apr 29 10:06:48 <wwoods>	I think there may be cases where we're getting false positives
Apr 29 10:07:06 <wwoods>	there was a recent fix for (I think) libatasmart that may have fixed some of those
Apr 29 10:07:14 <jlaska>	aaah
Apr 29 10:07:24 <wwoods>	but we should investigate the possibility that we're going to get false positives from this new, untested code
Apr 29 10:07:28 <wwoods>	and freak people out
Apr 29 10:07:31 <vincentvdk2>	fhornain: i'm ready
Apr 29 10:07:50 -->	cassmodiah (n=cass@fedora/cassmodiah) has joined #fedora-meeting
Apr 29 10:07:53 <wwoods>	so! we need some info on how to check the data when the icon pops up
Apr 29 10:07:57 <wwoods>	and see if it makes sense
Apr 29 10:08:17 <jlaska>	christi mentioned some smart commands you can run on #fedora-qa before the meeting
Apr 29 10:08:22 <adamw>	smartctl --all /dev/sda , i think
Apr 29 10:08:26 <wwoods>	interesting
Apr 29 10:08:26 <jlaska>	yeah
Apr 29 10:08:42 -->	sdziallas (n=sebastia@p5B046EB5.dip.t-dialin.net) has joined #fedora-meeting
Apr 29 10:08:42 <wwoods>	you can also view it all from palimpset
Apr 29 10:09:00 <jlaska>	sounds like another candidate to 1) make sure there is a bugzilla for this, 2) get something into CommonBugs ?
Apr 29 10:09:02 <wwoods>	but we'd want a way to doublecheck in F10/F9 to be sure
Apr 29 10:09:33 <wwoods>	so smartctl commands would be helpful
Apr 29 10:09:50 <fhornain>	Ok vincent
Apr 29 10:09:50 <fhornain>	Did you finish the document ?
Apr 29 10:10:00 <jlaska>	looks like we're getting some meeting overlap here
Apr 29 10:10:20 <wwoods>	shall we retire to #fedora-qa?
Apr 29 10:10:25 <jlaska>	I'll take an action item to chase down some bugs/relnotes for that one ... unless anyone else is jumping for that
Apr 29 10:10:45 <jlaska>	yeah ... I'm going to reset /topic and we can continue open discussion in #fedora-qa
Apr 29 10:11:02 <jlaska>	wwoods: adamw thanks for your time!