| *** monstr <monstr!~monstr@62.48.184.130> has joined #cip | 05:49 | |
| *** monstr_ <monstr_!~monstr@165.204.84.17> has joined #cip | 05:51 | |
| *** monstr <monstr!~monstr@62.48.184.130> has quit IRC (Ping timeout: 252 seconds) | 05:54 | |
| *** rajm <rajm!~robert@host-78-151-153-40.as13285.net> has joined #cip | 06:55 | |
| *** monstr_ <monstr_!~monstr@165.204.84.17> has quit IRC (Ping timeout: 252 seconds) | 07:00 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has joined #cip | 07:28 | |
| *** monstr <monstr!~monstr@110.8.30.213.rev.vodafone.pt> has joined #cip | 09:37 | |
| *** monstr <monstr!~monstr@110.8.30.213.rev.vodafone.pt> has quit IRC (Remote host closed the connection) | 09:46 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has quit IRC (Ping timeout: 244 seconds) | 12:30 | |
| *** prabhakalad <prabhakalad!~prabhakar@136.226.168.182> has joined #cip | 12:31 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:52 | |
| *** iwamatsu__8 <iwamatsu__8!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:58 | |
| *** iwamatsu__8 <iwamatsu__8!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Client Quit) | 12:58 | |
| *** jki <jki!~jki@62.156.206.42> has joined #cip | 13:01 | |
| jki | hi all | 13:01 |
|---|---|---|
| pave1 | Hi! | 13:01 |
| uli_ | hello | 13:01 |
| arisut | hi | 13:01 |
| patersonc | Hey | 13:01 |
| iwamatsu__ | hello | 13:01 |
| jki | let's start | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot` | Meeting started Thu May 15 13:02:27 2025 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 review | 13:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | nothing on my list | 13:02 |
| jki | 5 | 13:03 |
| jki | 4 | 13:03 |
| jki | 3 | 13:03 |
| jki | 2 | 13:03 |
| jki | 1 | 13:03 |
| jki | #topic Kernel maintenance updates | 13:03 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| pave1 | I'm reviewing 6.1.138 & .139. | 13:03 |
| uli_ | i pushed 4.4 | 13:03 |
| pave1 | .139 contains workarounds for another Spectre-like problem, and they currently break the build in our 6.1 testing. | 13:04 |
| iwamatsu__ | I reviewed 6.1.136, and released 5.10.y-cip | 13:04 |
| pave1 | Oh -stable is not back porting them to 5.10 for now. | 13:05 |
| jki | known-bugs? :) | 13:05 |
| pave1 | It will be "wait a bit, then investigate... and then KNOWN-BUGS". | 13:06 |
| jki | and 6.1.139 has a build-bug then? | 13:06 |
| jki | reported already? | 13:07 |
| pave1 | jki: No, we caught it in -rc1 testing, so we are now at -rc2 (different bug) and it is likely to be fixed. | 13:07 |
| jki | ah, ok | 13:07 |
| jki | anything to add? | 13:10 |
| jki | 5 | 13:10 |
| jki | 4 | 13:10 |
| jki | 3 | 13:10 |
| jki | 2 | 13:10 |
| jki | 1 | 13:10 |
| jki | #topic Kernel release status | 13:10 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| jki | all on schedule | 13:10 |
| patersonc | \o/ | 13:11 |
| jki | 6.12-cip status? | 13:11 |
| pave1 | Thanks Iwamatsu for 5.10-cip, -cip-rt is now being tested. | 13:11 |
| iwamatsu__ | :-) | 13:11 |
| jki | so, where are we with 6.12? | 13:13 |
| iwamatsu__ | I dont think there's a blocker now. | 13:13 |
| jki | then tag what we have? :) | 13:14 |
| iwamatsu__ | Who will release it? | 13:15 |
| jki | iwamatsu__: wasn't that you? | 13:15 |
| iwamatsu__ | Ah, sorry . I did not understand that. | 13:16 |
| iwamatsu__ | I will prepare it. | 13:16 |
| jki | ok, perfect | 13:19 |
| jki | then let's move on | 13:20 |
| jki | 5 | 13:20 |
| jki | 4 | 13:20 |
| jki | 3 | 13:20 |
| jki | 2 | 13:20 |
| jki | 1 | 13:20 |
| jki | #topic Kernel testing | 13:20 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:20 | |
| arisut | working on adding cip-kernel-confing to KernelCI https://github.com/kernelci/kernelci-pipeline/pull/1149 | 13:20 |
| patersonc | No updates from my end this week | 13:20 |
| patersonc | Thanks arisut, I missed that | 13:21 |
| arisut | we recently ported the legacy code of cip fragments to maestro | 13:21 |
| arisut | and we are currently working on adding cip-kernel-configs and disable all the configurations that are not needed to us | 13:22 |
| arisut | also currently cip kernel can be build on demand with kci-dev | 13:24 |
| patersonc | That's great. | 13:24 |
| patersonc | I saw that there were a couple of build errors for cip 5.10, but both for chromeos configs | 13:24 |
| arisut | yes we need to disable chromeos configs on cip | 13:25 |
| arisut | unfortunatly for doing that part of the code need to be rewrite afaik | 13:25 |
| pave1 | If there are failures on -cip that are not present on corresponding -stable, we may want to investigate. | 13:25 |
| pave1 | If there are failures on -stable, we may want -stable people to investigate :-). | 13:25 |
| arisut | yes but chromeos are chromeos dependent configurations | 13:25 |
| arisut | we actually want to test chromeos configurations ? | 13:26 |
| pave1 | Even random configs should build in ideal world. | 13:27 |
| arisut | I don't mind both cases | 13:27 |
| pave1 | ...we don't need to spend too much time testing, but if we already have the failure. | 13:27 |
| arisut | so we don't need to block chromeos config? | 13:28 |
| pave1 | It may be good time for me to familiarize with test environment :-). | 13:28 |
| patersonc | I can see a kernelci build for v5.10.236, but not v5.10.237 for some reason | 13:28 |
| arisut | the code i write is not yet in production | 13:28 |
| arisut | we can look into that | 13:29 |
| pave1 | Maybe you can send pointer to failures to the mailing list, and I'll try to take a look? | 13:30 |
| arisut | patersonc, is that from the dashboard? | 13:34 |
| patersonc | yes | 13:34 |
| arisut | v5.10.237 cip is here https://dashboard.kernelci.org/tree/f32dc72d4e2a5cadfdfca58f84404d51cae038a0?ti%7Cc=v5.10.237-cip60&ti%7Cch=f32dc72d4e2a5cadfdfca58f84404d51cae038a0&ti%7Cgb=linux-5.10.y-cip&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fcip%2Flinux-cip.git&ti%7Ct=cip | 13:34 |
| arisut | cip60 | 13:35 |
| patersonc | Yes. But the linux-stable build for 5.10.237 isn't as far as I can see | 13:35 |
| arisut | I see | 13:35 |
| patersonc | I've asked on Discord | 13:36 |
| iwamatsu__ | https://dashboard.kernelci.org/tree/f32dc72d4e2a5cadfdfca58f84404d51cae038a0?df%7Cbs%7CFAIL=true&df%7Cc%7Cdefconfig%2Barm64-chromebook%2BCONFIG_CPU_BIG_ENDIAN%3Dy%2Bdebug%2Bkselftest%2Btinyconfig=true&ti%7Cc=v5.10.237-cip60&ti%7Cch=f32dc72d4e2a5cadfdfca58f84404d51cae038a0&ti%7Cgb=linux-5.10.y-cip&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Fl | 13:37 |
| iwamatsu__ | inux%2Fkernel%2Fgit%2Fcip%2Flinux-cip.git&ti%7Ct=cip | 13:37 |
| iwamatsu__ | ihere appears to be a problem with the CIP. | 13:38 |
| patersonc | Maybe we should be testing more configs then :P | 13:40 |
| patersonc | More info here: https://dashboard.kernelci.org/issue/maestro%3Abad69ae5a6031018d1b7534daa1623f5b6bc4cef?iv=1 | 13:40 |
| jki | sorry, I'm distracted right now - let me know when you are done :) | 13:40 |
| iwamatsu__ | OK, I will take a look, too. | 13:41 |
| patersonc | Thanks | 13:42 |
| pave1 | I guess we should take this to the mailing list. | 13:42 |
| pave1 | irqreturn_t problem seems like a missing include; trying CONFIG_BIG_ENDIAN is .. interesting but it should not be hard to fix. | 13:42 |
| jki | anything to add for testing? | 13:44 |
| jki | 5 | 13:46 |
| jki | 4 | 13:46 |
| jki | 3 | 13:46 |
| jki | 2 | 13:46 |
| jki | 1 | 13:46 |
| jki | #topic AOB | 13:46 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:46 | |
| uli_ | i'll be absent next week | 13:46 |
| jki | ok - anything else? | 13:48 |
| jki | 5 | 13:48 |
| jki | 4 | 13:48 |
| jki | 3 | 13:48 |
| jki | 2 | 13:48 |
| jki | 1 | 13:48 |
| jki | #endmeeting | 13:48 |
| collab-meetbot` | Meeting ended Thu May 15 13:48:49 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:48 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-15-13.02.html | 13:48 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-15-13.02.txt | 13:48 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/05/cip.2025-05-15-13.02.log.html | 13:48 |
| *** 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 13: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:48 | |
| jki | thanks! | 13:48 |
| pave1 | Thank you! | 13:48 |
| uli_ | thanks | 13:48 |
| arisut | thx | 13:49 |
| iwamatsu__ | thank you | 13:49 |
| patersonc | Cheers | 13:49 |
| patersonc | arisut let me know if you need anything from me to help with your kci work | 13:49 |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 13:49 | |
| *** jki <jki!~jki@62.156.206.42> has quit IRC (Quit: Leaving) | 13:51 | |
| *** sskartheekadivi <sskartheekadivi!uid661193@id-661193.helmsley.irccloud.com> has joined #cip | 15:17 | |
| *** sskartheekadivi <sskartheekadivi!uid661193@id-661193.helmsley.irccloud.com> has left #cip | 15:28 | |
| *** monstr <monstr!~monstr@62.48.184.130> has joined #cip | 16:09 | |
| *** monstr_ <monstr_!~monstr@165.204.84.17> has joined #cip | 16:11 | |
| *** monstr <monstr!~monstr@62.48.184.130> has quit IRC (Ping timeout: 252 seconds) | 16:13 | |
| *** monstr__ <monstr__!~monstr@62.48.184.130> has joined #cip | 16:18 | |
| *** monstr_ <monstr_!~monstr@165.204.84.17> has quit IRC (Ping timeout: 252 seconds) | 16:21 | |
| *** sskartheekadivi <sskartheekadivi!uid661193@user/sskartheekadivi> has joined #cip | 16:37 | |
| *** monstr__ <monstr__!~monstr@62.48.184.130> has quit IRC (Remote host closed the connection) | 16:40 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-51-51.cust.vodafonedsl.it> has quit IRC (Ping timeout: 244 seconds) | 18:00 | |
| *** sskartheekadivi <sskartheekadivi!uid661193@user/sskartheekadivi> has quit IRC (Quit: Connection closed for inactivity) | 19:08 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!