15:00:49 #startmeeting Fedora QA 15:00:49 Meeting started Mon Oct 3 15:00:49 2011 UTC. The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:56 #meetingname fedora-qa 15:00:56 The meeting name has been set to 'fedora-qa' 15:01:01 #topic Roll Call 15:01:20 So, anyone here despite the late notice (again)? 15:01:28 morning 15:01:36 #chair adamw 15:01:36 Current chairs: adamw tflink 15:01:45 sorry, i was offline all day yesterday so i couldn't announce anything 15:02:22 adamw: excuses, excuses, excuses ... :-D 15:03:51 hey guys 15:04:18 Hey 15:05:13 i think our brno contingent is at fudcon 15:05:27 ah, I wasn't sure if that went through today or not 15:06:06 well, I suppose it's about time to get started 15:06:26 adamw: you want to drive or should I? 15:06:27 I think it ended yesterday, but there may be travel today. 15:07:15 #topic Previous Meeting Follow-Up 15:07:30 tflink: you go ahead 15:07:38 OK, I'm seeing 2 things from last week 15:07:49 one of them is for me 15:07:58 tflink to build python-yourls for F15, F16, EL6 and create update 15:08:39 which didn't get done. Now that beta's gone gold, I should have a bit more time to get that done 15:08:54 #info python-yourls still not built 15:09:04 #action tflink to build python-yourls for F15, F16, EL6 and create update 15:09:25 #info maxamillion create ticket for pkgdb to link to package-specific test cases 15:09:41 this looks like it had some traction last week 15:09:50 #link https://fedorahosted.org/packagedb/ticket/223 15:10:05 cool 15:10:25 and it doesn't look like maxamillion is around for any other updates 15:10:48 but it looks like the ticket is seeing progress 15:11:01 #info progress is being made, packagedb ticket has been assigned 15:11:18 if there are no other followup items ... 15:11:50 #topic F16 Beta Wrap-Up 15:12:05 #info F16 Beta RC4 => GOLD!!! 15:12:08 yaaaay 15:12:15 much thanks to all who tested 15:12:37 seeing the RC4 test matrix filled up that quickly was awesome 15:13:13 there is one item left for testing beta, though 15:13:32 #topic F16 Beta Preupgrade 15:13:41 #link https://bugzilla.redhat.com/show_bug.cgi?id=737731 15:13:58 #info F15 fix for F16 preupgrade 15:14:18 it looks like we have a new test build for F15 preupgrade that could use some testing 15:14:18 yeah 15:14:27 we need to test that quick so hughsie can submit an update 15:14:32 #link http://people.freedesktop.org/~hughsient/fedora/15/i386/ 15:14:34 i was gonna do it right after this meeting, the more testing the better 15:14:41 * tflink is installing F15 right now to test 15:15:21 i keep a clean f15 'master' image around in virt-manager 15:15:26 hopefully, we can get that to stable when F16 beta releases 15:15:28 then any time i want to test upgrade stuff i just clone it 15:15:33 somewhat faster than doing a fresh install 15:15:45 if I was smart, I'd start using LVM snapshots 15:15:57 but I usually don't remember until after I've done the upgrade 15:16:15 heh 15:16:26 anyways, yeah, we should get that tested 15:16:27 anything else for beta wrap up? 15:16:30 the other thing we need to do is common bugs 15:16:40 there's probably a ton of things with commonbugs tag and some more that should have it 15:16:51 #topic F16 Beta CommonBugs 15:16:59 i'm gonna take a look through final blockers and rejected blockers and tag anything that looks like it needs it 15:17:07 and i'll write up whatever i can; help with that is welcome of course 15:17:10 #info There are a lot of things with the commonbugs tag that need to be documented 15:17:38 http://bit.ly/fedora-commonbugs-proposed is the list of bugs proposed for commonbugs 15:17:52 a few may be old f15 stuff but mostly they'll be f16 things 15:17:53 #link https://fedoraproject.org/wiki/Common_F16_bugs 15:18:06 #link https://fedoraproject.org/wiki/Common_F16_bugs 15:18:27 so good, they linked it twice 15:18:36 whoops 15:18:38 #undo 15:18:38 Removing item from minutes: 15:19:07 #link http://bit.ly/fedora-commonbugs-proposed 15:19:36 Yay! Documentation fun time! 15:19:49 anything else for beta wrap up? 15:20:26 #topic F16 Final Prep 15:20:39 I don't think that there is a whole lot to say about this ATM 15:20:42 let's ship the beta and go on vacation! 15:20:49 https://bugzilla.redhat.com/show_bug.cgi?id=742695 EFI in virtualbox gets text install ? corner issue 15:20:51 #info F16 blocker bug review meetings have started 15:21:37 that was rather random 15:22:24 anyhow, other topics for final preparations? 15:22:51 satellit_: efi has to provide info to the OS about the video mode, i believe...it might not be doing it right. 15:23:07 * tflink assumes not and moves on 15:23:20 #topic Upcoming QA Events 15:23:32 We've got one event coming up this week 15:23:44 #info Printing Test Day on Thursday 15:23:51 #link http://fedoraproject.org/wiki/Test_Day:2011-10-06_Printing 15:24:31 coolbeans 15:24:34 it looks to me like preparations are coming along well 15:24:41 yeah, twaugh's usually on top of that one 15:24:43 the next one is 15:24:55 #info Fedora Pacakger for Eclipse test day is next week 15:25:03 #link http://fedoraproject.org/wiki/Test_Day:2011-10-13_Fedora_Packager_for_Eclipse 15:25:16 this also looks like it's coming along well 15:26:24 cool, so we're set for those. 15:26:32 looks like 15:26:49 the fedora packager test day page looks like it'll need some minor updating but that isn't until next week 15:26:49 we should probably get back to talking about proventester stuff, but we'd need more people around for that, and we may not have time before final rush is on. 15:27:12 there should be a proventesters meeting on wednesday 15:27:19 * tflink will ask nirik about it 15:27:37 yeah. 15:28:17 #topic Proventesters 15:28:28 adamw: was there anything in particular that you wanted to talk about? 15:28:48 not sure how useful the meetings are yet, but I'd like to at least do 1-2 more now that beta is done and people might have more time to look at it. 15:29:20 yeah, we cut the last meeting short due to beta testing 15:29:33 yeah, couple more meetings would be great 15:29:39 i'll try and actually be around for the next one :) 15:30:46 Anything else that we want to cover about proventesters? 15:31:08 * tflink assumes that we'll just leave it for wednesday 15:31:15 if folks have ideas for recruitment, testing coverage or the like, please do bring it up wed. 15:31:39 nirik: I assume that you're planning to send out the announcement etc.? 15:31:40 we still could do with better stats, which is something that never quite gets important enough to sort out 15:31:43 but it really ought to be possible 15:31:58 adamw: suggestions for better stats welcome :) 15:32:04 Some cookbook stuff for running old Fedora instances in a VM. 15:32:06 I was wondering if we could do better also documenting (in one place) the tools and where to look for things. 15:32:07 we can mock stuff up before proposing it in bodhi 15:32:42 tflink: yeah, unless someone else would like to. :) That would be fine with me. 15:32:53 #info proventesters meeting on Wednesday 15:33:05 I don't know that any of my home hardware will really support this practically, but I don't usually run old Fedora's unless I am having kernel - hardware interactions causing problems. 15:33:25 #info suggestions for recruitment strategies, new stats etc. are welcome 15:33:36 brunowolff: I am going to look at setting up a dual boot f14/f15 on my old old laptop... just so I can test stuff on bare hardware. ;) 15:33:42 nirik: as long as it gets sent out :) 15:34:53 * tflink is wondering if we should start the brainstorming on test@ now instead of waiting for wednesday 15:35:02 unless that thread was already started and I just forgot 15:35:54 Live images are another way to test things, but I have issues with those as well, because of old BIOS that don't like to boot from USB drives. 15:36:39 * tflink wanted to look into booting from iSCSI targets to test multiple releases on the same HW 15:36:56 but that requires somewhat specialized HW and time to figure it all out 15:37:25 * satellit_ I use 250 Gb usb external drives with f14 f15 f16 installed (each with virtualbox and livecd-tools ) easy to boot up each for tests 15:38:55 well, I'm thinking that we can move the brainstorming to test@ and hopefully we'll get some more good ideas 15:39:07 and with that, we come to 15:39:16 #topic Open Discussion 15:39:28 any other topics that folks want to discuss? 15:40:11 we do have a bunch of criteria updates to do/discuss 15:40:21 i'll try and fire off proposals for those to the list 15:40:26 I saw an issue with a live image using F16 include updates-testing failing to properly run gdm because of something selinux related. 15:40:36 ok, I know that I don't have any of that organized 15:40:45 This sounded similar to a bug I saw discussed, but can't find it now. 15:40:59 oh, and we should check karma for beta updates. 15:41:35 #action adamw to send criteria update proposals to test@ 15:41:40 This was with Adam's patch to spin-kickstarts, but I didn't see anything in the patch that was likely to cause this. 15:42:37 brunowolff: check without my patch, and file an selinux bug if it's still there, i guess 15:42:38 I was hoping someone might remember more about the bug so I could find it. It had to do with one bug hiding another. 15:42:45 but yeah, my patch shouldn't change anything tehre 15:43:03 the similar bug we had as a beta blocker was https://bugzilla.redhat.com/show_bug.cgi?id=738803 , i think 15:43:14 note the gnome spin boots straight to gnome now, there is no gdm step 15:43:24 When the first bug was fixed, some files didn't get relabelled causing an issue with selinux. 15:44:37 Yeah that's the one. 15:45:20 This seems similar, and I wanted to see if I can figure out if the bug was resurrected or if something else is going on. 15:45:43 okay, cool 15:45:46 keep us up to date 15:46:54 any other topics 15:46:56 ? 15:47:03 I was getting the somethings gone wrong message instead of a login page, so it may have actually been gnome not gdm. And the hardware is old, so fallback mode might work differently. 15:48:14 wait, what message exactly? 15:48:30 when you boot on hardware that can't manage shell, it'll boot to fallback mode and give you a sadface message about how shell didn't work 15:48:35 that's all intentional, though: it's not a bug 15:49:11 if the system tries to start shell but something goes wrong and it gives you the fail whale and forces you to 'log out', there's a bug 15:49:17 two different messages 15:49:43 I forget the exact wording, but it was the usual gnome shell has a fatal problem and asks you to logout. 15:50:25 okay, then that's shell, not fallback. 15:50:42 I noted an selinux warning so I used CA-F2 to get to the console, switched to permissive mode and then went back to X and was able to get in. 15:51:41 okay. so yeah, check it out some more then file a bug 15:52:43 cool, any other topics? 15:52:48 i've noticed that sometimes download via dl is slow compared to serverbeach1, should we be mentioning sb1 in the announcements? do other people see this? 15:53:14 * tflink hasn't tried both 15:53:16 robatino: if you can ping in #fedora-admin when you see that we can try and track it down... 15:53:23 i generally don't get a constant full-speed download, it varies from roughly dialup speed to my maximum (350 KBytes/s) 15:53:31 odd. 15:53:39 * nirik gets 2MB/sec or so from dl... 15:53:46 i used to get constant full-speed download 15:54:10 * tflink also gets 2M/s from dl 15:54:35 sb1 is still mirroring, so mentioning it should be fine too I guess... 15:54:59 it'll be running at peak for a while, then slow to around 10 KBytes/s, then jump to peak, etc. 15:56:00 sb1 syncs up about an hour after dl i think. 15:56:13 yeah, there's a delay there... 15:56:32 i'll try downloading something after the meeting and if i see it again, ask in #fedora-admin 15:57:23 yes, i sort of dislike sb1 because of the delay - i used to delay the announcements until after sb1 synced up 15:57:48 dl is using the same backend storage as secondary01/alt/releng... so it's pretty instant. ;) 15:59:40 any other topics? 16:00:35 * tflink sets fuse for 2 minutes 16:02:10 OK, thanks for coming everyone! 16:02:20 * tflink will be sending out minutes shortly 16:02:23 #endmeeting