| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 02:30 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:51 | |
| *** rajm <rajm!~robert@82.27.50.32> has joined #cip | 06:51 | |
| *** tobsch <tobsch!~quassel@195.145.170.192> has joined #cip | 08:54 | |
| *** tobsch <tobsch!~quassel@195.145.170.192> has quit IRC (Ping timeout: 268 seconds) | 09:30 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Quit: Connection closed) | 09:34 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip | 09:35 | |
| *** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip | 09:35 | |
| *** tobsch <tobsch!~quassel@195.145.170.202> has joined #cip | 09:42 | |
| *** arisut 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/" | 12:02 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 12:51 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 12:55 | |
| *** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip | 12:55 | |
| *** tobsch <tobsch!~quassel@195.145.170.202> has quit IRC (Read error: Connection reset by peer) | 12:57 | |
| *** jki <jki!~jki@46.128.89.130> has joined #cip | 13:01 | |
| jki | hi all! | 13:01 |
|---|---|---|
| sietze | Hello! | 13:01 |
| *** arisut 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:01 | |
| pave1 | hello! | 13:01 |
| uli | hello | 13:01 |
| *** arisut 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:01 | |
| arisut | Hi | 13:01 |
| *** arisut 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:01 | |
| iwamatsu | hi | 13:02 |
| *** tobsch <tobsch!~quassel@62.156.206.52> has joined #cip | 13:02 | |
| jki | did you already start? or is our bot still running? | 13:02 |
| arisut | No one started yet | 13:03 |
| jki | ok... | 13:03 |
| jki | then let's do this now | 13:03 |
| jki | #startmeeting CIP IRC weekly meeting | 13:03 |
| collab-meetbot` | Meeting started Thu Dec 14 13:03:31 2023 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:03 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:03 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:03 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| arisut | Waiting for you h | 13:03 |
| jki | #topic AI review | 13:03 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:03 | |
| jki | - prepare blog entry on SLTS kernel state and challenges [Jan] | 13:03 |
| jki | still need to do that... | 13:03 |
| arisut | Just fixing the meeting date on the bot topic | 13:04 |
| jki | ah, ok | 13:04 |
| jki | any other to-dos from last time? | 13:04 |
| jki | 5 | 13:04 |
| jki | 4 | 13:04 |
| jki | 3 | 13:04 |
| jki | 2 | 13:04 |
| jki | 1 | 13:04 |
| jki | #topic Kernel maintenance updates | 13:04 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| pave1 | I was doing reviews, 6.1.66. | 13:05 |
| uli | i'm reviewing 6.1.68 | 13:05 |
| iwamatsu | I reviewd 6.1.65 and 66. | 13:06 |
| jki | anything else? | 13:07 |
| *** tobsch <tobsch!~quassel@62.156.206.52> has quit IRC (Ping timeout: 268 seconds) | 13:07 | |
| *** tobsch_ <tobsch_!~quassel@195.145.170.152> has joined #cip | 13:07 | |
| jki | any further fallouts from recent backports? ;) | 13:08 |
| pave1 | Well, we have both .67 and .67-rt, but they only fix single wifi issue and I don't believe it applies to us. | 13:08 |
| jki | because we don't have the feature enabled in our configs, or why? | 13:09 |
| pave1 | Because wifi is usually not used heavilly in industrial configs. | 13:09 |
| jki | but do we have this config enabled or not for 6.1? | 13:10 |
| pave1 | I'll take a look. | 13:10 |
| jki | and was that issue a fatal failure for all wifi scenarios or just for some= | 13:10 |
| jki | ? | 13:10 |
| pave1 | I believe it is something like "blocks reboot". I'll take another look. | 13:11 |
| pave1 | It is not "eats filesystem" or "provides remote root". | 13:12 |
| jki | yeah, that is definitely more critical | 13:12 |
| jki | ok | 13:12 |
| jki | anything else on maintenance? | 13:13 |
| jki | 5 | 13:13 |
| jki | 4 | 13:13 |
| jki | 3 | 13:13 |
| jki | 2 | 13:13 |
| jki | 1 | 13:13 |
| jki | #topic Kernel release status | 13:13 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:13 | |
| jki | 4.4 | 13:13 |
| iwamatsu | https://lore.kernel.org/cip-dev/TYVPR01MB11245314D12E5E87434FA82C0928CA@TYVPR01MB11245.jpnprd01.prod.outlook.com/ | 13:13 |
| iwamatsu | Date the data is created: Thu Dec 14 12:57:00 PM UTC 2023 | 13:14 |
| iwamatsu | linux-4.4.y-cip: interval 30 day | 13:14 |
| iwamatsu | latest version release date: Mon Dec 11 02:40:37 AM UTC 2023 | 13:14 |
| iwamatsu | limit date: Wed Jan 10 02:40:37 AM UTC 2024 | 13:14 |
| jki | oh, didn't reach my inbox | 13:14 |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-4.4.y-cip-rt: interval 60 day | 13:14 |
| iwamatsu | latest version release date: Thu Oct 19 03:30:18 PM UTC 2023 | 13:14 |
| iwamatsu | limit date: Mon Dec 18 03:30:18 PM UTC 2023 | 13:14 |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-4.19.y-cip: interval 30 day | 13:14 |
| iwamatsu | latest version release date: Thu Dec 7 05:37:21 PM UTC 2023 | 13:14 |
| iwamatsu | limit date: Sat Jan 6 05:37:21 PM UTC 2024 | 13:14 |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-4.19.y-cip-rt: interval 60 day | 13:14 |
| iwamatsu | latest version release date: Wed Oct 18 10:02:27 AM UTC 2023 | 13:14 |
| iwamatsu | limit date: Sun Dec 17 10:02:27 AM UTC 2023 | 13:14 |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-5.10.y-cip: interval 30 day | 13:14 |
| iwamatsu | latest version release date: Thu Nov 23 11:51:14 AM UTC 2023 | 13:14 |
| iwamatsu | limit date: Sat Dec 23 11:51:14 AM UTC 2023 | 13:14 |
| *** tobsch_ <tobsch_!~quassel@195.145.170.152> has quit IRC (Ping timeout: 260 seconds) | 13:14 | |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-5.10.y-cip-rt: interval 60 day | 13:14 |
| iwamatsu | latest version release date: Thu Nov 23 06:12:31 PM UTC 2023 | 13:14 |
| iwamatsu | limit date: Mon Jan 22 06:12:31 PM UTC 2024 | 13:14 |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-6.1.y-cip: interval 15 day | 13:14 |
| iwamatsu | latest version release date: Mon Dec 11 11:00:07 AM UTC 2023 | 13:14 |
| iwamatsu | limit date: Tue Dec 26 11:00:07 AM UTC 2023 | 13:14 |
| *** tobsch <tobsch!~quassel@62.156.206.52> has joined #cip | 13:14 | |
| iwamatsu | Status: On track | 13:14 |
| iwamatsu | linux-6.1.y-cip-rt: interval 30 day | 13:15 |
| iwamatsu | latest version release date: Mon Dec 11 07:08:30 PM UTC 2023 | 13:15 |
| iwamatsu | limit date: Wed Jan 10 07:08:30 PM UTC 2024 | 13:15 |
| iwamatsu | Status: On track | 13:15 |
| jki | nice | 13:15 |
| iwamatsu | I put a script to https://gitlab.com/cip-project/cip-kernel/lts-commit-list/-/blob/master/bin/cip-release-term.sh | 13:15 |
| pave1 | 4.19-cip-rt is next; I seen -rt-rc, so hopefully coordination will be easy. | 13:15 |
| jki | we do not need to go through the kernels individually anymore then | 13:15 |
| jki | we could only focus on issues | 13:16 |
| jki | if any | 13:16 |
| jki | maybe I can try to run that script upfront next time | 13:16 |
| jki | include the output into the reminder | 13:17 |
| jki | good | 13:17 |
| jki | anything further to discuss in this context? | 13:17 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic Kernel testing | 13:17 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| arisut | Nothing new for me | 13:18 |
| arisut | Trying to test the new kernelci api | 13:19 |
| arisut | And checking what we can do with it | 13:19 |
| pave1 | Aha, thanks for remainder. I seen announcement twice, but I should take a look, too. | 13:20 |
| jki | any news from SQUAD? | 13:21 |
| sietze | Yes! | 13:21 |
| sietze | SQUAD Reporting has now gone live: https://squad.ciplatform.org/ | 13:21 |
| sietze | Everybody is invited to have a look and see how it fits their needs | 13:22 |
| jki | linux-cip vs cip-kernel - hmm.... | 13:22 |
| sietze | Well, the latter was for testing purposes | 13:22 |
| sietze | I shall remove that in due time | 13:22 |
| jki | ok, thought you wanted to use it for testing also in the future | 13:23 |
| jki | then it's fine | 13:23 |
| sietze | I think I can hide it and avoid such questions in the future ;-) | 13:23 |
| sietze | Anyway, we would like to have feedback | 13:23 |
| jki | now, how to make use of this - some simple example? | 13:24 |
| jki | is something like this usefull (compare builds)? https://squad.ciplatform.org/_/comparebuilds/?&baseline=5.10.191-cip38_a10a81410&target=5.10.194-cip39_83aa48649&comparison_type=test&project=cip-kernel%2Flinux-5.10.y-cip | 13:26 |
| sietze | One can show the overall results of test suites vs environments (defconfig + device) | 13:26 |
| sietze | Eg https://squad.ciplatform.org/linux-cip/linux-5.10.y-cip/build/5.10.204-cip41_c43d7b7bb/?failures_only=false&results_layout=table#!#test-results | 13:26 |
| sietze | One can see the history of a given test case vs builds and devices/defonfigs | 13:27 |
| sietze | Eg https://squad.ciplatform.org/_/comparetest/?project=18&suite=spectre-meltdown-checker-test&test=CVE-2018-12126 | 13:28 |
| sietze | And there's a lot of more data hidden in there | 13:28 |
| sietze | The questions is, if the overviews that SQUAD now presents are useful for the kernel developers | 13:29 |
| pave1 | Okay. Can someone go through data, and select "this went wrong, this is bad, we need to fix this" example? | 13:29 |
| pave1 | Then we fix the example and go through next example? | 13:29 |
| jki | will hunter work on this? | 13:30 |
| sietze | Yes, he already started | 13:30 |
| jki | great! | 13:31 |
| sietze | But we also need to know what exactly developers would like to see reported | 13:31 |
| sietze | Of course Chris, Hunter and I have our ideas, but it would be great to hear what the others would expect of the reporting | 13:31 |
| pave1 | Developers don't know :-). Issues that could hit our users. But we don't have much feedback what cip users are doing with the kernel. | 13:32 |
| sietze | But what do you expect when looking at the test results? | 13:34 |
| pave1 | Well, green tick for working kernels and red cross for broken kernels would be nice :-). | 13:35 |
| sietze | :-D | 13:35 |
| sietze | Well squad will give you a lot of green ticks and red crosses | 13:36 |
| sietze | I can give you that ;-) | 13:36 |
| pave1 | Well. | 13:37 |
| sietze | Using Hunter's work, we have the possibility to add custom reports on top of what SQUAD already does | 13:37 |
| pave1 | I don't have example nearby, but IMO good example is how stable kernel works. | 13:37 |
| pave1 | Greg acts as a developer, various labs act as testers. | 13:38 |
| pave1 | When they hit a bug, they report what config broke, and then work together to locate the failure. | 13:38 |
| pave1 | I can dig up mail threads from the area. | 13:39 |
| sietze | That could be helpful, but maybe a dedicated meeting would be more efficient here | 13:40 |
| pave1 | But I believe best start would be Q&A team watching the results, and telling us "everything ok" or "we see this, you broke it, you fix it". | 13:40 |
| sietze | Ok | 13:41 |
| sietze | Does it make sense to have dedicated meeting on this, with the QA Team and other involved parties? | 13:41 |
| sietze | With the current information I have now, I am unsure where to improve our reports to fit CIP needs | 13:42 |
| pave1 | I'd preffer to get single good bug report on cip-dev, first. | 13:42 |
| pave1 | But of course, we can do the meeting. | 13:42 |
| sietze | Whom should we invite? | 13:43 |
| sietze | pavel, patersonc, hunter, ...? | 13:43 |
| pave1 | jki, uli, iwamatsu. | 13:44 |
| jki | yep | 13:44 |
| sietze | Ok, I'll talk to patersonc and we'll setup the meeting | 13:44 |
| jki | but keep in mind that vacations are coming... | 13:44 |
| sietze | Sure, probably will take place in January | 13:45 |
| jki | meanwhile, if anyone wants to use the tool to extract and analyse some newly failing tests for a newer kernel... | 13:46 |
| jki | ...just report that to the list | 13:46 |
| sietze | Yes | 13:46 |
| sietze | We already have POC on how to fetch custom results from SQUAD | 13:47 |
| sietze | https://gitlab.com/cip-playground/squad-hacking/cip-test-reports | 13:47 |
| pave1 | You can use -stable kernels as a test data. | 13:48 |
| pave1 | Maybe 20% of -stable-rc kerenls are bad, so you'll get both successes and failures. | 13:48 |
| pave1 | Take a look how other test labs report the results to the lkml. | 13:49 |
| pave1 | ...and best do the same. Currently I'm doing that with test results from a gitlab. | 13:49 |
| pave1 | That's what should be done, best if QA team could do that, not me. | 13:50 |
| *** hunter <hunter!~hunter@dz4g39jdk1snbcfmgpz-4.rev.dnainternet.fi> has joined #cip | 13:50 | |
| jki | sietze: did this help you more? | 13:52 |
| sietze | Yes, a bit, but I still would like to have the meeting, to get a better picture | 13:52 |
| pave1 | Example how this works in "bug found" case is e: Thu, 30 Nov 2023 11:21:34 -0600, From: Daniel Díaz <daniel.diaz@linaro.org>, Subject: Re: [PATCH 5.15 00/69] 5.15.141-rc1 review and following thread on the lkml. | 13:53 |
| jki | sure | 13:53 |
| jki | anything else on testing today? | 13:55 |
| jki | 5 | 13:55 |
| jki | 4 | 13:55 |
| jki | 3 | 13:55 |
| jki | 2 | 13:55 |
| jki | 1 | 13:55 |
| jki | #topic AOB | 13:55 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:55 | |
| jki | vacations... | 13:55 |
| jki | I'll be off next Thursday and the week after as well | 13:56 |
| pave1 | :-). We went from "30 cm of snow" to "ton of mud". | 13:56 |
| jki | just in time for xmas :) | 13:56 |
| hunter | it's like a blizzard in here sorry for being late! | 13:56 |
| pave1 | I should be available on Dec 21, unsure (probably not) about Dec 28 | 13:57 |
| pave1 | Well, but at least we did have snow this winter! :-) | 13:57 |
| jki | who can take over next week then? | 13:57 |
| hunter | I agree, not looking forward to the slush afterwards. | 13:57 |
| jki | and should we keep the 28th? | 13:58 |
| hunter | I can join for that date no problem. | 13:58 |
| uli | i won't be here on the 28, though | 13:58 |
| pave1 | I can control the bot on Dec 21 . | 13:59 |
| jki | great, thanks | 13:59 |
| arisut | thanks | 13:59 |
| iwamatsu | I will not be able to participate on the 28th. | 13:59 |
| jki | maybe you want to decide next week then what to do with the 28th | 13:59 |
| pave1 | -pavel, -iwamatsu, -uli, -jki. It is quite close to Year end so I'd assume we'd cancel it. | 14:00 |
| jki | ok | 14:00 |
| arisut | ok | 14:00 |
| iwamatsu | +1 | 14:00 |
| jki | any other things for today? | 14:00 |
| jki | 5 | 14:01 |
| jki | 4 | 14:01 |
| jki | 3 | 14:01 |
| jki | 2 | 14:01 |
| jki | 1 | 14:01 |
| jki | #endmeeting | 14:01 |
| collab-meetbot` | Meeting ended Thu Dec 14 14:01:24 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:01 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-14-13.03.html | 14:01 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-14-13.03.txt | 14:01 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/12/cip.2023-12-14-13.03.log.html | 14:01 |
| *** 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/" | 14:01 | |
| sietze | Thank you! | 14:01 |
| pave1 | Thank you, happy holidays! | 14:01 |
| arisut | thanks | 14:01 |
| jki | happy holidays, everyone! | 14:01 |
| hunter | Thanks everyone and happy holidays everyone! | 14:01 |
| uli | thank you | 14:01 |
| iwamatsu | thank you! happy holidays | 14:01 |
| sietze | Enjoy the holidays! | 14:01 |
| *** hunter <hunter!~hunter@dz4g39jdk1snbcfmgpz-4.rev.dnainternet.fi> has quit IRC (Quit: Konversation terminated!) | 14:02 | |
| *** jki <jki!~jki@46.128.89.130> has quit IRC (Quit: Leaving) | 14:02 | |
| *** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving) | 14:05 | |
| *** rajm <rajm!~robert@82.27.50.32> has quit IRC (Quit: Konversation terminated!) | 15:49 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 15:52 | |
| *** rajm <rajm!~robert@82.27.50.32> has joined #cip | 15:54 | |
| *** tobsch <tobsch!~quassel@62.156.206.52> has quit IRC (Read error: Connection reset by peer) | 16:26 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip | 18:06 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed) | 19:09 | |
| *** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:16e7:fef0:afb2:c84b> has joined #cip | 19:46 | |
| *** tobsch <tobsch!~quassel@2a02:810d:603f:fe38:16e7:fef0:afb2:c84b> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 19:53 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip | 20:16 | |
| *** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 268 seconds) | 22:48 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds) | 22:48 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!