Thursday, 2023-11-02

« Wednesday, 2023-11-01 Index Friday, 2023-11-03 »
*** uli_ <uli_!~uli@49.150.109.202> has joined #cip04:09
*** uli_ <uli_!~uli@49.150.109.202> has quit IRC (Remote host closed the connection)04:29
*** uli_ <uli_!~uli@49.150.109.202> has joined #cip04:30
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip05:29
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:52
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has joined #cip08:22
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)08:23
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has joined #cip08:24
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)08:24
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has joined #cip08:24
*** HRafuse <HRafuse!~HRafuse@d4yqqhzyn2nrhnzmfvy-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)08:26
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip09:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)09:10
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip10:31
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)11:24
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip11:24
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)11:27
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip11:27
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)11:41
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip11:41
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)11:47
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip11:48
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has joined #cip11:57
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)12:02
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has joined #cip12:03
HRafusehello12:04
masamihi12:04
iwamatsuhello12:04
iwamatsuIt looks like Jan hasn't joined yet.12:06
patersoncHis email said it would be in an hour12:06
HRafuseAh okay12:06
patersoncSummer time has ended in GMT land12:06
iwamatsuOh12:07
masamiah, yes12:07
patersoncWhich I guess means it's getting a bit late in Japan12:07
patersoncMaybe we can move the meeting to be fixed on Japan time, not Europe time12:07
HRafuseShould be snowing soon too there12:07
patersoncHRafuse: It's certainly raining non-stop12:08
HRafuseoh same here, it's trying to snow but it rains instead12:08
iwamatsupatersonc: It is same as TSC meeting. no problem to me.12:09
HRafuseI am also open to later time if that makes it easier12:09
masamiI'm ok on both 12:00(GMT) and 13:00(GMT)12:13
patersoncWell for today at least we'll have to wait for Jan at 1300 GMT :)12:13
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip12:21
*** HRafuse <HRafuse!~HRafuse@83-245-217-192.elisa-laajakaista.fi> has quit IRC (Remote host closed the connection)12:38
*** HRafuse <HRafuse!~HRafuse@d4yqqhdsz2sv6g9zsgf-4.rev.dnainternet.fi> has joined #cip12:42
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)12:57
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip12:59
*** jki <jki!~jki@46.128.188.24> has joined #cip13:01
jkihi all13:01
uli_hello13:01
iwamatsuhi13:01
masamihi13:01
HRafusehello13:01
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 255 seconds)13:01
jkihope we didn't lose anyone over time shifting13:02
patersonchello13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Nov  2 13:02:35 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jkistill none recorded13:02
jkianything to add?13:02
jki513:03
jki413:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
pave1Hi!13:03
pave1Reviewing 6.1.61.13:03
uli_i'm preparing 4.4 and reviewing 6.1.6013:03
masamiThis week reported 2 new CVEs and 3 updated CVEs.13:03
iwamatsuI reviewed 6.1.60, and reviewing 6.1.61.13:04
pave1I looked at the CVEs. There's a scary one, but it should be virtualization-only, and only affects "Secure Encrypted Virtualizations", so likely we can wait for stable to handle this.13:05
jkianyhing else?13:07
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel release status13:07
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:07
jki- 4.413:07
uli_on track, will post request for reviews soon13:08
pave1-rt is up-to-date.13:08
jki- 4.1913:08
pave1-rt is due next month13:08
iwamatsuon track, I am preparing release this week.13:08
jki- 5.1013:09
pave1-rt is due in 14 days13:10
iwamatsuon track I will release this week too.13:10
jki- 6.113:10
pave1iwamatsu:13:10
pave1you may want to wait with 5.10 release.13:10
pave15.10.199 is buggy on renesas. FIx is known but maybe just wait for .10.200.13:10
iwamatsuAha, I forgot it. Thanks.13:11
pave16.1-rt is due at end of month.13:11
jkiand regular one was just released as well13:12
iwamatsuPave1: thanks for release -cip tree.13:12
jkigood13:12
jkiyeah, good to see that we can rotate roles :)13:12
pave1iwamatsu: You are welcome. I'm glad I tried the process.13:12
jkithen let's move on13:13
jki#topic Kernel testing13:13
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:13
patersoncHello13:13
patersoncNothing that exciting to highlight this week from me13:14
patersoncI looked into multi-boot jobs in LAVA a bit13:14
patersoncHopefully that'll be useful for swupdate13:14
jkidoes that solve the issue of testing watchdog resets?13:14
patersoncNo - it would only work if LAVA initiates the reboot13:15
jkithat is the problem13:15
patersoncah okay13:15
jkiwe can't set swupdate properly without watchdogs13:15
jkis/set/test/13:15
patersoncMaybe we can find a way13:16
jkiyou can test a good share, but not the "funny" cases13:16
patersoncLAVA will watch for specific strings, so if we tell a test case to watch for the first line of a reboot after watchdog timeout maybe it can do something, but then the LAVA scripts won't be running in Linux anymore so it won't be able to complete the test case. hmmm13:16
patersoncIt may be worth sending a mail to the lava mailing list to see if anyone there has any suggestions13:17
jkiexactly, there is a design problem with lava here13:17
jkii thought that was discussed already, but I was not involved13:17
jkiwill ping my colleagues on that13:18
patersoncThanks13:18
jkianother DE-Nano-SOC is running again in our lab13:20
jkithe IPC227E still had some issue on Tuesday, should follow soon13:20
patersoncThanks!13:21
jkianything else regarding testing?13:22
patersoncNot from me13:22
jki513:23
jki413:23
jki313:23
jki213:23
jki113:23
jki#topic AOB13:23
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:23
jkieveryone still happy with our time slot?13:23
HRafuseYes, it is fine with me.13:23
pave1I would not mind hour earlier, but can do this.13:24
masamiYes.13:24
iwamatsuEither is fine.13:24
jkiwell, if no one suggests to move, let's keep it (CET-anchored)13:26
jkimaybe Europe will give up on daylight saving, one day, when all other problems are solved ;)13:26
patersoncWe can only hope13:26
jkianyone anything else?13:26
HRafuseI am hoping13:26
jki513:27
patersoncBudget for 202413:27
jki413:27
jkigood point13:27
jkiwas some update requested already from us?13:27
jkiah, I missed the TSC...13:28
patersoncI think in this weeks TSC, but I wasn't there :P13:28
jkime neither13:28
jkioops13:28
patersoncI got asked to think about testing budget for next year13:28
patersoncPresumably kernel team needs to do the same13:28
jkiright13:28
jkiare we expecting more work next year?13:29
jkiare we fine with the current situation? (I'm assuming that)13:29
pave1When is 4.19 ending maintainance by kernel team?13:29
jkiend of 2413:30
pave1Dec 2024.13:30
jkiexactly13:30
jki2026 will be the "fun" year13:30
pave1So we'll get little more work at that point. I guess that means increase in 2025.13:30
jkiyep, plus one more kernel in 25, if all goes well13:31
pave1Ok, so significant increase in 2025.13:31
patersoncWe really need to get our testing better by then...13:32
pave1Yeah.13:32
HRafuseWhat are the current issues with testing?13:32
pave1Actually I believe we should somehow expanding 4.4 testing.13:32
patersoncThe person in charge is rubbish13:32
patersoncpave1: agreed13:32
pave1stable team was doing testing for us, and that no longer happens.13:32
HRafuseahh okay well I am not a team but will be willing to help13:33
jkido we have a concrete list of todos?13:33
jkiwould help contributors to get started13:33
pave1For 4.4 I'd suggest at least compile testing all non-crazy architectures.13:34
jkiand would also help us to budget efforts13:34
jkiwhat's in KernelCI so far? nothing for 4.4?13:34
patersoncjki: No. I need to carve out a day and get a backlog sorted13:34
patersonc4.4 is being tested by kernelci: https://linux.kernelci.org/job/cip/13:35
patersoncCIP and -st versions13:35
patersoncand -rt13:35
jkiso, what is missing then for 4.4?13:35
patersoncFor CIP's testing, we're not actually testing much, mainly boot testing. And for the kernelci testing noone is really monitoring the output and acting on failures (as far as I understand)13:36
jkimaybe we should have a week test report, just like the weekly CVE news ;)13:37
jkiyeah, someone reading, sorting tracking, possibly fixing - that would be a start13:38
pave1I can do the fixing :-).13:38
patersoncjkl: agreed13:38
jkiHRafuse: would you have some bandwidth - and an idea where to look at?13:39
HRafuseSomewhat, I am looking through the testing and things now. I think a backlog might be more structured and reduce the time it takes to fix this issue.13:40
HRafuseI can do the reading and sorting to start with.13:41
patersoncThank you HRafuse. And yes some tickets would certainly help! I'll try and get organised13:41
jkicool!13:41
HRafuseNo worries patersonc.13:42
jkiok - back to budget13:43
jkithen I will only ask Neal to request offers for the same amount of hours next year13:43
jkithen we have the kernel budget at least13:43
patersoncSure13:43
jkianything else for today?13:45
jki513:45
jki413:45
jki313:45
jki213:45
jki113:45
HRafuseJust that I am quite excited to get things rolling. Looking forward to working on this project.13:45
jki#endmeeting13:45
collab-meetbot`Meeting ended Thu Nov  2 13:45:55 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:45
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-02-13.02.html13:45
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-02-13.02.txt13:45
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-02-13.02.log.html13:45
*** 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:45
pave1Thank you!13:46
jkithanks all!13:46
iwamatsuthank you!13:46
uli_thanks13:46
masamithank you13:46
HRafusethanks!13:46
patersoncThanks for joining HRafuse13:46
jkiHRafuse: thanks a lot for offering help!13:46
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:46
HRafuseanytime jki and patersonc also new to irc but will get used to it13:46
patersonc:)13:47
*** uli_ <uli_!~uli@49.150.109.202> has quit IRC (Quit: Leaving)13:52
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip14:21
*** HRafuse <HRafuse!~HRafuse@d4yqqhdsz2sv6g9zsgf-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)15:00
*** jki <jki!~jki@46.128.188.24> has quit IRC (Quit: Leaving)15:05
*** HRafuse <HRafuse!~HRafuse@d4yqqhbqcd9zylcdy7t-4.rev.dnainternet.fi> has joined #cip15:25
*** HRafuse <HRafuse!~HRafuse@d4yqqhbqcd9zylcdy7t-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)15:29
*** HRafuse <HRafuse!~HRafuse@d4yqqh1jssd2-d0hl4y-4.rev.dnainternet.fi> has joined #cip15:39
*** HRafuse <HRafuse!~HRafuse@d4yqqh1jssd2-d0hl4y-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)15:39
*** HRafuse <HRafuse!~HRafuse@d4yqqh1jssd2-d0hl4y-4.rev.dnainternet.fi> has joined #cip15:42
*** HRafuse <HRafuse!~HRafuse@d4yqqh1jssd2-d0hl4y-4.rev.dnainternet.fi> has quit IRC (Remote host closed the connection)15:42
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:42
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip18:10
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 264 seconds)22:47
« Wednesday, 2023-11-01 Index Friday, 2023-11-03 »

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