15:00:45 <adamw> #startmeeting Fedora QA Meeting
15:00:45 <zodbot> Meeting started Mon Apr 13 15:00:45 2020 UTC.
15:00:45 <zodbot> This meeting is logged and archived in a public location.
15:00:45 <zodbot> The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:45 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
15:00:51 <adamw> #meetingname fedora-qa
15:00:51 <zodbot> The meeting name has been set to 'fedora-qa'
15:00:54 <adamw> #topic Roll call
15:00:56 <adamw> ahoyhoyhoy
15:00:58 <frantisekz> .hello2
15:00:59 <zodbot> frantisekz: frantisekz 'František Zatloukal' <fzatlouk@redhat.com>
15:01:00 <adamw> who's around for meeting fun?
15:01:00 <bcotton> .hello2
15:01:02 <zodbot> bcotton: bcotton 'Ben Cotton' <bcotton@redhat.com>
15:01:04 <adamw> apologies if it's a holiday for you
15:01:14 <adamw> and you want to be outside doing something els- oh.
15:03:10 <Southern_Gentlem> .hello
15:03:12 <zodbot> Southern_Gentlem: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
15:03:12 * coremodule is here
15:03:14 <lruzicka> .hello2
15:03:15 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
15:03:22 <Southern_Gentlem> .hello2
15:03:23 <zodbot> Southern_Gentlem: Sorry, but you don't exist
15:03:28 <Southern_Gentlem> .hello jbwillia
15:03:29 <zodbot> Southern_Gentlem: jbwillia 'Ben Williams' <vaioof@gmail.com>
15:03:32 <adamw> existence is overrated
15:05:01 <adamw> alrighty
15:05:05 <adamw> #topic Previous meeting follow-up
15:05:12 <adamw> #info we had zero action items last week
15:05:17 <adamw> (clearly a highly effective meeting!)
15:05:28 <coremodule> is that an approximation?
15:05:31 <adamw> anything anyone wanted to follow up on that wasn't an action item
15:05:33 <adamw> ?
15:05:42 <adamw> coremodule: well, "last week" is an approximation :0
15:06:16 <coremodule> im going to need to take a seat in my recliner, smoke my tobacco pipe, and reflect on that
15:06:32 <bcotton> coremodule++
15:07:00 <adamw> alrighty then, moving on
15:07:41 <adamw> #topic F32 Final status
15:07:46 <adamw> so, we are now frozen for final
15:08:10 <adamw> go/no-go is somehow thursday although we have had a grand total of like one working day in freeze
15:08:43 <adamw> i'm not aware of any huge showstoppers or process issues right now, we have blocker review at the top of the next hour
15:09:12 <adamw> #info we are frozen for Fedora 32 Final, go/no-go is Thursday, usual blocker process is in flow, we do not have any huge showstoppers at this point
15:09:32 <frantisekz> any bets on go/no-go?
15:09:43 <adamw> #info we are treating IoT (and CoreOS) as non-blocking for Fedora 32 at this point, as no clear plans were ever brought forward to do otherwise
15:09:56 <adamw> not really!
15:10:38 <lruzicka> I would like to ask, are we going to have an RC any time sooner than Thursday morning?
15:10:51 <frantisekz> depends lruzicka
15:11:04 <frantisekz> no one knows right now, I guess we can request TC right away
15:11:12 <lruzicka> it would help a lot
15:11:44 <Southern_Gentlem> depends if bug fixes have pushed
15:11:52 <adamw> i'm not planning to do it until after the blocker review meeting
15:12:00 <adamw> if we accept any blockers that are unfixed there we can't do an rc
15:12:12 <adamw> if we don't, we can request one
15:12:49 <frantisekz> or we can request TC now and accepted blockers later... (ignore this, just trolling adamw :) )
15:13:01 <frantisekz> *accept
15:13:09 <lruzicka> yeah, we will see about the blockers
15:14:27 <frantisekz> just went through some proposed blocker/fe updates, if folks can go ahead and test fixes/give karma in bodhi, it'd be awesome :)
15:14:47 <frantisekz> eg. https://bodhi.fedoraproject.org/updates/FEDORA-2020-856e17297c (gnome-weather) , https://bodhi.fedoraproject.org/updates/FEDORA-2020-3abcc8bb29 (zezere)
15:14:51 <adamw> ++
15:15:14 <adamw> #info please everyone check the blocker list and test all the updates linked there: https://qa.fedoraproject.org/blockerbugs/milestone/32/final/buglist
15:15:55 <adamw> pwhalen: ping?
15:15:55 <zodbot> adamw: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings
15:16:12 <frantisekz> .fire zodbot
15:16:12 <zodbot> adamw fires zodbot
15:17:40 * adamw looks at testcase_stats
15:17:59 <adamw> oh good, dashes in test names break testcase_stats
15:18:02 <adamw> well that's excelltn
15:19:00 <adamw> test coverage is looking fairly good, some ARM stuff isn't covered since beta
15:19:01 <frantisekz> adamw, I am planning to ramp up validation testing tomorrow, didn't have too much time for it yet
15:19:13 <adamw> firmware RAID and FCoE aren't covered since beta
15:19:16 <adamw> frantisekz: cool
15:19:31 <frantisekz> adamw, I am almost certain I did FW raid at least once since beta
15:19:43 <frantisekz> (passed)
15:19:56 <adamw> guess you didn't fill it in on the wiki :P
15:20:07 <adamw> #info test coverage is looking fairly good, just a few things haven't been tested since Beta
15:20:18 <adamw> anything else on f32?
15:25:19 <adamw> alrighty then
15:25:31 <adamw> #topic Suspend criterion proposal
15:25:49 <adamw> i think this is our only outstanding proposal right now (correct me if i'm wrong)
15:26:02 <adamw> it seems like people are generally in favour of the idea and we're only discussing the details?
15:26:54 <Southern_Gentlem> yes good idea but i see no way that this can be tested so we know it works
15:27:17 <adamw> well, it's like any other hardware-dependent thing really
15:27:38 <adamw> we rely on people to test it on what hardware they have to hand, and evaluate proposed blockers as they come up
15:27:48 <adamw> not much different from graphics or networking for e.g.
15:28:51 <lruzicka> I agree, this one will depend on a number of different hardware in the community.
15:29:51 <frantisekz> also, we should be careful with blocking on something that kernel folks can't test/fix... take their opinion into account
15:31:32 <adamw> true
15:32:47 <Southern_Gentlem> this is a nice to have and maybe schedule a test day for it in F33 but till them i dont think this should be a blocker
15:33:00 <Southern_Gentlem> them/then
15:33:16 <adamw> i mean, people suspend all the time
15:33:19 <adamw> you can't really use a laptop without it
15:33:28 <adamw> so i'm not sure we need a test day before deciding to block on it
15:33:51 <adamw> it'
15:33:58 <adamw> it's not like it's strange, uncharted new territory ;)
15:35:02 <Southern_Gentlem> but how many people would actually block the release other it
15:35:38 <lruzicka> I think we should be able to decide individually. If there is some massive problem with the majority of devices, we would probably want to block on that .... this gives us the criterion to do so.
15:35:39 <Southern_Gentlem> how easy is it to test with openqa
15:35:40 <cmurf> depends on the scope, both hardware affected and the cause of the bug
15:36:03 <adamw> we can't really test it in openqa
15:36:18 <lruzicka> On the other hand, if only individual machines do not suspend, we will probably not to block on that anyway (even in other cases with criteria defined already)
15:36:25 <adamw> well, i mean, maybe we could, but it would provide almost no value
15:36:30 <adamw> suspending a VM doesn't mean much
15:36:30 <cmurf> i've got a long singular experience working with upstream kernel developers on a kernel regression that they ultimately blamed on an ACPI bug (with a lot of kernel building to enable ACPI debugging stuff)
15:37:04 <cmurf> in the end, they said it must be an ACPI bug; and even though it was revealed by a kernel regression, they won't fix it
15:37:25 <cmurf> (and it also suspends on Windows ok)
15:37:42 <cmurf> anyway, it's tricky and will depend on the bug
15:39:54 <adamw> sure
15:40:05 <adamw> again, this is not very different from other physical hardware-dependent issues
15:40:12 <adamw> we have lots of experience with graphics bugs etc. at this point
15:41:14 <adamw> #info this proposal is still under discussion on the list, we noted that blocking on this will require subjective evaluations of proposed blockers, manual testing buy-in, and collaboration with kernel team on viability of fixing bugs
15:42:03 <bcotton> yeah, i think this is the kind of proposal that gives us permission to make subjective decisions, not that binds us to make a decision we don't like
15:42:08 <adamw> #topic Test Day / community event status
15:42:29 <adamw> sumantro: around?
15:42:38 <sumantro> adamw yep!
15:43:16 <sumantro> so the kernel test week is running however, the communishift is having downtime
15:43:46 <sumantro> and frantisekz migrated the testdayapp to his server and filed an infra request to map DNS
15:43:47 <frantisekz> (just noting that communishift is going to be offline till around 13th of May, I've redeployed testdays web app on my vps to keep it up during that period)
15:44:04 <adamw> #info kernel 5.6 test week is running now: https://fedoraproject.org/wiki/Test_Day:2020-04-13_Kernel_5.6_Test_Week
15:44:06 <frantisekz> it should be up now
15:44:16 <adamw> #info testdays app is running on a different server, apologies for any disruption, we are trying to make it seamless
15:44:18 <sumantro> which should be take sometime, but I am helping as many as I can on the test-day channel
15:44:48 <sumantro> frantisekz, its live
15:45:04 <frantisekz> amazing, let's hope it doesn't break :)
15:45:13 <sumantro> IoT test day to follow in 2020-04-15
15:45:41 <sumantro> http://fedoraproject.org/wiki/Test_Day:2020-04-15_Fedora_32_IoT_Edition
15:45:51 <adamw> #info IoT Test Day is this Wednesday, http://fedoraproject.org/wiki/Test_Day:2020-04-15_Fedora_32_IoT_Edition
15:47:00 <sumantro> I got caught up and will be working towards setting up an community onboarding call this week or early next week
15:47:32 <adamw> cool
15:47:44 <adamw> #info onboarding call coming this week or next week, watch out on the mailing list for details
15:49:07 <sumantro> thats all from my end
15:49:33 <adamw> thanks sumantro!
15:49:36 <adamw> #topic Open floor
15:49:38 <adamw> any other business, folks?
15:51:06 <sumantro> no adamw
15:51:18 <Southern_Gentlem> looks like we have time for pause for th cause before the next meeting
15:51:34 <adamw> indeed
15:52:57 <adamw> thanks for coming, everyone
15:52:59 <adamw> #endmeeting