15:00:06 <adamw> #startmeeting Fedora QA meeting
15:00:06 <zodbot> Meeting started Mon Jun  6 15:00:06 2016 UTC.  The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:06 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:06 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:00:13 <adamw> #meetingname fedora-qa
15:00:14 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:20 <adamw> #topic Roll call
15:00:25 <adamw> ahoyhoy folks, who's here for QA meeting times?
15:00:44 <sumantro> \me is here
15:00:44 <coremodule> Morning!
15:00:48 * coremodule is here.
15:00:51 * garretraziel is here
15:01:02 <sumantro> I am here @adamw!
15:01:30 <adamw> hi sumantro, coremodule, garret
15:03:09 <sumantro> hey adam! :D
15:03:26 * adamw wonders where all the grizzled veterans are
15:03:33 <adamw> too busy with their morning whisky i guess
15:03:48 * pschindl is here
15:04:11 <garretraziel> for CEST folks around here it
15:04:22 <garretraziel> it's whiskey at 5 o'clock
15:04:35 <garretraziel> and that's bearable :-)
15:04:55 <garretraziel> it's like tea at 5, but better
15:05:04 <adamw> bearable? it's at least 8 hours too late!
15:05:31 <adamw> roshi: tflink: kparal: ahoy? can you see us through the bottoms of your glasses?
15:06:18 <adamw> ah well, guess we'll start rolling and see if anyone else drops by later
15:06:21 <kparal> adamw: morning
15:06:25 <adamw> ah, there's one
15:06:35 <kparal> we're still closing up the qa-devel meeting
15:06:53 <adamw> you mean the bit where you all do shots at the end? :P
15:07:01 <kparal> that's the one
15:07:03 <adamw> =)
15:07:08 <adamw> #topic Previous meeting follow-up
15:07:09 * brunowolff will try to keep an eye on the meeting
15:08:09 <adamw> #info "adamw to sync with desktop team and FESCo on graphical upgrade feature release planning" - this is still kinda in progress, it seems. latest is that fesco wants me and kparal to come up with a list of 'release blocking' bugs for graphical upgrades which they can use to decide when to release it
15:08:19 <tflink> adamw: sorry, qa-devel meeting is going long
15:08:31 <adamw> #action adamw and kparal to come up with list of 'blocking' bugs for graphical system upgrade
15:08:43 <adamw> aaand that's all the action items, any other follow-up from last time?
15:08:50 * kparal spent today re-testing gnome-software
15:10:20 <adamw> kparal: awesome...i'll message or mail you after the meeting to sync up on that
15:10:36 <kparal> ok
15:10:58 <adamw> #topic Fedora 24 status and test planning
15:11:15 <adamw> #info Go/No-Go meeting is this Thursday (2016-06-09)
15:11:29 <adamw> so that's the big date we're working with. :) that means we'd like to have the RC today or tomorrow
15:12:05 <adamw> we are still waiting on the grub2 blocker bug before we can build an RC, I will sync with pjones on that today
15:12:20 <adamw> #action adamw to sync with pjones on grub2 blocker and try to get an RC built ASAP
15:13:45 <adamw> the other concerning thing is we do still have some validation tests that have not been run at all or for quite a long time
15:13:56 <kparal> the RC request is waiting for grub2?
15:14:07 <kparal> I noticed it was created a week ago, but no RC
15:14:08 <adamw> kparal: yep
15:14:37 <adamw> kparal: ah, the compose request i filed was for a non-RC (what we used to call a TC)
15:14:50 <adamw> but dgilmore said we can't do that for tedious pungi reasons
15:14:59 <adamw> basically for final we can only do RCs apparently.
15:15:27 <kparal> ok
15:16:34 <adamw> so one thing we definitely should sort out: we need to run https://fedoraproject.org/wiki/QA:Testcase_install_to_FCoE_target
15:16:45 <adamw> does anyone have the necessary setup for that?
15:17:03 <tflink> don't we run into this pretty much every release?
15:17:11 <adamw> ...yeah, now you mention it
15:17:28 <adamw> hasn't been run since at least f20.
15:17:36 <adamw> we should probably fix that...:P
15:18:11 <adamw> anyone want to take the job of figuring out how to get that run, or should I do it?
15:18:28 <coremodule> I have no FCoE hardware...
15:19:05 <adamw> i'm kinda poking around now to figure out if it's possible to do it without dedicated hardware
15:19:10 <sumantro> same here as core module
15:19:21 <adamw> wikipedia says "FCoE encapsulation can be done in software with a conventional Ethernet network interface card"...
15:19:58 <tflink> IIRC it requires a dedicated physical network, doesn't it
15:20:13 <tflink> ie, it can't co-exist with tcp/ip traffic on the same ethernet system
15:20:31 <tflink> which is the big difference between iscsi and fcoe, IIRC
15:20:51 <tflink> iscsi is on top of tcp/ip, fcoe is in place of tcp/ip
15:20:51 <adamw> i dunno, i'm going in blind
15:21:27 <adamw> welp, looks like it's my job
15:21:33 <cmurf> well if two people do it at the same time...
15:21:36 <adamw> #action adamw to try and figure out a way to get the FCoE test run
15:21:49 <cmurf> they may be running into the various brick walls at slightly different times
15:22:00 <coremodule> adamw, Do you have dedicated FCoE hardware or are going to software-emulate it?
15:22:00 <cmurf> and it ends up going faste
15:22:02 <cmurf> r
15:22:37 <cmurf> FCoE is software emulated that's the point, rather than having to buy fibre channel hardware
15:22:40 <adamw> coremodule: i'm going to see if i can find someone who already knows about FCoE to do it. failing that i guess i get to try and do it in openqa. :P
15:23:23 <adamw> alrighty, so aside from that I guess the other slightly tricky one is dualboot_with_OSX
15:23:29 <adamw> cmurf, have you looked at that lately?
15:23:49 <cmurf> that has been working the whole time so if it's busted since beta i'd be surprised
15:23:53 <cmurf> not since beta
15:24:00 <cmurf> I know that it boots
15:24:27 <cmurf> and but does it still install into free space? almost certainly but unknown
15:24:37 <adamw> if you could check it that'd be awesome
15:24:43 <cmurf> yeah i'm going to check today
15:24:48 <adamw> thanks a bunch man
15:24:51 <cmurf> 20160531.n.0
15:24:56 <adamw> yup
15:25:00 <cmurf> it's already on a stick
15:25:34 <adamw> let's see, so another thing we need is to test the current blocker fixes
15:26:02 <adamw> i sent out https://bodhi.fedoraproject.org/updates/FEDORA-2016-714119426f for the cloud partition resize bug; kushal / coremodule, could you test it?
15:26:17 <coremodule> adamw, No problemo!
15:26:18 <adamw> not sure if you'd need to build new images to test it, though...
15:26:44 <kushal> adamw, I think we have to
15:27:13 <adamw> do you know how to do that? :)
15:27:33 <adamw> kushal: btw it'd be good if autocloud tested this too, i guess
15:27:48 <kushal> adamw, Yes, we will have to add a test, and enable it after the freeze.
15:28:04 <coremodule> adamw, No, not without asking some questions. I'll ping you after the meeting.
15:28:23 <adamw> well i'll do my best but i don't really know either :P kushal, do you know?
15:28:59 <kushal> coremodule, this should do http://worknotes.readthedocs.io/en/latest/cloudimages.html#imagefactory
15:29:10 <adamw> the other blocker-fixing update that needs testing, btw, is https://bodhi.fedoraproject.org/updates/FEDORA-2016-5714267e09 - i think it should be possible to test that outside of anaconda, at least make sure it generally works
15:29:16 <adamw> kushal: thanks
15:29:17 <coremodule> kushal, Thanks!
15:29:49 <kushal> adamw, just now reached Raleigh after the long pycon, body/mind are still not in sync
15:30:12 <adamw> #action coremodule and kushal to try and test+karma https://admin.fedoraproject.org/updates/FEDORA-2016-714119426f
15:31:01 <adamw> looks like the desktop tests are getting filled out now
15:31:12 <adamw> however I am always suspicious when i see a 'pass' for https://fedoraproject.org/wiki/QA:Testcase_desktop_menus
15:31:16 <adamw> it makes me think you're not trying ;)
15:31:24 * adamw always has at least five 'warnings' when he runs that test...
15:31:42 <cmurf> ohoh
15:31:47 <cmurf> who filled it out pass?
15:31:49 <cmurf> noogie
15:31:54 <cmurf> GIVE HIM A NOOGIE
15:32:49 <adamw> coremodule and Wolnei Tomazelli seem to be the guilty parties
15:33:00 <coremodule> adamw, Hang on, I'm looking.
15:33:02 <adamw> .fire coremodule that can't possibly be working
15:33:02 <zodbot> adamw fires coremodule that can't possibly be working
15:33:07 <cmurf> haha
15:33:11 <cmurf> i saw it coming
15:33:13 * adamw is half-joking, don't worry :P
15:34:02 <coremodule> adamw, Only half joking? Well half is better than nothing at all!
15:34:09 <adamw> =)
15:34:32 <coremodule> adamw, I will say though, I ran those tests just like they said and found nothing out of the ordinary in the 20160531n0 release.
15:34:32 <adamw> i mean i always seem to find a few apps that are kinda wonky in some way, but i'm not seriously busting you for saying it's ok
15:34:59 <coremodule> Now on the 20160524n0 Xfce, I did find problems with Xfce4-screenshooter.
15:35:11 <coremodule> It did not take screenshots when the system menu was pulled down.
15:35:34 <adamw> oh, yeah, screenshot apps always seem to have issues like that...
15:35:38 <coremodule> https://bugzilla.redhat.com/show_bug.cgi?id=1340522
15:35:39 <adamw> using the timer usually gets around it
15:35:41 <adamw> aaaanyhoo
15:35:54 <adamw> thanks a lot for all the validation testing work, everyone
15:36:10 <adamw> and on a personal note sorry i haven't been helping out as much as usual, i've been trying to automate some of the more complex tests for future sanity's sake
15:37:10 <adamw> so i think we're pretty much lined up now? we've got blocker meeting in 25 minutes and then after that i'll be trying to get an RC built, then it's just the usual panic testing cycle till thursday. :P
15:37:16 <adamw> anything else on f24 stuff?
15:37:55 <coremodule> Any mission-critical tests that we should run before Thursday, other than the ones mentioned in this meeting?
15:38:52 <cmurf> it's looking pretty good all things considered ya?
15:39:35 <adamw> coremodule: ideally for the RC we want to re-run as many of the tests as possible for confirmation
15:39:52 <adamw> cmurf: eh, i'd say about the same as usual...we'll see when we get the RC
15:39:54 <cmurf> right, RC testing is marathon running
15:40:00 <adamw> especially if we don't manage to keep kparal away from it :P
15:40:11 <cmurf> he is a bug magnet
15:40:12 <adamw> pschindl, do you have the kparal isolation unit prepared?
15:40:20 <cmurf> vacation?
15:40:21 <garretraziel> we bought kparal Witcher 3 for wedding gift
15:40:29 <garretraziel> I think that we'll be OK :-)
15:40:40 <garretraziel> for several weeks that is
15:40:47 <cmurf> I have no idea what that... oh my
15:41:00 <adamw> ooooh, nice strategy. i like it.
15:41:11 * kparal hasn't slept in a way
15:41:13 <cmurf> there's a rabbit hole
15:41:17 <kparal> *in a week
15:41:35 <kparal> testing over day, playing over night
15:42:04 <cmurf> don't forget to bathe or your wedding could end abruptly
15:42:06 <cmurf> hah
15:42:45 <coremodule> Congratulations kparal!
15:42:56 <danofsatx> oh yeah, there's a meeting going on. sorry guys, contractors running around repairing the interior damage from the destroyed roof.
15:43:01 <kparal> thanks :)
15:43:12 <adamw> danofsatx: jeez, what'd you do to the roof
15:43:16 <danofsatx> oh, and congrats kparal
15:43:52 <danofsatx> I bought a house with a cheap shingle job, and the wind decided they were old enough to be replaced. They got blown off, and the rain ended up on the stairway inside.
15:44:01 <adamw> fun.
15:44:08 <adamw> alrighty, we do have one more topic before blocker meeting time...
15:44:27 <adamw> #topic Graphical system upgrade status
15:44:43 <adamw> so we kinda mentioned this in previous meeting follow-up, I guess, I just had it on the agenda as it seemed like an important topic
15:45:00 <adamw> kparal i guess you're closest to this one, what's your feeling? how much stuff is there still to fix before it's really releasable?
15:45:22 <kparal> there's an update pending here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-fad11727bf
15:45:24 <kparal> it fixes some bugs
15:45:30 <kparal> I just tested it, it works well
15:45:42 <kparal> there are a few more bugs reported at https://bugzilla.redhat.com/showdependencytree.cgi?id=1308538&hide_resolved=0
15:46:05 <kparal> the important ones seem to be:
15:46:13 <kparal> https://bugzilla.redhat.com/show_bug.cgi?id=1335463
15:46:42 <kparal> https://bugzilla.redhat.com/show_bug.cgi?id=1336530
15:47:12 <cmurf> i think the one that concerns me the most is the failed upgrades result in no notification (of the failure)
15:47:14 <kparal> all the other ones might be annoying, but probably not blocking
15:47:21 <kparal> the two linked might be blocking
15:47:38 <kparal> cmurf: yes, but at least it does not destroy anything
15:47:41 <cmurf> sure
15:47:50 <kparal> which is different from clicking on Cancel and then seeing the system upgrade
15:47:58 <kparal> (the first one linked)
15:48:02 <cmurf> oh ick
15:48:24 <adamw> just call it Microsoft Mode
15:48:27 <cmurf> haha
15:48:43 <kparal> right, it's the business standard nowadays
15:48:46 <adamw> ("Do you want to upgrade to Windows 10 now or in ten minutes? Please choose "YES" or "HECK YES")
15:48:55 <coremodule> lol
15:48:59 <cmurf> OK so i'd back 1335463 being a blocker, that's the cancel does not cancel but installs bug
15:49:16 <cmurf> hey gotta monotize those users
15:49:21 <kparal> and the second one, 1336530, is directly covered in criteria
15:49:36 <cmurf> right
15:49:53 <kparal> well, not fully directly
15:49:56 <adamw> alrighty
15:50:02 <kparal> it says the user packages should stay
15:50:03 <cmurf> i'd say "cancel" qualifies as basic functionality if you can't cancel...
15:50:10 <adamw> so basically it's nearly there but there's at least one or two not-ship-worthy bugs remaining
15:50:10 <kparal> in this case, they have to be removed due to deps
15:50:14 <kparal> but the user is not informed
15:50:26 <cmurf> that seems doable
15:50:36 <kparal> when we talked to fesco about system upgrade behavior in the past, they agreed it should be mentioned
15:51:00 <cmurf> and actually don't we need a different word sorta? this is not release blocking, but it's making gnome-software graphica upgrades "active" blocking.
15:51:00 <kparal> but it was part of a bigger proposal, so not fully explicitly agreed on this particular thing
15:51:29 <cmurf> ergo it only affects gnome-software
15:51:41 <kparal> adamw: yeah, I'd say there are about 2 issues to be fixed yet
15:51:47 <adamw> cmurf: this is going to be a kind of one-time thing
15:51:50 <kparal> the more the better, of course
15:52:04 <adamw> since it's about when we initially flip the switch to make graphical upgrades appear for regular users
15:52:07 <cmurf> it is a unique situation admittedly
15:52:38 <cmurf> which could happen anytime after GA once the tool is ready
15:52:46 <adamw> so i think we're just gonna handle it ad hoc for now. in future i'd expect it to get wired into the release process somehow.
15:52:56 <cmurf> but we want to give marketing and web folks a way to showcase it
15:53:30 <adamw> allllrighty
15:53:39 <adamw> blocker review in 6 minutes, so let's do a very quick...
15:53:41 <adamw> #topic Open floor
15:53:42 <adamw> any other business?
15:54:04 * cmurf runs to go make a coffee
15:57:41 <adamw> alrighty, guess that's that
15:57:44 <adamw> thanks for coming everyone
15:57:58 <adamw> blocker meeting in a couple of minutes in #fedora-blocker-review, see EVERYONE there...right? *looks meaningful*
15:58:26 <adamw> #endmeeting