| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 05:50 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 05:54 | |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has joined #cip | 06:42 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has joined #cip | 12:53 | |
| *** jki <jki!~jki@95.157.49.24> has joined #cip | 12:56 | |
| *** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has joined #cip | 12:58 | |
| jki | hi everyone | 12:59 |
|---|---|---|
| masami | hello | 13:00 |
| arisut | hi | 13:00 |
| iwamatsu__ | hello | 13:00 |
| jki | ok, let's start | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
| collab-meetbot` | Meeting started Thu Apr 24 13:01:44 2025 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-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| collab-meetbot` | The 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 | |
| patersonc | Hey | 13:01 |
| jki | #topic AI review | 13:01 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | - write docs for release scripts [iwamatsu-san] | 13:01 |
| iwamatsu__ | I am updating it , but not finish. | 13:02 |
| jki | ok | 13:02 |
| jki | no other AIs recorded | 13:02 |
| jki | 5 | 13:02 |
| jki | 4 | 13:02 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #topic Kernel maintenance updates | 13:02 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| pave1 | Hi! | 13:03 |
| uli_ | i pushed 4.4 | 13:03 |
| masami | This week reported 28 new CVEs and 4 updated CVEs. | 13:03 |
| pave1 | I'm reviewing 6.1.135. | 13:03 |
| iwamatsu__ | I reviewed 6.1.132 | 13:03 |
| jki | anything else to add? | 13:05 |
| jki | 5 | 13:05 |
| jki | 4 | 13:05 |
| jki | 3 | 13:05 |
| jki | 2 | 13:05 |
| jki | 1 | 13:05 |
| jki | #topic Kernel release status | 13:05 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:05 | |
| jki | all on track | 13:05 |
| jki | anything to add? | 13:06 |
| jki | 5 | 13:06 |
| jki | 4 | 13:06 |
| jki | 3 | 13:06 |
| jki | 2 | 13:06 |
| jki | 1 | 13:06 |
| jki | #topic Kernel testing | 13:06 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:06 | |
| arisut | looking into why kernelci is not using cip configurations anymore looks like after moving from kernelci legacy to pipeline we loose the cip configuration settings | 13:07 |
| patersonc | I updated the stable-rc testing so we're testing the v6.14 and 6.15 etc. | 13:08 |
| arisut | I'm currently trying to restore the configuration to kernelci pipeline | 13:08 |
| patersonc | Thanks Arisu-san | 13:09 |
| arisut | patersonc, any idea on why https://github.com/kernelci/kernelci-pipeline/pull/840 is missing the cip:// configurations? | 13:10 |
| patersonc | I guess the plan was to add them later but didn't | 13:11 |
| arisut | ok thanks | 13:11 |
| patersonc | No technical reason - I just didn't try | 13:11 |
| arisut | I see, I will try to restore it on pipeline | 13:12 |
| arisut | also I think we want to run exclusively cip:// configurations | 13:13 |
| arisut | gitlab is testing only cip configurations I suppose | 13:13 |
| arisut | Kernelci should do same | 13:14 |
| patersonc | We also test some defconfigs in CIP | 13:14 |
| arisut | oh really? | 13:14 |
| patersonc | But technically we only support CIP configs | 13:14 |
| arisut | I see so we build defconfigs and cip configs | 13:15 |
| jki | problem is likely not testing - it's evaluating the results | 13:15 |
| jki | will we look at defconfig errors? | 13:15 |
| arisut | so less results is better ? | 13:15 |
| pave1 | We don't want to introduce regressions. | 13:15 |
| arisut | curerntly we are looking at defconfig ? | 13:16 |
| arisut | on gitlab | 13:16 |
| pave1 | If we introduced a bug so bad it affect defconfig, I'd really wanted us to investigate. | 13:16 |
| jki | then let's test defconfigs if maintainers do bother - fine | 13:16 |
| arisut | do you mean defconfig run only at needed ? | 13:16 |
| arisut | but usually don't get tested ? | 13:17 |
| patersonc | I would assume that generic users are more likely to try defconfig as a first step than CIP configs as they are in-tree | 13:17 |
| pave1 | We do look at gitconfigs on the gitlab. bbb_defconfig is normally only one that needs to be retried. | 13:17 |
| patersonc | arisut: defconfig is always run | 13:17 |
| arisut | we have generic users ? by policy cip is only supported on cip configurations afaik | 13:18 |
| pave1 | arisut: People are using our kernels, yes. We got some patches for 4.X because we broke audio on phones or something like that. | 13:19 |
| arisut | i see thanks | 13:19 |
| pave1 | arisut: Catching bugs early is quite cheap. Catching it after it is in tree for a year is less fun. | 13:19 |
| pave1 | arisut: But yes, supported configs on supported boards is only thing we officially support. | 13:20 |
| arisut | but referring to jki "problem is not testing, it's evaluating the results" | 13:20 |
| arisut | more things we tests more we have results to evaluate | 13:21 |
| jki | we can obviously revisit configs if they stay in permant failures, and no one looks at those | 13:22 |
| pave1 | arisut: Yes. Current gitlab setup makes it reasonably easy. | 13:22 |
| arisut | I'm ok on enabling defconfig and cip config | 13:22 |
| patersonc | Sounds good Arisu | 13:22 |
| arisut | pave1, current kernelci have a system for sending only regressions | 13:22 |
| pave1 | arisut: Yes, so regressions are what we really care about. If we break boot on arm64_defconfig, | 13:23 |
| pave1 | it is quite a big deal. | 13:23 |
| arisut | that i shared weeks ago and I don't find the link now | 13:23 |
| arisut | we are sending mail with only the board that have regression | 13:24 |
| arisut | also dashboard is becoming better https://d.kernelci.org/tree | 13:24 |
| jki | ok - anything to add regarding this or testing in general? | 13:25 |
| jki | 5 | 13:26 |
| jki | 4 | 13:26 |
| jki | 3 | 13:26 |
| jki | 2 | 13:26 |
| jki | 1 | 13:26 |
| jki | #topic AOB | 13:26 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:26 | |
| jki | just a recap: we have green lights to release 6.12-cip when we think it is ready | 13:27 |
| jki | TSC approved | 13:27 |
| pave1 | This may be good time. | 13:27 |
| patersonc | Any objections to adding the 6.12 tree to KernelCI? | 13:28 |
| jki | well, rather a precondition ;-) | 13:28 |
| iwamatsu__ | I will not be able to attend the next meeting. Japan is holiday season. | 13:29 |
| jki | 4.19.124-cip27 and 4.19.216-cip61, rcu stall on one cpu, apparently over held hb spinlock in futex_wake | 13:30 |
| jki | does that ring any bells by chance? | 13:31 |
| pave1 | "bh"? | 13:31 |
| pave1 | No, not really. | 13:31 |
| jki | hash bucket lock | 13:31 |
| pave1 | Aha, so not a bottom half. Still no bells. | 13:32 |
| jki | but there are no suspicious changes on kernel/futex.c, also in newer kernels | 13:32 |
| jki | ok - we need to hope for better reproducibility then | 13:32 |
| jki | anything else for today? | 13:32 |
| jki | 5 | 13:33 |
| jki | 4 | 13:33 |
| pave1 | So ... we wait for KernelCI | 13:33 |
| pave1 | with the 6.12? | 13:33 |
| patersonc | Shouldn't be a big job to add | 13:34 |
| jki | you likely mean our linux-6.12.y-cip branch, right? | 13:34 |
| patersonc | I'll create an MR today | 13:34 |
| patersonc | jki: Yes | 13:34 |
| jki | perfect | 13:34 |
| pave1 | I guess I could do 6.12 release with current tree (no version update, yet) after the KernelCI is ready | 13:35 |
| pave1 | if everyone is ok with that? | 13:35 |
| patersonc | Did we get the configs we need from members? | 13:36 |
| iwamatsu__ | I got some MR for 6.12. I am checking it. | 13:36 |
| jki | that's for qemu and x86 targets | 13:37 |
| patersonc | There's another for Renesas arm64 | 13:37 |
| jki | ah, right | 13:38 |
| jki | all those should be considered for kernelci | 13:39 |
| patersonc | I'll just add defconfig today - then Arisu can add the CIP configs at the same time as the other branches | 13:40 |
| patersonc | We don't have a 6.12-cip-rt yet right? | 13:41 |
| pave1 | There won't be 6.12-cip-rt tree. | 13:42 |
| pave1 | But we should probably do some configs with rt enabled. | 13:42 |
| jki | indeed | 13:42 |
| arisut | patersonc, ok | 13:42 |
| pave1 | So I guess we revisit 6.12-cip1 next week? :-) | 13:43 |
| jki | sure - except that we will need iwamatsu-san for the final decision, and he will be off | 13:45 |
| jki | but let's prepare the testing and configs and see when that is ready | 13:45 |
| jki | anything else? | 13:47 |
| jki | 5 | 13:47 |
| jki | 4 | 13:47 |
| jki | 3 | 13:47 |
| jki | 2 | 13:47 |
| jki | 1 | 13:47 |
| jki | #endmeeting | 13:48 |
| collab-meetbot` | Meeting ended Thu Apr 24 13:48:01 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/04/cip.2025-04-24-13.01.html | 13:48 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-24-13.01.txt | 13:48 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/04/cip.2025-04-24-13.01.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 | thank you all! | 13:48 |
| arisut | thx | 13:48 |
| uli_ | thanks | 13:48 |
| pave1 | Thank you! | 13:48 |
| iwamatsu__ | I think the blocker is probably config, but it will fix tomorrow. | 13:48 |
| masami | thank you | 13:48 |
| iwamatsu__ | Thank you. | 13:48 |
| pave1 | Hmm. May 1 and May 8 are holidays here, too. | 13:48 |
| *** masami <masami!~masami@FL1-122-134-103-12.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:48 | |
| jki | and enjoy holidays in japan! | 13:48 |
| *** jki <jki!~jki@95.157.49.24> has quit IRC (Quit: Leaving) | 13:48 | |
| pave1 | So don't be too surprised if I don't make it. | 13:48 |
| iwamatsu__ | :-) | 13:49 |
| patersonc | arisut: Should we be limiting the arches used for CIP? It looks like we build for all as we extend "base" | 13:51 |
| patersonc | https://github.com/patersonc/kernelci-pipeline/blob/main/config/trees.yaml#L4 | 13:52 |
| patersonc | Presumably we want "base-standard" plus riscv for the newer kernels? | 13:52 |
| patersonc | PR created: https://github.com/kernelci/kernelci-pipeline/pull/1130 | 14:20 |
| *** tmerciai <tmerciai!~tmerciai3@net-188-217-55-31.cust.vodafonedsl.it> has quit IRC (Remote host closed the connection) | 14:25 | |
| *** iwamatsu__ <iwamatsu__!~iwamatsu_@ae053227.dynamic.ppp.asahi-net.or.jp> has quit IRC (Quit: Client closed) | 14:50 | |
| arisut | yes we should limit the arch to only the one we use | 23:50 |
| arisut | for CIP | 23:50 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!