13:01:50 <jki> #startmeeting CIP IRC weekly meeting
13:01:50 <collab-meetbot> Meeting started Thu Dec  7 13:01:50 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:50 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:50 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:01:50 <iwamatsu> hi
13:02:01 <jki> #topic AI review
13:02:14 <jki> I didn't find any in the last report
13:02:21 <jki> anything missed?
13:02:42 <jki> 5
13:02:44 <jki> 4
13:02:46 <jki> 3
13:02:47 <jki> 2
13:02:49 <jki> 1
13:02:52 <jki> #topic Kernel maintenance updates
13:03:12 <uli> i reviewed 6.1.63 and prepared the next 4.4 release
13:03:23 <pave1> I did reviewes, 6.1.65 and 6.1.66
13:03:43 <iwamatsu> I am reviewing 6.1.65.
13:04:30 <masami> hello
13:04:56 <uli> masami: #topic Kernel maintenance updates
13:05:06 <masami> uli: thank you
13:05:09 <uli> ;)
13:05:16 <masami> This week reported 2 new CVEs and 2 updated CVEs.
13:05:27 <pave1> masami: the "Spectre based on Linear Addres\
13:05:29 <pave1> s Masking"
13:05:56 <jki> that is for to-be-released HW only
13:06:03 <jki> to my understanding
13:06:04 <pave1> vulnerability is "fun". I hope the CPU vendors add suitable chicken bits, given that the hardware was not yet released.
13:06:19 <jki> exactly
13:06:41 <masami> maybe, microcode update..
13:07:09 <pave1> There was AMD CVE quoted there, and AMD response was like "so our cpus are buggy... deal with that.". :-(.
13:08:05 <masami> pavel: :-(
13:08:49 <jki_> grr, was disconnected
13:08:56 <jki_> may have lost moderation
13:09:18 <pave1> And now the moderation bot will eat the world :-).
13:09:55 <jki_> at least record this fully...
13:10:18 <jki_> ok, anything else on CVEs or maintenance?
13:11:07 <jki_> 5
13:11:08 <jki_> 4
13:11:09 <jki_> 3
13:11:10 <jki_> 2
13:11:12 <jki_> 1
13:11:15 <jki_> #topic Kernel release status
13:12:00 <jki_> iwamatsu nicely shared that already on the list
13:12:29 <jki_> anything to add / discuss?
13:13:31 <iwamatsu> Pave1: I commented about 4.19 in mail,
13:13:37 <pave1> #topic Kernel release status
13:14:20 <uli> errr, what exactly is going on here? :)
13:14:25 <pave1> I can do the 4.19-cip release, yes.
13:14:34 <iwamatsu> Please update and release 4.19.y. Thank you!
13:14:44 <pave1> Ok, will do :-).
13:14:50 <iwamatsu> :-)
13:15:16 <pave1> I tried to steal jki's name to get control of the robot. I guess it did not work.
13:15:24 <jki_> (/me shouldn't have started the meeting with my current link)
13:17:23 <jki> at least I have my name back
13:17:30 <jki> ok, moving on...
13:17:32 <jki> 3
13:17:34 <jki> 2
13:17:36 <jki> 1
13:17:38 <jki> #topic Kernel testing
13:17:47 <patersonc> Hello
13:18:12 <patersonc> There are some MRs going on for the SQUAD work. Other than that it's been conference week
13:18:40 <pave1> We have had some random failures in testing. Most of them cleared when I hit retry.
13:18:46 <pave1> But this one is somehow recurring:
13:18:47 <pave1> https://lava.ciplatform.org/scheduler/job/1050903
13:19:22 <pave1> I believe it will clear when hitting retry, but it is common enough that it may be worth investigating.
13:19:46 <pave1> Note the 100 second jump in the timestamps.
13:19:48 <patersonc> Thanks Pavel
13:20:25 <patersonc> Do you know if you always see the issue with the same kernel?
13:20:58 <jki> is the jump the only indication of the problem?
13:20:59 <pave1> I did not really investigated that much.
13:21:25 <pave1> We'll also get "[  OK  ] Reached target System Initialization.
13:21:26 <pave1> login-action timed out after 119 seconds
13:21:28 <pave1> "
13:21:36 <jki> ah, ok, now i see
13:21:37 <pave1> So it shows as a failure.
13:21:45 <jki> fair enough
13:22:59 <sietze> There's a 120 s timeout on the login action, if it takes longer, then the test job will fail and mark as incomplete
13:23:00 <jki> someone would have to dig deeper, I suppose...
13:23:14 <sietze> So the source could be very well that 100s jump
13:23:51 <pave1> So I'd ask patersonc to take a look, and if it looks to him like kernel issue, I can take over?
13:24:44 <patersonc> Sure
13:24:52 <pave1> Thank you!
13:25:46 <jki> ok, great
13:27:35 <jki> anything else on testing?
13:27:45 <sietze> Did I already share the link to our PoC for custom SQUAD Reports?
13:27:52 <hunter> I am pushing the final changes today actually right now
13:28:22 <hunter> There also seems to be a bit of a pause since the last testing but seems to work for weekly when tested.
13:28:58 <sietze> Actually, SQUAD hasn't gone live yet, so that's the reason why there aren't so many reports there
13:29:36 <hunter> ah gotchya well if tested it should work fine i'll make the PR in a second
13:29:46 <sietze> Great!
13:30:03 <hunter> thanks for being patient with me about it! things came up
13:31:16 <sietze> no problem
13:31:38 <jki> then we will likely here more about this next week :)
13:32:18 <sietze> Looking forward to that!
13:32:44 <jki> moving on...
13:32:45 <jki> 5
13:32:47 <jki> 4
13:32:48 <jki> 3
13:32:49 <jki> 2
13:32:50 <jki> 1
13:32:52 <jki> #topic AOB
13:34:12 <jki> forgot to mention my AI earlier:
13:34:20 <jki> should write something up where our SLTS is going, where we will have challenges, where we need more support
13:35:00 <jki> may become a CIP blog post if readable
13:35:14 <jki> anyone any other topics?
13:36:05 <jki> 5
13:36:07 <jki> 4
13:36:09 <jki> 3
13:36:11 <jki> 2
13:36:12 <jki> 1
13:36:14 <jki> #endmeeting