16:06:41 <coremodule> #startmeeting Fedora ARM Working Group Meeting
16:06:41 <zodbot> Meeting started Tue Mar  7 16:06:41 2023 UTC.
16:06:41 <zodbot> This meeting is logged and archived in a public location.
16:06:41 <zodbot> The chair is coremodule. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:06:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:06:41 <zodbot> The meeting name has been set to 'fedora_arm_working_group_meeting'
16:06:41 <coremodule> #chair pwhalen pbrobinson jlinton coremodule
16:06:41 <zodbot> Current chairs: coremodule jlinton pbrobinson pwhalen
16:06:41 <coremodule> #topic roll call
16:06:53 <coremodule> #info jlinton, pwhalen, and jforbes are here
16:06:59 <coremodule> let's get started
16:07:09 <coremodule> also, bear with me as this is my time hosting the ARM meeting...
16:07:17 <coremodule> #topic 1) ==== Stable Releases ====
16:07:48 <coremodule> anything for stable releases?
16:08:17 <jforbes> nothing here
16:08:32 <coremodule> #info Nothing of note for stable releases.
16:08:34 <pwhalen> Not aware of any issues, but also not testing or on top of it
16:08:48 <coremodule> okay, thanks. let's move on.
16:08:49 <coremodule> #topic 2) ==== Kernel Status ====
16:09:09 <coremodule> #info kernel-6.2.2-300.fc38
16:09:10 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2164177
16:09:34 <jforbes> It is kernel test week.
16:10:08 <coremodule> #info Kernel test week is currently running.
16:10:11 <coremodule> #link https://testdays.fedoraproject.org/events/148
16:10:25 <jlinton> I noticed this https://bugzilla.redhat.com/show_bug.cgi?id=2167404 a month late, and I'm fairly certain that was just the EFI virtual address changes, and should be fixed in the release kernels.
16:12:04 <coremodule> thanks jlinton, waiting for bugzilla to load to take a look...
16:12:28 <coremodule> well, lets move on and I'll look at it when it loads
16:12:31 <coremodule> #info Please test and report any issues to #fedora-arm or the mailing list.
16:12:34 <jlinton> I will run the fedora kernel regression on the usual suspects in the next coupld days. But is there any value in opening BZ's about the LTP failures I was seeing a couple days ago? (OOM failures, mostly although there were a couple others)
16:12:35 <pwhalen> Would be good to check, not sure I have time but will try
16:13:23 <coremodule> jlinton, are they fixed or will be fixed with the release kernel?
16:13:49 <pwhalen> jlinton: if its not too much trouble, could be useful
16:14:31 <jforbes> Yes, worth tracking if these are regressions
16:14:49 <jlinton> I don't there are fixed in the released kernel. I don't tend to run LTP much, I was running it after some internal conversations and noticed that it wasn't completing cleanly with the rawhide versions of 6.2.
16:15:12 <jforbes> Does it compete cleanly with 6.1?
16:15:14 <jlinton> I will rerun it again with the test kernel, and see if anything changes but, i'm not really expecting it to.
16:15:25 <jlinton> I don't know.
16:17:27 <coremodule> #topic 3) ==== Bootloader Status ====
16:17:27 <coremodule> #info uboot-tools-2023.04-0.2.rc2.fc38
16:17:27 <coremodule> #link https://koji.fedoraproject.org/koji/buildinfo?buildID=2156096
16:18:01 <coremodule> this is a newer kernel than we discussed last week
16:18:17 <coremodule> i'm sure jforbes can enlighten us :)
16:19:01 <jforbes> ?
16:19:48 <coremodule> oh, nothing specific, just thought you might have something to mention/add
16:20:02 <coremodule> AH!
16:20:04 <coremodule> this is uboot
16:20:05 <coremodule> my bad
16:20:12 <coremodule> sorry jforbes
16:20:13 <jforbes> heh
16:20:54 <coremodule> for the record, this uboot is *not* newer than the one discussed last week
16:20:59 <coremodule> I don't have anything to add
16:21:54 <coremodule> #topic 4) ==== Fedora 38 status ===
16:21:55 <coremodule> #info OpenQA Testing
16:21:55 <coremodule> #info https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=38&build=Fedora-38-20230307.1&groupid=5
16:22:11 <coremodule> moving on to F38 openqa status
16:22:34 <coremodule> pwhalen, I know with IoT we have several expected failures, are there any like that with ARM?
16:23:35 <pwhalen> I haven't been following the arm testing tbh, so not sure about the status
16:24:11 <coremodule> okay, I will do a deep dive this week in comparison to previous weeks and see what I can find
16:25:07 <coremodule> #info Accepted Blockers & Freeze Exceptions
16:25:07 <coremodule> #link https://qa.fedoraproject.org/blockerbugs/milestone/38/beta/buglist
16:26:02 <jlinton> None of those are arm specific right?
16:26:17 <pwhalen> I started an install on an Altra,  it failed and dropped to grub. Looks to be an issue with Beaker though
16:26:42 <coremodule> jlinton, no, not that I can tell
16:26:51 <pwhalen> We dont have an AArch64 minimal image in the RC compose. It failed.
16:27:19 <jforbes> and it is not a blocker it seems
16:27:22 <pwhalen> https://koji.fedoraproject.org/koji/taskinfo?taskID=98392387
16:27:25 <jlinton> Yah, I saw pbrobinson's comment/request to make it blocking.
16:27:42 <jforbes> Well, the compose has to work I think, but even if the compose works, there are image issues
16:27:45 <pwhalen> jforbes: right. It really should be though
16:28:37 <coremodule> #info Fedora 38 Schedule
16:28:37 <coremodule> #link https://fedorapeople.org/groups/schedule/f-38/f-38-devel-tasks.html
16:28:39 <jforbes> pwhalen: Yeah, it was with armv7, seems odd that dropping an arch would drop an image type
16:28:44 <coremodule> here is a link to the release schedule for f38
16:30:52 <coremodule> I don't have anything else for F38
16:31:06 <coremodule> if no one else has anything, we'll move to the open floor
16:31:23 <pwhalen> Testing the RC would be greatly appreciated.
16:31:34 <coremodule> ah, yes, good point.
16:32:33 <coremodule> #topic 5) ==== Open Floor ====
16:32:46 <coremodule> anyone have anything for the open floor? otherwise, I will close the meeting!
16:33:01 <jlinton> I've been looking at spinning up the cloud images/fedora iso on the alibaba machines.
16:33:36 <jlinton> yt710's not the altras, and the cloud image fails validation because it doesn't have an nvme driver (and maybe there are issues with the ESP?)
16:34:23 <coremodule> thanks jlinton
16:34:27 <jlinton> the server image should work though, and it passes validation it just can't be attached to a host, which at the moment appears to be cloud-init related but debugging it is a bit of a pain due to lack of error messages.
16:35:24 <jlinton> That should when it works give us a "modern" arm test platform.
16:35:32 <jlinton> aka its armv9 with all the fancy features.
16:36:46 <coremodule> thanks for looking into that jlinton
16:37:12 <coremodule> alright! meeting end in 5...
16:37:14 <coremodule> 4...
16:37:16 <coremodule> 3...
16:37:18 <coremodule> 2...
16:37:19 <coremodule> 1...
16:37:33 <coremodule> thanks for attending! ARM testing is much appreciated if you have time...
16:37:36 <coremodule> #endmeeting