Thursday, 2023-12-07

« Wednesday, 2023-12-06 Index Friday, 2023-12-08 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:55
*** rajm <rajm!~robert@82.27.50.32> has joined #cip06:58
*** frieder <frieder!~frieder@i5C75E6C6.versanet.de> has joined #cip08:02
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip09:37
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip09:37
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 252 seconds)10:18
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)10:18
*** uli <uli!~quassel@static.153.40.69.159.clients.your-server.de> has joined #cip10:48
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip10:54
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip10:54
*** hunter <hunter!~hunter@d1256rzdslszc48vsmp-4.rev.dnainternet.fi> has joined #cip11:04
*** hunter <hunter!~hunter@d1256rzdslszc48vsmp-4.rev.dnainternet.fi> has quit IRC (Client Quit)11:05
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)12:43
*** jki <jki!~jki@80.149.170.9> has joined #cip12:58
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip12:59
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip12:59
jkihi all!13:00
sietzeHello!13:00
ulihello13:00
arisuthi13:00
pave1hi!13:01
jkiok, let's get started13:01
jki#startmeeting CIP IRC weekly meeting13:01
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:01
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:01
iwamatsuhi13:01
jki#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jkiI didn't find any in the last report13:02
jkianything missed?13:02
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip13:02
jki513:02
jki413:02
jki313:02
jki213:02
jki113:02
jki#topic Kernel maintenance updates13:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:02
ulii reviewed 6.1.63 and prepared the next 4.4 release13:03
pave1I did reviewes, 6.1.65 and 6.1.6613:03
iwamatsuI am reviewing 6.1.65.13:03
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip13:04
masamihello13:04
ulimasami: #topic Kernel maintenance updates13:04
masamiuli: thank you13:05
uli;)13:05
masamiThis week reported 2 new CVEs and 2 updated CVEs.13:05
pave1masami: the "Spectre based on Linear Addres\13:05
pave1s Masking"13:05
jkithat is for to-be-released HW only13:05
jkito my understanding13:06
pave1vulnerability is "fun". I hope the CPU vendors add suitable chicken bits, given that the hardware was not yet released.13:06
jkiexactly13:06
masamimaybe, microcode update..13:06
pave1There was AMD CVE quoted there, and AMD response was like "so our cpus are buggy... deal with that.". :-(.13:07
masamipavel: :-(13:08
*** jki_ <jki_!~jki@80.149.170.9> has joined #cip13:08
jki_grr, was disconnected13:08
jki_may have lost moderation13:08
pave1And now the moderation bot will eat the world :-).13:09
jki_at least record this fully...13:09
jki_ok, anything else on CVEs or maintenance?13:10
jki_513:11
jki_413:11
jki_313:11
jki_213:11
jki_113:11
jki_#topic Kernel release status13:11
jki_iwamatsu nicely shared that already on the list13:12
*** jki <jki!~jki@80.149.170.9> has quit IRC (Ping timeout: 268 seconds)13:12
jki_anything to add / discuss?13:12
*** jki_ <jki_!~jki@80.149.170.9> has quit IRC (Client Quit)13:13
*** jki <jki!~pavel@jabberwock.ucw.cz> has joined #cip13:13
iwamatsuPave1: I commented about 4.19 in mail,13:13
pave1#topic Kernel release status13:13
*** jki_ <jki_!~jki@80.149.170.9> has joined #cip13:13
ulierrr, what exactly is going on here? :)13:14
pave1I can do the 4.19-cip release, yes.13:14
*** jki <jki!~pavel@jabberwock.ucw.cz> has quit IRC (Client Quit)13:14
iwamatsuPlease update and release 4.19.y. Thank you!13:14
pave1Ok, will do :-).13:14
iwamatsu:-)13:14
pave1I tried to steal jki's name to get control of the robot. I guess it did not work.13:15
jki_(/me shouldn't have started the meeting with my current link)13:15
*** jki <jki!~jki@80.149.170.9> has joined #cip13:17
jkiat least I have my name back13:17
jkiok, moving on...13:17
jki313:17
jki213:17
jki113:17
jki#topic Kernel testing13:17
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:17
patersoncHello13:17
patersoncThere are some MRs going on for the SQUAD work. Other than that it's been conference week13:18
pave1We have had some random failures in testing. Most of them cleared when I hit retry.13:18
pave1But this one is somehow recurring:13:18
pave1https://lava.ciplatform.org/scheduler/job/105090313:18
pave1I believe it will clear when hitting retry, but it is common enough that it may be worth investigating.13:19
pave1Note the 100 second jump in the timestamps.13:19
patersoncThanks Pavel13:19
*** jki_ <jki_!~jki@80.149.170.9> has quit IRC (Ping timeout: 260 seconds)13:20
patersoncDo you know if you always see the issue with the same kernel?13:20
jkiis the jump the only indication of the problem?13:20
pave1I did not really investigated that much.13:20
pave1We'll also get "[  OK  ] Reached target System Initialization.13:21
pave1login-action timed out after 119 seconds13:21
pave1"13:21
jkiah, ok, now i see13:21
pave1So it shows as a failure.13:21
jkifair enough13:21
*** hunter <hunter!~hunter@d1256rzdslszc48vsmp-4.rev.dnainternet.fi> has joined #cip13:21
sietzeThere's a 120 s timeout on the login action, if it takes longer, then the test job will fail and mark as incomplete13:22
jkisomeone would have to dig deeper, I suppose...13:23
sietzeSo the source could be very well that 100s jump13:23
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)13:23
pave1So I'd ask patersonc to take a look, and if it looks to him like kernel issue, I can take over?13:23
patersoncSure13:24
pave1Thank you!13:24
jkiok, great13:25
jkianything else on testing?13:27
sietzeDid I already share the link to our PoC for custom SQUAD Reports?13:27
hunterI am pushing the final changes today actually right now13:27
hunterThere also seems to be a bit of a pause since the last testing but seems to work for weekly when tested.13:28
sietzeActually, SQUAD hasn't gone live yet, so that's the reason why there aren't so many reports there13:28
hunterah gotchya well if tested it should work fine i'll make the PR in a second13:29
sietzeGreat!13:29
hunterthanks for being patient with me about it! things came up13:30
sietzeno problem13:31
jkithen we will likely here more about this next week :)13:31
sietzeLooking forward to that!13:32
jkimoving on...13:32
jki513:32
jki413:32
jki313:32
jki213:32
jki113:32
jki#topic AOB13:32
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:32
jkiforgot to mention my AI earlier:13:34
jkishould write something up where our SLTS is going, where we will have challenges, where we need more support13:34
jkimay become a CIP blog post if readable13:35
jkianyone any other topics?13:35
jki513:36
jki413:36
jki313:36
jki213:36
jki113:36
jki#endmeeting13:36
collab-meetbotMeeting ended Thu Dec  7 13:36:14 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:36
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-07-13.01.html13:36
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-07-13.01.txt13:36
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-07-13.01.log.html13:36
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"13:36
sietzeThanks!13:36
iwamatsuThank you13:36
ulithank you13:36
masamithanks13:36
jkithanks all!13:36
patersoncThanks13:36
pave1thank you!13:36
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:36
*** jki <jki!~jki@80.149.170.9> has quit IRC (Remote host closed the connection)13:36
hunterthanks!13:36
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)13:43
arisutthanks13:48
*** hunter <hunter!~hunter@d1256rzdslszc48vsmp-4.rev.dnainternet.fi> has quit IRC (Quit: Konversation terminated!)13:56
*** arisut <arisut!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo)15:25
*** arisut <arisut!~none@gentoo/developer/alicef> has joined #cip15:25
*** ChanServ sets mode: +o arisut15:25
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds)16:54
*** frieder <frieder!~frieder@i5C75E6C6.versanet.de> has quit IRC (Remote host closed the connection)19:40
*** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 240 seconds)22:45
« Wednesday, 2023-12-06 Index Friday, 2023-12-08 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!