15:00:20 #startmeeting Fedora QA meeting 15:00:20 Meeting started Mon Jul 25 15:00:20 2022 UTC. 15:00:20 This meeting is logged and archived in a public location. 15:00:20 The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:20 The meeting name has been set to 'fedora_qa_meeting' 15:00:23 #meetingname fedora-qa 15:00:23 The meeting name has been set to 'fedora-qa' 15:00:28 #topic Roll Call 15:00:35 morning folks, who's around for qa meeting fun? 15:00:45 .hello geraldosimiao 15:00:46 geraldosimiao: Something blew up, please try again 15:00:49 geraldosimiao: An error has occurred and has been logged. Please contact this bot's administrator for more information. 15:00:58 I'm here 15:01:09 .hello2 15:01:10 bcotton: Something blew up, please try again 15:01:13 bcotton: An error has occurred and has been logged. Please contact this bot's administrator for more information. 15:01:21 no. 15:01:26 Zod is angry, must call superman 15:02:25 * kparal is here 15:03:13 morning 15:03:20 naraiank is here.. 15:04:19 ahoyhoy everyone 15:06:16 might be a quick one today, let's see! 15:06:19 #topic Previous meeting follow-up 15:07:39 "coremodule to remove 32-bit arm columns from validation matrix templates" - coremodule , around? did you do that? 15:09:04 well, let's see here 15:09:38 it doesn't look like it, so we'll put it back on for next time 15:09:54 #info "coremodule to remove 32-bit arm columns from validation matrix templates" - this isn't done yet, we'll check in again next time 15:09:59 #action coremodule to remove 32-bit arm columns from validation matrix templates 15:10:48 #info "adamw to implement the latest draft of the proposed networking criteria" - this is done: https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria&diff=650015&oldid=611584 15:11:13 so we have a ready-made criterion for future networking issues. now the question arises whether to add specific test cases for everything covered 15:11:17 #action adamw to consider adding test cases for new networking criterion 15:12:15 any other followup? 15:13:34 alrighty 15:13:38 #topic Fedora 37 check-in 15:13:56 nirik: ahoy! what's the mass rebuild status? 15:14:12 it's being tagged in right now. ;) 15:15:32 well, that'll be fun ;) 15:16:45 #info Rawhide has been relatively stable for the last few days, even with GNOME 43-alpha merged. The mass rebuild has been done and is currently being tagged in, we will see its effects in the next compose 15:16:59 assuming the tagging will be done by tonight nirik? 15:17:32 oh yeah, I'll fire another rawhide after it finishes too. 15:17:45 rgr 15:17:56 anyone hit anything interesting with gnome 43? 15:19:43 * cmurf lost track of time 15:19:45 i'm here 15:20:20 nirik: Superman is here..!geraldosimiao 15:20:29 ahoy, cmurf 15:20:35 the time is right over there, behind the couch 15:20:44 :P 15:20:59 yep i found the time 15:21:50 so one thing from last week's workstation WG meeting, and GNOME 43, and QA is this notion upstream isn't exactly certain of the exact tarball release and getting it build into Fedora 15:22:28 it's a range of a few days i guess? so the question is about having a 2 week tentative range for a GNOME test week 15:22:40 i mean sure, no reason we can't do that, really 15:22:46 and then pick week A or B once the release is imminently ready 15:22:53 the earlier the date can be firmed up the better for attendance, i guess 15:23:14 because there's so much churn right after the tarballs are done, that they'd like to do a Fedora test week ASAP after there's builds in koji 15:23:38 even a couple weeks delay makes the test week less useful 15:25:06 maybe kalev is around and can confirm/deny my understanding of the idea 15:25:55 well, as i said, it ought to be possible. would just need to be figured out on the ticket for the test day 15:26:12 we'd probably want to send an initial announcement with the date range, explaining the issue, and then a later announcement with the chosen date 15:26:13 anyway it would mean a test week for GNOME beta and another week for RC, each with a two week "A week" and "B week" that would basically get picked at the last minute once availability is known 15:26:20 yep perfect 15:28:11 alright, yeah, we can do that. if the tickets aren't getting enough attention go ahead and ping me and i'll jump in 15:28:23 great 15:29:23 anything else rawhide-adjacent folks? 15:31:52 #topic Test Day / community event status 15:31:56 sumantro: around? 15:34:44 nope, okay. well, it looks like we have a couple of test day tickets for Toolbox and virt-manager, dates aren't picked yet. 15:35:19 We had many calls in Fedora General support group, about issues related to Display drivers. can anybody take this call to include as many supported drivers in builds? 15:36:01 The Exorcist: we already include all relevant F/OSS drivers, I believe. fedora does not and will not include non-free drivers by default, that's been established for a long time 15:36:20 or were you thinking of something else? 15:36:38 #action adamw to check in with sumantro on test day planning 15:37:06 Yes, some body was reminding, now we have open-sourced nvidia drivers from xorg. 15:38:01 mesa drivers have some problems in adopting few hardwares.. 15:38:43 yep that's going to take some time to shake out as i understand it 15:38:49 yeah 15:39:00 the open source nvidia drop is not fully complete 15:39:03 there isn't really a functioning open source graphics driver yet 15:39:14 https://blogs.gnome.org/uraeus/2022/05/11/why-is-the-open-source-driver-release-from-nvidia-so-important-for-linux/ is a blog post written by one of our RH folks which explains the situation 15:39:26 "There is code in there to support display, but it is not complete or fully tested yet. Also this is only the kernel part, a big part of a modern graphics driver are to be found in the firmware and userspace components and those are still closed source." 15:39:53 so it's big news, but it's not a thing we can usefully put in fedora right now for people to see pictures with :D 15:40:20 yeah it's a big step forward but we're still somewhere in the middle of the river :P 15:41:44 #topic Open floor 15:41:47 alright, any other business folks? 15:42:01 time to mention test-reports? 15:42:21 I failed to make a proper announcement yet 15:42:29 oh yes, good idea 15:42:55 also a reminder about the TCMS conversation. The demo instance is still up and the plan is to make a decision during the QA meeting next week 15:43:14 there is a new mailing list "test-reports", which will consolidate all those compose/update/test mass reports which were previously sent to test+devel lists. Feel free to subscribe if you're interested: 15:43:14 https://lists.fedoraproject.org/archives/list/test-reports@lists.fedoraproject.org/ 15:45:30 And another one: The Exorcist: is helping us for a few days now. We need a sponsor for him to join QA group at the account system. 15:45:59 i can do that 15:46:00 Username: naraiank 15:46:29 oh, it looks like sumantro already did 15:46:46 Ok, thanks 👍 15:48:40 #info regular report emails like the compose reports and compose-check reports have been moved to a new list, test-reports@lists.fedoraproject.org , sign up for that list if you want to continue receiving those mails 15:49:10 #info the Kiwi TCMS demo instance is up for another week, we will make a decision whether to move forward with it next week 15:50:27 alrighty, looks like that's about all? 15:50:49 Soo it seems 15:50:57 thanks for coming, everyone! 15:51:42 Alright. Goodbye friends 😁 15:52:19 #endmeeting