| *** lfam <lfam!~lfam@user/lfam> has quit IRC | 04:37 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 07:18 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:51 | |
| *** toscalix_ <toscalix_!~toscalix@80.31.249.68> has joined #cip | 09:03 | |
| *** toscalix_ <toscalix_!~toscalix@80.31.249.68> has quit IRC | 09:03 | |
| *** toscalix_ <toscalix_!~toscalix@80.31.249.68> has joined #cip | 09:03 | |
| *** toscalix__ <toscalix__!~toscalix@90.167.167.99> has joined #cip | 09:30 | |
| *** toscalix_ <toscalix_!~toscalix@80.31.249.68> has quit IRC | 09:34 | |
| *** toscalix <toscalix!~toscalix@80.31.249.68> has joined #cip | 09:38 | |
| *** toscalix__ <toscalix__!~toscalix@90.167.167.99> has quit IRC | 09:38 | |
| *** uli <uli!~uli@55d40d81.access.ecotel.net> has joined #cip | 10:46 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip | 12:45 | |
| *** jki <jki!~jki@165.225.27.19> has joined #cip | 12:54 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 12:57 | |
| *** pave1 <pave1!~pavel@88.103.227.175> has joined #cip | 12:59 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:00 |
|---|---|---|
| brlogger | Meeting started Thu Jan 13 13:00:32 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:00 | |
| jki | hi all! | 13:00 |
| uli | hello | 13:00 |
| iwamatsu | hi | 13:00 |
| pave1 | hi | 13:00 |
| masami | hi | 13:00 |
| alicef | hi | 13:00 |
| patersonc[m] | hi | 13:01 |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 13:01 | |
| *** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip | 13:02 | |
| jki | ok, let's get started then | 13:03 |
| jki | #topic AI review | 13:03 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | 1. Provide v3 of kernelci patches for isar-cip-core - alicef | 13:03 |
| alicef | jki thanks for the review. v3 is still not done. bit busy with other work. | 13:04 |
| jki | ok, np. if i should help, let me know | 13:04 |
| jki | 2. Propose tweet on KernelCI-CIP collaboration progress - alicef | 13:04 |
| alicef | patersonc[m]: maybe we can decide here something to write ? | 13:05 |
| patersonc[m] | Probably best. Then the proposal can be sent to Neil for posting | 13:06 |
| alicef | I was thinking something like "check the CIP work on Kernelci https://github.com/orgs/kernelci/projects/11 @kernelci @cip" | 13:06 |
| alicef | I was thinking something like "check the CIP work on Kernelci https://github.com/orgs/kernelci/projects/11 @kernelci @cip_project" | 13:07 |
| patersonc[m] | alicef: We should probably meet to work out the next steps for cip+kernelci as well | 13:07 |
| alicef | yes | 13:07 |
| jki | ok, great | 13:09 |
| jki | 3. Clarify with KernelCI whether CIP maintainers can get accounts - alicef | 13:09 |
| patersonc[m] | What are these accounts for btw? For KernelCI's GitHub? | 13:10 |
| alicef | still working on this probably it will take some time for now. and is part of the kernelci next steps | 13:10 |
| alicef | patersonc[m]: Is actually not account as is possible to do it programmatically | 13:10 |
| alicef | I asked iwamatsu and pave1 to send me a mail with the development branch that they want to be enabled for development but didn't get it yet afaik | 13:11 |
| jki | "Clarify with KernelCI how CIP maintainers can get trigger private builds" | 13:11 |
| jki | better? | 13:11 |
| pave1 | alicef: https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-test | 13:12 |
| alicef | actually the current task is for pavel and iwamatsu to send me a mail with the branch they want to be enabled for developement | 13:12 |
| pave1 | This is what I'm using for testing, and I guess it makes sense to keep testing it. | 13:12 |
| patersonc[m] | jki: Gotcha, thanks | 13:12 |
| alicef | pave1: please send me a mail about this | 13:12 |
| pave1 | ok :-). | 13:12 |
| iwamatsu | alicef: I will do it. | 13:13 |
| patersonc[m] | You can also request branches to be supported as an issue ticket on GitHub: https://github.com/kernelci/kernelci-core/issues/new?assignees=&labels=&template=new-kernel-branch.md&title=Add+branch+BRANCH+from+TREE | 13:13 |
| alicef | pave1: can you make a branch like for-kernelci? | 13:13 |
| alicef | oh right | 13:14 |
| pave1 | alicef: The name of the branch does not really matter, so yes, I guess I can. | 13:14 |
| patersonc[m] | Or https://github.com/kernelci/kernelci-core/issues/new?assignees=&labels=&template=new-kernel-branch.md&title=Add+branch+pavel-for-kernelci+from+cip | 13:14 |
| alicef | probably the best is to follow patersonc[m] link and send a issue to kernelci-core | 13:14 |
| patersonc[m] | alicef or I can action the issue once created | 13:15 |
| alicef | specifing that is a development branch | 13:15 |
| alicef | what you mean by "action the issue" | 13:15 |
| alicef | ? | 13:15 |
| patersonc[m] | Create an MR | 13:16 |
| patersonc[m] | PR | 13:16 |
| alicef | whatever is ok for you | 13:17 |
| alicef | just remember that is a special PR for dealing with development branch | 13:18 |
| alicef | not just enabling it | 13:18 |
| jki | ok, looks like we have (clearer) plan now | 13:19 |
| jki | anything else? | 13:19 |
| jki | 3 | 13:19 |
| jki | 2 | 13:19 |
| jki | 1 | 13:19 |
| jki | #topic Kernel maintenance updates | 13:20 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:20 | |
| pave1 | I was reviewing 5.10.91 and various series on the mailing lists. | 13:20 |
| masami | There are 7 CVEs this week. CVE-2021-4204 hasn't been fixed in the mainline yet. | 13:20 |
| pave1 | Renesas ADC and ethernet patches were applied. Sound needs more work. | 13:20 |
| uli | done with 5.10.87, was going to do 5.10.91... | 13:20 |
| iwamatsu | I reviewed 5.10.91. | 13:20 |
| uli | pave1: what's left to review? | 13:21 |
| pave1 | Everything that should be relevant to us should be done. There's stuff left that scripts marked as irrelevant. I'll mail you with details. | 13:22 |
| uli | ok | 13:22 |
| jki | is the worksplit via wiki now more or less established? | 13:24 |
| pave1 | I'll need to look into it. | 13:26 |
| iwamatsu | it hasn't been split yet./ | 13:26 |
| jki | "old habits", or is there still something not fitting well? | 13:27 |
| iwamatsu | There are duplicate reviews . | 13:29 |
| iwamatsu | allocate it automatically ? | 13:29 |
| jki | that was my idea, but pavel said that splitting has to be "smart", and that might be hard | 13:30 |
| pave1 | Lets see how this works, I'd say. I'll need to start using it. | 13:30 |
| pave1 | Yes, splitting so that related series and related patches across the releases are reviewed by same person makes sense IMO. | 13:31 |
| jki | so, someone needs to take a lead for a new kernel release to do that split | 13:31 |
| jki | and then folks can start reviewing | 13:32 |
| jki | ok, let's put this on recall, I would say | 13:33 |
| jki | anything else for this topic? | 13:33 |
| jki | 3 | 13:34 |
| jki | 2 | 13:34 |
| jki | 1 | 13:34 |
| jki | #topic Kernel testing | 13:34 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:34 | |
| iwamatsu | let's split it when I create the patch list. | 13:34 |
| patersonc[m] | No updates from me RE testing | 13:35 |
| pave1 | For stable kernels, 4.4 and 4.19 are tested, but 5.10 fails to build due to gcc problems. | 13:35 |
| alicef | tomorrow I have a presentation at Linux conf au about CIP and KernelCI | 13:36 |
| alicef | no updates other than this | 13:36 |
| alicef | https://linux.conf.au/schedule/presentation/8/ | 13:36 |
| pave1 | It would be nice to get it fixed, we'll eventually hit it in our testing, too. | 13:36 |
| alicef | patersonc[m]: maybe we can tweet about the presentation https://linux.conf.au/schedule/presentation/8/ | 13:37 |
| iwamatsu | pave1: yes, we need to create a enviromnet for it. And I am working this. | 13:37 |
| pave1 | iwamatsu: Thank you! | 13:38 |
| alicef | also kernelci tweeted about it https://twitter.com/kernelci/status/1481365948363911172 | 13:38 |
| patersonc[m] | alicef: I'll email Neil | 13:38 |
| jki | good - anything else? | 13:40 |
| jki | 3 | 13:40 |
| jki | 2 | 13:40 |
| jki | 1 | 13:40 |
| jki | #topic AOB | 13:40 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:40 | |
| pave1 | There is 4.4.296-rt229 released, and the 4.4-rt releases are quite rare. | 13:41 |
| pave1 | It would be great to get 4.4.296-cip release, so I could do -cip-rt... | 13:41 |
| patersonc[m] | Sounds like a good idea | 13:42 |
| jki | and it should be due as well, one month after the last one | 13:42 |
| iwamatsu | I am going to relase new CIP kernel for 4.4 and 4.19. so I will 4.4.296-cip as 4.4.y cip tree. | 13:43 |
| pave1 | THank you! | 13:44 |
| jki | perfect, thanks! | 13:44 |
| iwamatsu | you are welcome ;-) | 13:44 |
| jki | two topics from my side: | 13:44 |
| jki | 1. does any one know how our chatbot is hosted? | 13:45 |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 13:45 | |
| alicef | I know but I have to check old logs | 13:45 |
| alicef | jki: what you want to know ? | 13:45 |
| alicef | something specific? | 13:46 |
| jki | asking because Codethink is leaving CIP | 13:46 |
| alicef | so we need a new bot ? | 13:46 |
| jki | if they provided it, I don't expect a shutdown, but we may run into troubles when no one recalls who owns it when its broken | 13:47 |
| alicef | I have a similar think on #gentoo-kernel | 13:47 |
| jki | not yet I strongly assume | 13:47 |
| jki | but a plan b might be good to have | 13:47 |
| patersonc[m] | jki: Codethink set up the chatbot etc. | 13:47 |
| alicef | someone here is the maintainer but I cannot recollect the exact name now | 13:47 |
| jki | alicef: if you have information or even contacts about the current setup, please check | 13:47 |
| jki | again, just safety measure | 13:48 |
| jki | ok, topic #2: I'm off next Thursday | 13:49 |
| jki | alicef: would you be so kind to run the show? :) | 13:49 |
| alicef | sure | 13:49 |
| jki | thanks! | 13:49 |
| jki | ok, that's all from my side | 13:50 |
| jki | anything else? | 13:51 |
| jki | 3 | 13:51 |
| jki | 2 | 13:51 |
| jki | 1 | 13:51 |
| jki | #endmeeting | 13:52 |
| brlogger | Meeting ended Thu Jan 13 13:52:02 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:52 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2022/01/cip.2022-01-13-13.00.html | 13:52 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2022/01/cip.2022-01-13-13.00.txt | 13:52 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2022/01/cip.2022-01-13-13.00.log.html | 13:52 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 13:52 | |
| jki | thank you all! | 13:52 |
| pave1 | Thank you, stay safe! | 13:52 |
| uli | thanks | 13:52 |
| alicef | thanks you | 13:52 |
| masami | thank you | 13:52 |
| jki | bye bye | 13:52 |
| patersonc[m] | ttfn | 13:52 |
| iwamatsu | thank you! | 13:52 |
| patersonc[m] | pave1: What kind of build coverage do you want for your CI branch in KernelCI? | 13:52 |
| patersonc[m] | Same Q for iwamatsu | 13:53 |
| patersonc[m] | Generally speaking, a good rule is to build fewer variants for branches that... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/8e6b1a69fd17b75aef086051b2ba496b6b6551ef) | 13:53 |
| *** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC | 13:53 | |
| pave1 | patersonc: Well, the more the better :-). | 13:53 |
| pave1 | patersonc: But similar configuration to what we have currently would be enough. | 13:53 |
| patersonc[m] | Okay | 13:54 |
| patersonc[m] | How often are you expecting to push? | 13:54 |
| pave1 | Normally it is something like once or twice a week. | 13:55 |
| pave1 | But I had pushes in half an hour when I was bisecting an issue. | 13:55 |
| patersonc[m] | FYI: https://github.com/kernelci/kernelci-core/issues/983 | 13:56 |
| pave1 | Ok, I'll take a look. | 13:57 |
| pave1 | I should go, bye for now! | 13:58 |
| *** pave1 <pave1!~pavel@88.103.227.175> has quit IRC | 13:59 | |
| *** jki <jki!~jki@165.225.27.19> has quit IRC | 14:02 | |
| *** uli <uli!~uli@55d40d81.access.ecotel.net> has left #cip | 14:42 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC | 15:04 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC | 15:33 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 18:22 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 18:26 | |
| *** toscalix <toscalix!~toscalix@80.31.249.68> has quit IRC | 19:10 | |
| *** lfam <lfam!~lfam@user/lfam> has joined #cip | 20:31 | |
| *** lfam <lfam!~lfam@user/lfam> has quit IRC | 20:51 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 22:56 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!