15:01:42 #startmeeting Fedora QA meeting 15:01:42 Meeting started Mon Aug 29 15:01:42 2022 UTC. 15:01:42 This meeting is logged and archived in a public location. 15:01:42 The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:01:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:42 The meeting name has been set to 'fedora_qa_meeting' 15:01:46 #meetingname fedora-qa 15:01:46 The meeting name has been set to 'fedora-qa' 15:01:53 #topic Roll Call 15:01:56 morning folks 15:02:00 afternoon 15:02:04 * SumantroMukherje is here 15:02:11 * bittin- is also here 15:02:16 morning adamw! 15:02:35 morning 15:03:16 * coremodule is here 15:03:21 good morning! 15:03:49 how's everyone doing? 15:04:04 * bittin- is alright 15:05:54 good good 15:06:02 #topic Previous meeting follow-up 15:06:32 "coremodule to remove 32-bit arm columns from validation matrix templates" - how's that going? 15:06:41 done! 15:07:21 yay 15:07:31 my favorite kind of follow-up 15:07:40 #info "coremodule to remove 32-bit arm columns from validation matrix templates" - this is done 15:07:49 if you see any stray 32-bit arm stuff in validation test pages, yell 15:07:54 any other follow-up anyone? 15:10:12 alrighty then 15:10:36 oh hmm 15:10:40 oh yes tim's here good 15:10:43 #topic Kiwi TCMS evaluation results 15:10:46 #chair tflink 15:10:46 Current chairs: adamw tflink 15:10:49 take it away, tflink 15:11:42 I do recognize some irony here but do we want to do this topic this week? I know kparal is out and AFAIK, he's the only other person who tried out the Kiwi demo instance 15:11:46 .hello geraldosimiao 15:11:47 geraldosimiao: geraldosimiao 'Geraldo S. SimiĆ£o Kutz' 15:12:34 tflink: i'm easy... 15:13:14 tflink[m], I *did* help with your setup tflink[m], not that I have much input here, but take that for what it's worth 15:14:14 I don't think that the outcome of the conversation is going to be different next week, anyways 15:14:20 #link https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/message/HSNAKQHR2TBQFYJAEMD4SWATJFA4WHT6/ 15:14:37 oops i'm actually here 15:14:56 so, there has been some discussion around test case management and potentially moving away from using the wiki for test cases and results 15:15:21 cmurf: hi 15:15:40 adamw hi 15:15:48 is that also for test days if that happends? *curious* 15:16:13 as KiwiTCMS is the only maintained open source option for test case management, I set up a demo instance to see if kiwi was a good choice for Fedora QA 15:16:41 bittin-: yeah, that would change as well 15:16:48 or at least that was part of the idea 15:16:55 ah thanks, i will let you go on 15:18:18 kparal set a long summary to test@ about his thoughts after poking around with the demo and it seems like his thoughts on the matter mostly match mine 15:19:04 which is: There's nothing horribly wrong with Kiwi as a TCMS but its implementation details make it a not very good choice for Fedora 15:19:45 we could switch over to using it but the cost of porting everything, changing all of our documentation and teaching all the new ways of doing things would be very expensive 15:20:50 yeah, that was my take on yours and kparal's takes 15:20:53 so, if we don't switch to Kiwi, that leaves us with two options that I'm aware of: keep using the wiki or write something from scratch 15:21:03 sorry i never got around to playing with it myself, but it sounds a whole lot like my experience with moztrap 15:21:53 both have good and bad things - as much of an odd use case as it is, the wiki works for us for the most part and doesn't require much in the way of upkeep 15:22:09 same haven't had time to test it myself, but i will use whatever the Fedora community decides to use 15:22:56 writing something from scratch would certainly cover all the things we do that are less common and integrate nicely with existing Fedora systems but it'd take time to create and maintenance once it's created 15:23:09 would that time be better spent doing something else? 15:23:45 that's the primary question that I wanted to ask here - where do we go or at least look at going from here? 15:25:23 so we have several newer contributors here 15:25:42 how painful do you folks find it to report results in the wiki? is it a real pain or just a little thing you got used to? 15:25:48 The primary concern raised in the test@ thread was about the usability of the test matrices and how easy it is to break them if you're not used to them already 15:26:37 the Wiki works for me, i am not the best with Wiki syntax however, but can always copy the person before only done so like 2-3 times, mostly used the testweeks. app 15:28:01 oh, yeah, we do also have the option of kinda extending the testdays webapp to cover validation too. dunno how sane that'd be. 15:28:29 off the top of my head, its requirement to create metadata pages would be a stumbling block. but we could...i dunno. mmm. 15:29:06 adamw, multi arch same test case on metapage is weird :) 15:29:16 yeah 15:29:25 we'd have to do quite a bit of extending... 15:29:36 at that point, I'd almost rather have a dedicated frontend - using wiki pages as a database seems like a very odd way of doing things, especially if folks can edit the wiki page and whatever frontend we're using 15:29:50 dedicated frontend and database backend, rather 15:30:22 unless tweaking testdays and/or the wiki layout would be easier and less problematic than I think it would be 15:31:47 "how painful do you folks find it..." <- I use relval to fill the release validation wiki. Simple and straightforward. 15:32:38 yay, i like good reviews 15:33:02 another interesting (but potentially problematic) question is that if the current wiki-based setup is intimidating new users, would we ever hear about it? 15:33:06 geraldosimiao: need to look into that 15:33:20 problematic in that it promotes wild speculation 15:33:38 tflink: i'm hoping we'd hear from folks joining up then telling us 'oh god this wiki thing is terrible' before they leave. but of course, hard to prove. 15:34:19 bittin-: relval is a dumb little CLI client for the wiki stuff that i wrote. `relval report-results` walks you through reporting validation results and does the wiki editing for you so you can't mess it up. 15:34:55 adamw: geraldosimiao: cool did not know about that, need to look at that next time thanks for the tip/info :) 15:35:00 tbh, I like wiki and how easy it is to onboard people with relval . Thats my take on wiki at least. 15:35:27 in the end it boils down to 'is writing a new thing from scratch the best use we can think of for the dev hours', i guess 15:35:28 wrote a reminder for myself 15:35:45 adamw: pretty much, yeah 15:35:53 for myself i can think of at least five things i'd put a higher value on the time for, but i dunno about anyone else 15:36:02 and it sounds like the consensus here is pretty much: probably not 15:36:16 .hi 15:36:17 TheExorcist[m]: Sorry, but user 'TheExorcist [m]' does not exist 15:36:34 .hi naraiank 15:36:35 TheExorcist[m]: Sorry, but user 'TheExorcist [m]' does not exist 15:36:46 the wiki has it's issues and quirks but it does pretty much everything we need it to do and any replacement would also have issues and quirks 15:36:48 it's ok, we know who you are :D 15:37:01 .hello 15:37:01 TheExorcist[m]: (hello ) -- Alias for "hellomynameis $1". 15:37:08 .hello2 tflink 15:37:09 tflink[m]: Sorry, but user 'tflink [m]' does not exist 15:37:17 that's probably what you're looking for 15:37:35 never mind 15:37:46 i think you need .hello if you need to put in the username manually 15:37:54 .hello2 uses your nick 15:38:05 .hello sumantrom 15:38:05 ...or something 15:38:05 I had it backwards, whoops 15:38:06 SumantroMukherje: sumantrom 'Sumantro Mukherjee' 15:38:54 anyhow, are there any dissenting opinions on replacing the wiki as a TCMS? 15:39:45 the wiki works for me at this time. 15:39:58 proposed #agreed the wiki may not be perfect but it is likely better than the alternatives of moving everything over to kiwi or writing our own TCMS from scratch 15:40:23 tflink[m]: May be it needs to be forwarded to Council, I guess. Correct me, if I'm wrong. 15:41:00 The Exorcist: I suspect that the council would defer to our judgement here 15:41:20 Yeah, if it went to the Council, my first question would be "why are you asking us?" 15:41:41 yeah, this is more of an our team thing 15:43:02 off topic: Is it intentional that kiwi is an anagram for wiki? 15:43:32 I suspect so 15:43:46 sorry, I misread 15:43:53 I suspect it's a coincidence 15:45:34 OK, it sounds like the people here are pretty much in agreement 15:45:59 #agreed the wiki may not be perfect but it is likely better than the alternatives of moving everything over to kiwi or writing our own TCMS from scratch 15:46:03 yup 15:46:10 thanks for the work on the testing, tflink 15:46:15 I'll send out a conclusion to the thread on test@ 15:46:21 :) +1 15:46:28 +1 tflink[m] 15:46:34 .cookie tflink[m] 15:46:37 .cookie tflink 15:47:00 tflink++ 15:47:06 tflink++ 15:47:12 ah i forgot how you did it 15:47:27 so on to some status then? 15:48:20 #topic Fedora 37 check-in 15:48:28 so, afaik, status of f37 is 'mostly working' 15:49:06 Workstation works in my testing VM in Virtualbox and new composes are rolling, but there might be some bugs but i guess we are talking about those in the Blocker bugs meeting later today 15:49:22 coremodule: oh hmm, the Base validation page still has a "Release-blocking environments (armhfp)" section? 15:49:36 were there any updates released for F37 PR testing? Did I messed them? 15:49:38 oh, you changed it since we last created an event 15:49:52 s/messed/missed/ 15:50:13 TheExorcist[m]: https://openqa.fedoraproject.org/nightlies.html 15:50:35 was two sets of updates just today 15:51:13 seems some IoT 37 composes is broken otherwise rest seem to work 15:52:00 we fixed that today 15:52:06 great :) 15:52:11 there's still an outstanding bug with greenboot though 15:52:22 oh ok 15:53:20 #info bugs in greenboot for Fedora IoT 37 15:53:29 adamw: I must redo download and iso check for the workstation build because 20220826 build didn't worked at pendrive usb live session 15:53:49 Strange because same uso worked at vm 15:53:56 geraldosimiao: if previous ones were ok, it's probably a glitch, off the top of my head i don't think anything relevant should have changed... 15:54:01 s/uso/iso/ 15:54:42 adamw: Yeah, must be 15:54:42 bittin-: Keep the updates posted in #quality:fedoraproject.org 15:54:55 now we're in freeze it would be good if folks can run the basic and beta validation tests and find any bugs now, so we have plenty of time to fix them 15:55:08 TheExorcist[m]: don't have the time there is new images 1-3 times per day 15:55:14 looks like the usual suspects that haven't been done yet - cloud testing on real clouds, the printing test case, stuff like that 15:55:29 just sign up to the testing-reports and testing mailinglists TheExorcist[m] 15:55:46 #info it'd be great if folks can run the missing Basic and Beta validation tests for the current candidate compose so we can catch any blocker bugs with plenty of time to fix them 15:55:54 i'll also send out an email about that 15:56:00 I would like to schedule a Beta Validation Week .. when do we start? 15:56:19 SumantroMukherje: the week after Beta drops maybe? 15:56:45 Sumantro Mukherjee: do you mean pre-Beta testing, or post-Beta testing? 15:56:54 if you mean pre-Beta testing, next week would be great :D 15:57:02 pre-beta, i suppose! 15:57:12 post beta will be pre-final :D 15:57:23 next week is also the i18n and GNOME 43 RC test weeks 15:57:41 so next week, we will be running "validation events" for the first time :D 15:57:54 a lot of testing next week 15:58:02 hmm 15:58:14 then this week would've been great, but i guess it's short notice :D 15:58:20 the target release date is 13th sept 15:58:26 so we can't really leave it later than next week 15:58:38 let's switch topics while we still have two minutes 15:58:46 #topic Test Day / community event status 15:58:48 I18n Test Week is coming up on 5th Sept through the end of the week.https://testdays.fedoraproject.org/events/139. CryptoPolicy test day is also going to be on 5th Sept. IoT and Gnome Final to decide the dates. I will push in Gnome Apps, toolbx , virt, FCOS and podman somewhere in next come of weeks, before Fedora 37 upgrade test day. 15:58:50 any really quick news/announcements, sumantro?> 15:59:01 haha, you're ahead of me 15:59:15 GNOME 43 RC Test week starts 7th September and goes on until 14th September 15:59:17 #info i18n Test Week is coming up on 5th Sept through the end of the week: https://testdays.fedoraproject.org/events/139 15:59:26 #info CryptoPolicy test day is also going to be on 5th Sept. 15:59:43 #info others are pending date decisions 16:00:25 so adamw, should we start the beta validation from 31st itself? 16:00:48 sure, that'd be great if folks are readu 16:00:51 ready* 16:00:57 starting up the blocker bug review meeting now 16:01:11 works for me 16:01:17 I will write some doc and set things up! 16:02:38 f37 blocker review meeting starting now over in #blocker-review:fedoraproject.org 16:03:14 awesome, thanks sumantro 16:03:27 #info late notice Beta validation test week starting on August 31st 16:03:27 np adamw! 16:03:28 #topic Open floor 16:03:34 anyone got anything else burningly urgent? 16:03:36 * bittin- have nothing 16:05:12 alrighty, thanks for coming everyone 16:05:31 * bittin- heads to the blocker review meeting 16:05:44 #endmeeting