| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 01:20 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:17 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 07:24 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 09:30 | |
| *** uli <uli!~uli@175.176.15.140> has joined #cip | 10:47 | |
| *** jki <jki!~jki@88.215.103.113> has joined #cip | 12:56 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 12:59 | |
| *** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:c18b:3221:d756:217b> has joined #cip | 12:59 | |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip | 13:00 | |
| jki | hi all! | 13:00 |
|---|---|---|
| masami | hi | 13:01 |
| uli | hello | 13:01 |
| hiromotai | hi | 13:01 |
| iwamatsu | Hello | 13:01 |
| alicefm | hi | 13:01 |
| patersonc[m] | Hello | 13:01 |
| jki | let's go | 13:02 |
| pave1 | hi | 13:02 |
| jki | #startmeeting CIP IRC weekly meeting | 13:02 |
| collab-meetbot` | Meeting started Thu Jan 19 13:02:06 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 review | 13:02 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | I don't have any on the list | 13:02 |
| jki | anything missed? | 13:02 |
| pave1 | I guess empty list is a good thing :-). | 13:03 |
| jki | possibly... :) | 13:03 |
| jki | moving on in | 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 | |
| uli | i backported the remaining 4.9 patches to 4.4 | 13:04 |
| masami | This week reported 7 new CVEs and 8 updated CVEs. | 13:04 |
| pave1 | I did reviews on 5.10.163 and 164. | 13:04 |
| iwamatsu | I reviewed 5.10.193 and 194. | 13:04 |
| pave1 | 4.19-rt is released, 5.10-rt hit bug in upstream. | 13:04 |
| jki | 5.10.193?? | 13:05 |
| pave1 | That looks like typo -- 6 vs. 9. | 13:06 |
| jki | 163, I suppose :) | 13:06 |
| jki | anything else? | 13:07 |
| iwamatsu | sorry, 163 and 164. | 13:07 |
| jki | 3 | 13:07 |
| jki | 2 | 13:07 |
| jki | 1 | 13:08 |
| jki | #topic Kernel release status | 13:08 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:08 | |
| jki | -4.4 | 13:08 |
| uli | pavel did the reviews, everything seems ok. i think it's ready to release. | 13:08 |
| pave1 | Yep, two more patches to look at, but lets not hold a release for that. | 13:08 |
| jki | good. -rt would be able to follow? | 13:09 |
| pave1 | I guess the question is "who does the rt"? :-) | 13:09 |
| jki | uli: would you feel ready for that? | 13:10 |
| uli | i haven't looked at it at all yet... | 13:11 |
| uli | next time, maybe? | 13:11 |
| jki | pavel: would you do it again, giving uli some intro? | 13:11 |
| pave1 | jki: Makes sense. There is still series to be backported from 4.9-rt and we'll actually have to start watching 4.14-rt. | 13:13 |
| jki | yep | 13:14 |
| jki | were those trees rather silent rt-wise by now, only integration with stable? | 13:15 |
| pave1 | There were silent for a year, but there are some changes now (hence the backport). It seems to be "just nice to have" and not critical. | 13:15 |
| jki | ok | 13:16 |
| jki | -4.19 | 13:16 |
| jki | I think we are up-to-date here, right? | 13:16 |
| pave1 | I think so. | 13:16 |
| jki | -5.10 | 13:16 |
| jki | -rt release in sight? | 13:17 |
| pave1 | I hit a bug in mainline -rt. | 13:17 |
| jki | uh | 13:17 |
| pave1 | It is currently being discussed, I'm not only one hitting it. | 13:17 |
| jki | ok, then we have a good reason to wait | 13:17 |
| jki | anything else? | 13:18 |
| jki | 3 | 13:18 |
| jki | 2 | 13:18 |
| pave1 | It is assembly on arm64, not too evil but could not figure it out in 5 minutes, either. | 13:18 |
| alicef | 4.19 we are missing the cip release as yesterday we got update from kernel upstream. I think iwamatsu san is currently working on it. | 13:18 |
| jki | indeed! | 13:19 |
| jki | ok | 13:19 |
| iwamatsu | Yes, I am working about it. I will relelase 4.19.y-cip tomorrow. | 13:19 |
| alicef | iwamatsu: thanks | 13:20 |
| jki | good - then move on | 13:21 |
| jki | #topic Kernel testing | 13:21 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:21 | |
| alicef | sent PR to kernelCI for updating the isar-cip-core | 13:21 |
| patersonc[m] | just a couple of things from me | 13:22 |
| patersonc[m] | 1) As I reported in the TSC, 5.10 gitlab CI builds should now include the riscv and qemu-riscv defconfigs | 13:22 |
| patersonc[m] | 2) It sounds like we still need a discussion on testing _all_ of the stable kernel branches | 13:22 |
| alicef | and writing PR for using more cip configs on KernelCI other than 4.19 | 13:23 |
| pave1 | patersonc: Yep. I believe we should start testing 6.1.X -- that's no brainer. | 13:23 |
| patersonc[m] | Thank you alicef | 13:23 |
| pave1 | Testing all the stables would not hurt, either, but in that case I'd like you to take over writing all the "no bugs detected" here to Greg ;-). | 13:24 |
| pave1 | I still plan to watch the results and debug failures, etc. | 13:24 |
| patersonc[m] | I'm for it | 13:25 |
| pave1 | Ok, job is yours :-). | 13:25 |
| jki | I also believe that running them all is not the issue, processing them is | 13:25 |
| pave1 | But maybe more importantly... | 13:26 |
| pave1 | It looks like upstream -rt trees are not tested adequately. | 13:26 |
| pave1 | Could we start testing them, too? In -stable testing, we won't make much difference but here we would | 13:27 |
| jki | just throwing the same tests as for vanilla on them? | 13:27 |
| pave1 | jki: That would be a very good start. | 13:28 |
| patersonc[m] | We can start testing -rt stable | 13:28 |
| pave1 | That would be great. | 13:29 |
| jki | then let's go - but if we are multiplying CI times, just make sure to warn the TSC about the costs ;) | 13:29 |
| patersonc[m] | Okay | 13:29 |
| jki | or can we also leverage kernelci for that? | 13:30 |
| patersonc[m] | Potentially | 13:31 |
| patersonc[m] | Maybe they are already testing -rt I need to check | 13:31 |
| patersonc[m] | If they are, then it's a question of whether we also want to test it with our set of configs | 13:31 |
| jki | would be good to know, to foxus on the real gaps | 13:31 |
| pave1 | I'd suggest testing 6.1.X and -rt on our infrastructure. | 13:32 |
| pave1 | We already know there's a gap in 5.10-rt testing: it did not build on arm64 at all. | 13:32 |
| patersonc[m] | https://linux.kernelci.org/job/rt-stable/ | 13:32 |
| patersonc[m] | So yes, they already test -rt stable | 13:32 |
| pave1 | ...and it took 3 days for person from TI to notice. | 13:32 |
| patersonc[m] | But whether the RT project monitor the build/test reports is another thing | 13:33 |
| jki | evaluating reports is the bottleneck again... | 13:33 |
| patersonc[m] | 5.10 is reported to fail for Arm64: https://linux.kernelci.org/build/rt-stable/branch/v5.10-rt/kernel/v5.10.162-rt78/ | 13:33 |
| patersonc[m] | So usual story, lots of people building & testing things, not so many looking at the results :P | 13:34 |
| pave1 | jki: Yep, kernelci got that, but nobody noticed. It is the same fail: https://linux.kernelci.org/build/id/63c57fa09c4841bd961d39cd/logs/ | 13:34 |
| jki | at least the respective -rt stable maintainer should cross-check, I would say | 13:35 |
| jki | or should be subscribed | 13:35 |
| pave1 | That's not the way it works, I'm afraid. | 13:35 |
| patersonc[m] | Does the RT project have some sort of RC release? | 13:36 |
| pave1 | patersonc: I'm sure they did _some_ kind of -rc at least occassionaly. I'm not sure if they do it for every release. | 13:37 |
| patersonc[m] | Okay | 13:37 |
| patersonc[m] | Obviously that would be the best thing to test, but it's not so useful if it's not always done | 13:37 |
| pave1 | There are differnent people maintaining different stable-rt branches, so their workflows may differ. | 13:38 |
| jki | then we may have to help with reporting - once again | 13:38 |
| pave1 | Yes, that would be a good thing to do. | 13:39 |
| jki | I'll check internally what our group may contribute here - was on my mid-term plan anyway | 13:42 |
| jki | anything else on testing? | 13:43 |
| patersonc[m] | Not from me | 13:44 |
| jki | who will take the AI for enbling more stable trees in our lab now? | 13:44 |
| patersonc[m] | I will | 13:45 |
| jki | perfect, thanks! | 13:45 |
| jki | then moving on.... | 13:45 |
| jki | 3 | 13:45 |
| pave1 | I believe we'll also need configs. | 13:45 |
| jki | 2 | 13:45 |
| pave1 | ...but using configs for older version we are already testing should work well enough for a start. | 13:46 |
| patersonc[m] | pave1: ah good point | 13:46 |
| jki | likely | 13:46 |
| jki | but having a look at the resulting diff of the .configs would not be bad | 13:46 |
| jki | now moving on in... | 13:48 |
| jki | 3 | 13:48 |
| jki | 2 | 13:48 |
| jki | 1 | 13:48 |
| jki | #topic AOB | 13:48 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:48 | |
| jki | I'm on vacation next Thursday | 13:48 |
| jki | would need a substitute | 13:48 |
| pave1 | I can do it I guess. | 13:49 |
| jki | thanks! | 13:49 |
| jki | anything else? | 13:50 |
| jki | 3 | 13:50 |
| jki | 2 | 13:50 |
| jki | 1 | 13:50 |
| jki | #endmeeting | 13:51 |
| collab-meetbot` | Meeting ended Thu Jan 19 13:51:00 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:51 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/01/cip.2023-01-19-13.02.html | 13:51 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/01/cip.2023-01-19-13.02.txt | 13:51 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/01/cip.2023-01-19-13.02.log.html | 13:51 |
| *** 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:51 | |
| pave1 | Thank you! | 13:51 |
| uli | thanks | 13:51 |
| iwamatsu | Thank you | 13:51 |
| alicef | thanks | 13:51 |
| jki | thank you all! | 13:51 |
| hiromotai | Thanks | 13:51 |
| masami | thank you | 13:51 |
| *** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:c18b:3221:d756:217b> has quit IRC (Quit: Leaving) | 13:51 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:51 | |
| patersonc[m] | Cheers | 13:52 |
| *** uli <uli!~uli@175.176.15.140> has left #cip (Leaving) | 13:52 | |
| *** jki <jki!~jki@88.215.103.113> has quit IRC (Quit: Leaving) | 13:53 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection) | 15:39 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 15:42 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 17:14 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 19:43 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds) | 22:45 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!