15:59:58 #startmeeting Fedora QA meeting 15:59:58 Meeting started Mon Feb 27 15:59:58 2012 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:02 #meetingname fedora-qa 16:00:02 The meeting name has been set to 'fedora-qa' 16:00:06 #topic roll call 16:00:14 call your rolls, people! 16:00:19 * nirik is lurking. 16:00:20 * kparal rolls 16:00:20 * pschindl is here 16:00:39 * mkrizek here 16:00:44 ooh, what rolls can we choose from? 16:01:00 * adamw calls his roll bob 16:01:04 before I eat it. 16:01:29 * jskladan wantz a roll with goat cheese and beef ham 16:01:46 jskladan: beef ham? Isn't that an oxymoron? 16:01:58 unless...it's a beefy miracle 16:02:12 it all makes sense now ... 16:02:15 * brunowolff is lurking for the first 1/2 hour, then I have a work meeting. 16:02:18 * Southern_Gentlem sitting in my rocking chair with rollers (so i can rock and roll) 16:02:30 hey everyone, let's keep talking nonsense about rolls for the first half hour 16:02:55 so we can have an even longer meeting? 16:03:09 and so bruno misses it 16:03:11 tflink: http://www.alibaba.com/product-free/215780949/Smoked_Beef_Ham.html 16:03:42 Thta's better than being fired. 16:03:44 with a name like Delicious Food Industries, how can you go wrong. 16:03:56 hehe 16:04:06 From both work and QA. 16:04:23 jskladan: huh, you learn something new every day 16:04:35 at last! the meeting is useful! 16:04:45 #chair jskladan 16:04:45 Current chairs: adamw jskladan 16:04:49 .fire adamw 16:04:49 adamw fires adamw 16:04:53 i'm outta here 16:05:09 ok, I call anarchy time! 16:05:37 :P 16:05:38 #topic previous meeting follow up 16:05:54 aaaaaaand you fell right into the bear trap 16:06:02 THERE IS NO PREVIOUS MEETING FOLLOW-UP 16:06:25 #info adamw is in denial about previous meeting! 16:06:38 moving on then :) 16:06:42 heheh 16:06:48 we had no action items from last week 16:06:53 so i just left it out 16:07:00 #topic Fedora 17 Alpha wrap-up and Beta prep 16:07:23 IIRC F17 was declared gold on Feb 22 16:07:29 soo, we signed off on alpha. i was probably drunk or something. 16:07:37 also, my birthday 16:08:00 that explains being drunk 16:08:01 we signed off on your birthday? 16:08:09 i think so? 16:08:15 you're not sure? 16:08:18 someone is spending a bit too much time with processes 16:08:20 we definitely need to get common bugs done, cos this thing is riddled with them 16:08:31 Sorry I'm late 16:08:34 class ran over 16:08:42 #chair j_dulaney 16:08:42 Current chairs: adamw j_dulaney jskladan 16:09:06 What did I miss wrap-up wise? 16:09:25 nothing 16:09:50 so yeah, since we have that kernel slowdown bug, and sound not working, and the installer blowing up if you have any other distro installed... 16:09:51 rolls 16:10:06 i'll start off the common bugs page today, if anyone else wants to throw in some contributions that'd be great. 16:10:27 Sound works at least sometimes as I am listening to music on F17 right now. 16:10:51 Sound not working = why I have not upgraded bare metal to F17 yet 16:10:58 * j_dulaney needs his Bach 16:11:20 j_dulaney: it's incredibly easy to work around, you just cut a bit out of pulseaudio's config or install consolekit. 16:11:27 but explaining that is of course why we need the common bugs page... 16:11:44 we also need to make sure a livecd-tools update gets karma'ed and pushed for f16 and f15 asap 16:11:47 i'll poke bcl about that today 16:12:09 #action adamw to start common bugs page 16:12:20 adamw: Why does pulse still want consolekit in it's config? 16:12:23 #action adamw to poke bcl about livecd-tools updates for fixing bugs writing f17 16:12:34 I haven't seen the flood from updates-testing to f17 after goldness. Does releng need to get reminded it's OK for stable updates? 16:12:45 j_dulaney: because no-one thought to take it out of there, and then when we did, we found PA doesn't compile any more, so we coldn't fix it quickly. 16:12:53 brunowolff: probably, good point 16:12:56 Huh 16:13:08 #action brunowolff to ping release engineering about post-freeze update re-opening for f17 16:13:09 brunowolff: I was waiting until dgilmore finished testing the ec2 image 16:13:15 Isn't sound a final criteria? 16:13:16 if thats done we can start anytime. 16:13:19 fastest. action item. ever. 16:13:23 j_dulaney: no, it's a beta one. 16:13:25 OK. 16:13:32 j_dulaney: happily, we just released alpha, so no problem. :P 16:13:43 Indeed 16:14:08 ec2 still doesnt boot 16:14:23 brunowolff: maybe we will get updates in the next couple of days 16:14:34 or we will get updates and no ec2 images for alpha 16:15:13 Do ec2 images need to be part of the goldness process? 16:15:34 we didn't write that SOP yet, so we don't have a good answer. 16:15:52 there's a 'deliverables' action item zinging around between qa and releng but it hasn't ever got much traction. 16:16:00 dgilmore: Where are ec2 images dumped? 16:16:07 Otherwise when you push stuff from testing to stable it goes into a black hole. 16:17:53 #info updates pushes are still not happening because we don't have an ec2 image yet 16:18:52 One possible future state would be to use the empty updates repository to hold stuff on its way from testing to stable. 16:19:06 all updates?? 16:19:17 f17 updates. 16:19:18 how do those two depend on each other (sorry, i'm less than brainy here) 16:19:23 This would also handle dealing with stable not being rebuilt at the same times as the testing repo. 16:19:49 rbergeron: if we started updates flowing again, what would dgilmore compose the ec2 images from? 16:19:59 THIN AIR 16:20:01 point taken 16:20:07 that sounds a little hacky and aren't pre-releases configured to use updates, even though its empty? 16:20:07 brunowolff: How difficult would that be to impliment? 16:20:19 I am not sure. 16:20:27 tflink: that would be my concern - it's something we could change, but it involves several moving parts. 16:20:34 what's the cutoff point for when we just say "sorry charlie" ? 16:20:36 and has consequences up to release time, with the repo configuration question 16:20:45 rbergeron: that depends on how you feel about charlie. 16:20:54 Poor Charlie 16:21:03 he's gone off to the cloud ... 16:21:18 on to a "better" place :) 16:21:26 We also have to worry about PXE 16:21:37 Or is it finally booitng? 16:21:44 j_dulaney: for beta, no? 16:22:19 tflink: I think we skipped it for Alpha 16:22:25 Well, not skipped, per se 16:22:38 But, didn't require it to boot for Alpha 16:22:52 j_dulaney: it is booting, if you provide correct 'extra parameters', which is something i don't really like, but bcl tries to convince me that it's actually OK https://bugzilla.redhat.com/show_bug.cgi?id=787744 16:23:19 right, it's not broken. we can document that. 16:23:49 Okay 16:24:11 Still, a NTH to fix that would be great 16:24:43 i don't feel that strongly about charlie. charlie would be nice to have though. /me sighs 16:24:43 i think it already is fixed, just didn't make alpha. 16:25:22 adamw: PXE? 16:25:26 rbergeron: seriously, i dunno the answer to that. isn't it more, er, your department? with either your current hat or your previous one? :) 16:25:36 j_dulaney: the need for a kernel= parameter in certain boot types in general 16:25:46 i remember seeing some chat in #anaconda to the effect that it's fixed 16:26:49 adamw: Ah 16:27:03 ec2 shouldn't be a blocker. not when we don't have criteria, or testing beforehand 16:27:18 +1 16:27:35 that said: since we aren't discovering this until the time when we need to post it, we should maybe start considering actually doing a test-compose-to-upload-to-ec2 in the future 16:27:52 so that if that process is broken we don't find out ... in this meeting the day before release 16:28:06 rbergeron: i don't see it as something which should have a criterion - we don't have a 'criterion' that the live image should work, a 'criterion' that the dvd image should work, etc 16:28:07 Time to get fired from QA so I don't get fired from my paying job. See you next week. 16:28:18 the deliverables aren't specified in the criteria, we should have probably a releng sop for them 16:28:44 the criteria specify the functions that should work across all supported deliverables. but eh, i'm disappearing up my own process ass here, we can figure it out in post. 16:28:48 .fire brunowolff 16:28:48 adamw fires brunowolff 16:29:03 .fire brunowolff 16:29:03 adamw fires brunowolff 16:29:09 sorry late but here john 16:29:12 there is criteria that things should boot - but do we block if, say, xfce doesn't boot, but gnome does? 16:29:14 LOL 16:29:24 not currently. 16:29:32 gnome and kde are the blocking desktops 16:29:36 (i think, talking out my ass while i'm on the phone in a meeting) 16:30:16 multitasking much? 16:30:29 rbergeron: the criteria use the phrase 'supported desktops', and there's a little bit in the preamble which states what those currently are by policy. 16:30:30 FWIW why should kde get special status over XFCE? 16:30:33 (which is KDE and GNOME) 16:30:35 right. so we could block final if ec2 doesn't boot, but ... not alpha? /me is just brainstorming, but i think we just need a decision here and i i think it's just "sorry charlie, no alpha" 16:30:45 me can see gnome, since it is default, butn ot kde 16:31:01 nb: would you like to hold pandora's box so you can peer into it as deeply as possible? 16:31:02 nb: it always has and so it continues to. it just is considered to be supported while the others aren't. that can always change, but the decision wouldn't come from us. 16:31:13 nb: Do we block on Fluxbox? 16:31:29 nb: historical reasons. 16:31:48 nb: If you want to change that, poke the Board 16:31:55 ok 16:32:05 dgilmore: can we not back out changes to last known working appliance-tools, rebuild it, and try that? 16:33:41 anyway, it seems like the takeaway here is clearly that we're lacking policy/process for deliverables: what they are, and how hard we try to deliver the ones that aren't required at any point, when we stop trying, etc 16:33:56 so we need to renew that ticket, wherever it is, and get that done 16:34:10 #action adamw to dig out the 'deliverables' ticket / action item and get it moving again 16:34:21 How much of that is FeSCO, how much releng, and how much us? 16:34:30 hand wavey! 16:34:47 i think it's one of those things where it's better to ask for forgiveness than permission. 16:34:53 Does that mean I can wave my hands and make it go awaY? 16:35:33 if only. 16:35:48 i think we'd best move on and keep discussing this elsewhere, it's getting a bit freeform 16:35:59 #topic Upcoming QA events 16:36:41 we get back into blocker reviews this week, so everyone set aside your friday... 16:36:52 Yay ... 16:37:05 wheee! 16:37:09 What is todays date? 16:37:10 we also have 'Pre-Beta Acceptance Test Plan' on the schedule for two days from now, which seems a) early and b) redundant since rats is now firing daily 16:37:16 02-27 16:37:46 First test day is a week from Thursday 16:38:00 yup, indeed 16:38:19 In fact 16:38:22 okay, so it seems like when we got the schedule modified to bump TC1 earlier, 'acceptance test plan' got moved a week earlier instead of being removed 16:38:38 rbergeron: the idea was to drop the 'acceptance test plan' points entirely (replace them with TCs), not bump them a week forward 16:38:43 #info First test day is a week from Thursday; it is 03/07 16:40:44 alrighty, so yeah, blocker review this friday, first TC next week, first test day also next week. 16:41:04 i think that's all 16:41:08 #topic AutoQA update 16:41:10 #chair tflink 16:41:10 Current chairs: adamw j_dulaney jskladan tflink 16:41:19 #chair kparal 16:41:19 Current chairs: adamw j_dulaney jskladan kparal tflink 16:41:25 I have some small update 16:41:27 take it away, folks. just remember to bring it back before the due date 16:41:53 first of all I'd like to remind everyone that we're now testing anaconda installation automatically every day 16:42:03 link is here: http://autoqa-stg.fedoraproject.org/resultsdb/frontend/search?type=Testcase&terms=rats_install 16:42:23 there were some complaints about log messages, so I tried to improve that 16:42:56 at the end of the result log you can now see last 10 lines parsed from serial console output: http://autoqa-stg.fedoraproject.org/results/27117-autotest/qa06.qa.fedoraproject.org/rats_install/results/f17-i386.html 16:43:33 and someone asked last time whether we can add 'newlines' to the following log: http://autoqa-stg.fedoraproject.org/results/27117-autotest/qa06.qa.fedoraproject.org/rats_install/results/stage2.log 16:43:37 Might be a useful feature, that 16:43:44 yeah, that'd be good. 16:43:47 hi 16:43:51 in short: we can't, because newt is drawing on serial console using escape characters 16:44:06 so at least I filtered it using 'strings' command: http://autoqa-stg.fedoraproject.org/results/27117-autotest/qa06.qa.fedoraproject.org/rats_install/results/stage2.log_filtered 16:44:22 so now we should be able to debug potential problems quicker 16:45:10 I m Rejaul, Fedora Ambassador Bangldesh 16:45:21 #info rats_install output has been improved 16:45:38 that's all I have for today 16:45:50 i want to become a mentor of APAC Bangldesh 16:46:01 kparal: BTW, I was the one asking for newlines 16:46:09 irejaul: can you please ask in the correct channel? we're in the middle of a QA meeting...sorry 16:46:10 irejaul: I think you might have the wrong channel or time 16:46:15 kparal: Much more readable 16:46:19 kparal: Thanks 16:49:33 tflink: anything to add for autoqa? 16:49:51 adamw: nope 16:50:09 kparal: 16:50:18 adamw: nope, that's all 16:50:32 Instead of replacing the author name in tests, just add a maintainer line 16:50:33 okely dokely 16:50:43 #topic open floor 16:50:48 Have both author and maintainer 16:50:56 i hope everyone enjoyed this exciting and enthralling meeting 16:51:06 now you can make it even better with your pearls of wisdom! 16:51:26 adamw: We have wisdom? 16:51:32 * j_dulaney did not know of this 16:52:08 j_dulaney: the author credits are still available in all the source files 16:52:18 kparal: True 16:52:59 kparal: where is the contact info used, anyways? 16:53:44 nowhere. it's for our needs only 16:53:57 let's discuss in #fedora-qa 16:54:02 works for me 16:54:35 .fire himself 16:54:35 adamw fires himself 16:55:42 :) 16:55:57 hrm, he seems to have disappeared 16:55:59 holiday! 16:57:20 * j_dulaney wants to go back to the house, stir up the fire place (which has been going for two days now), sit in front of it and watch anime 16:58:17 Alas, I've class this afternoon 16:58:21 j_dulaney: come on, you have fireplace, and you're going to watch dragon ball? :) 16:59:12 ok, I'll do what I wanted to do for a long time now :)) 16:59:15 #endmeeting