IRC logs for #cip for Thursday, 2022-03-24

« Wednesday, 2022-03-23 Index Friday, 2022-03-25 »
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC01:01
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip01:12
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip07:20
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:40
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip08:38
*** toscalix <toscalix!~toscalix@90.166.55.149> has joined #cip09:32
*** toscalix <toscalix!~toscalix@90.166.55.149> has joined #cip09:33
*** toscalix <toscalix!~toscalix@90.166.55.149> has quit IRC12:27
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:37
*** jki <jki!~jki@165.225.24.49> has joined #cip12:48
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip12:49
*** uli <uli!~uli@55d4ae0d.access.ecotel.net> has joined #cip12:50
*** pave1 <pave1!~pavel@88.103.227.177> has joined #cip12:59
jki#startmeeting CIP IRC weekly meeting13:00
brlogger`Meeting started Thu Mar 24 13:00:47 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
collab-meetbotMeeting started Thu Mar 24 13:00:47 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:00
jkihi all13:00
iwamatsuhello13:00
masamihi13:00
josiahHello13:00
ulihello13:01
pave1hi13:01
jkiok, test crew still missing, but let's get started anyway13:05
jki#topic AI review13:05
*** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:05
jki1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm13:05
jkino one around to answer this, I assume13:05
jkiother AIs?13:06
jki313:06
jki213:06
jki113:06
jki#topic Kernel maintenance updates13:06
*** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:06
pave1I have reviewed patches for 5.10.108.13:07
ulireviewed 5.10.10613:07
masamiThis week reported 8 new CVEs.13:07
masamiThey are not so critical vulnerability.13:07
iwamatsuI reviewed 5.10.108.13:07
pave1I did work on 4.4-stable branch. It should be up-to-date with 4.9.305, and I believe we should do a -cip release to get more eyes on it and test the process.13:08
jkisounds good to me13:09
pave1I do believe we should trim down kernel configs. There's a lot of stuff that does not make sense because someone copied defconfig, and we have enabled it as modules.13:10
jkihow to approach that?13:10
iwamatsupave1: I also replied to your email, do you have any thoughts on the -st tree release tags?13:10
pave1jki: Dunno. Ask for explanation for things that look unneeded in the config, and disable option if explanation is not given?13:12
pave1jki: Other possibility would be to ask if we have tests to cover specific config option, and disable it if not.13:12
jkiI'm afraid the test coverage widely relies on kernelci & Co.13:13
pave1iwamatsu: I have added localversion-st to the -st tree. You probably want to remove that before releasing -cip.13:14
jkiwhat worked best so far was asking if certain switches could be dropped13:14
pave1jki: I'm pretty sure kernelci does not have the crazier options enabled.13:15
jkimake it concrete, then we can iterate over that13:16
pave1jki: But yes, we can continue asking. See the ...Disabling XEN in our configs (used by QEMU and Rene... thread on cip-members.13:16
pave1jki: I guess I'd like to get consensus that yes, we need configuration to be trimmed down, that it is okay to do and that we'll continue doing it.13:17
jkiI wouldn't disagree with that13:17
jkiI can add this as an item to present /remind folks of on our ext-TSC agenda13:18
pave1jki: Good :-). Can you state that on the members list? I don't feel comfortable arguing there.13:18
iwamatsupave1: Well, are you planning to tag the linux-4.4.y-st tree for release? For example linux-4.4.y-st-st5.13:19
pave1jki: But maybe ext-TSC agenta makes sense, too.13:19
jkipavel: we can do both, but let's start with that meeting13:19
pave1jki: Ok, thanks!13:20
pave1iwamatsu: Yes, I guess I should do the tags, too.13:20
pave1iwamatsu: I propose tagging it as "v4.4-st5" ...?13:20
patersonc[m]Is my IRC broken? Or has this meeting stalled?13:21
iwamatsupave1: I got it. I think it will probably be such a tag.13:21
pave1Ok. Let me do tags in v4.4-stX form.13:22
iwamatsuthank you!13:22
ulipatersonc[m]: i think it's your irc13:22
alicefmHi13:22
alicefmSame here13:23
pave1(To be clear. I'll do v4.4-st5, not v4.4.302-st5, as .302 would just be repeated everywhere).13:23
alicefPatersonMatrix bridge is stalled13:24
jkihow would 4.4-cip be tagged, what numbers will be incremented there?13:25
pave1I guess I'll also do -st-next as doing development on -st branch is confusing.13:25
pave1jki: I thought it would be v4.4-cipX or v4.4.302-cipX.13:26
jkican be risky to change the naming scheme13:27
patersonc[m]Or -st-rc?13:27
jkiso the second option might be safer13:27
patersonc[m]To follow the same convention as other cip branches13:27
pave1-st-rc works for me, too.13:27
pave1jki: Yes, I guess we can stay with v4.4.302-cipX.13:28
iwamatsuhmm, what should we do with the CIP release tag? v4.4-st5-cip69?13:29
pave1iwamatsu: I'd just tag it as v4.4.302-cipX.13:29
pave1iwamatsu: If someone wants to know what -stX it is based on, it will be in git history.13:30
jkicontinuity, also in naming13:31
jkiok, further topics here?13:33
iwamatsuIf we want to release it, merge -st tree into -cip tree and set the tag to 4.4.302-cipX+1. is this correct understanding?13:33
pave1iwamatsu: Correct, AFAICT.13:34
iwamatsupave1: OK13:34
pave1(You'll need to delete localversion-st, so that we get correct version info).13:34
iwamatsuYes, I think so.13:35
jkiso... moving on in...13:36
jki313:36
jki213:36
jki113:36
jki#topic Kernel testing13:36
*** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:36
jkipatersonc[m]: do we have news on the AI?13:38
alicefThe pull request i sent about preempt rt as been updated and take over with Guillermo13:39
alicefWith Gtucker pull request13:40
jkialicef: what was that about?13:40
alicefAdding preempt rt test on KernelCI13:41
alicefAlso for cip rt branches13:41
jkiah, great13:41
jkihttps://github.com/kernelci/kernelci-core/pull/1094 - right?13:42
alicefYes that's it13:43
jkihow sophisticated are rt tests in kernelci already?13:44
alicefWhat do you mean by sophisticated?13:45
jkiwhat do they run, roughly, for how long? already recording latencies or "just" stability topics?13:46
jki"it's fine if it boots" is surely not enough here ;)13:48
alicefThey use rt-test and do some round of cyclic test13:50
alicefcyclictest measures event latency in Linux kernel by13:50
alicefmeasuring the amount of time that passes between when a timer13:50
alicefexpires and when the thread which set the timer actually13:50
alicefruns.13:50
jkiyes, sure13:51
jkibut you need to run that longer than usual tests, you need to run stress in parallel13:51
jkiand we eventually also need an I/O loop test13:51
pave1cyclictest is kind of default for realtime testing, yes.13:51
pave1And it is a bit of art:13:51
jkiI'm asking as I could try to push that topic via some colleagues, looking into status quo and possible improvements13:52
pave1a) Not all systems are suitable; you'll get failures on many machines because firmware is broken.13:52
pave1b) You have to load system a bit, but not unrealistically so.13:52
alicefhttps://github.com/kernelci/kernelci-core/issues/47413:53
jki"a bit" is relative to what you want to show - usually, you load a lot13:53
alicefIs the discussion about rt tests implementation13:53
jkiand vary that13:53
pave1jki: Well, you want to test basic functionality. You don't want to test OOM killer and serial console, for example.13:54
jkipavel: if you want to test out numbers, you need to do more than that13:55
alicefWe are adding what is used on mainline to cip13:55
jkipavel: for basic stability tests, that is fine, yes13:55
jkithat is definitely a valuable start!13:56
alicefMaybe write in the KernelCI pr or open a new issue if there are suggestions13:58
jkisure, will do - need an overview first13:59
jkiother testing topics?13:59
alicefNot that I know about.14:00
jkithen move on in14:00
jki314:00
jki214:00
jki114:00
jki#topic AOB14:00
*** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"14:00
jkiI would need a substitute next Thursday (OOO)14:01
alicefI asked patersonc[m] if he can help out with the already opened KernelCI pr as I'm busy in this days.14:02
alicefIf anyone is interested or want to help out this is the current KernelCI situation on cip https://github.com/orgs/kernelci/projects/1114:04
pave1jki: I guess I can send the email and operate the chatbot.14:06
pave1jki: Is anything else required?14:06
jkipavel: that should be enough, TIA!14:06
pave1jki: No problem :-).14:06
jkiok - anything else for today?14:08
jki314:09
jki214:09
jki114:09
jki#endmeeting14:09
brlogger`Meeting ended Thu Mar 24 14:09:12 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:09
brlogger`Minutes:        https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-24-13.00.html14:09
brlogger`Minutes (text): https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-24-13.00.txt14:09
brlogger`Log:            https://irclogs.baserock.org/meetings/cip/2022/03/cip.2022-03-24-13.00.log.html14:09
*** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"14:09
collab-meetbotMeeting ended Thu Mar 24 14:09:12 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:09
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-24-13.00.html14:09
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-24-13.00.txt14:09
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/03/cip.2022-03-24-13.00.log.html14:09
jkithanks, all!14:09
jkihave a nice day14:09
pave1Thank you!14:09
ulithanks14:09
iwamatsuthank you!14:09
masamithanks14:09
alicefThanks14:09
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC14:10
*** pave1 <pave1!~pavel@88.103.227.177> has quit IRC14:11
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:11
*** jki <jki!~jki@165.225.24.49> has quit IRC14:12
*** uli <uli!~uli@55d4ae0d.access.ecotel.net> has left #cip14:14
*** toscalix <toscalix!~toscalix@90.167.31.107> has joined #cip14:14
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC15:08
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip15:25
*** toscalix <toscalix!~toscalix@90.167.31.107> has quit IRC16:04
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC17:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC20:11
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip20:32
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC20:45
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC22:57
« Wednesday, 2022-03-23 Index Friday, 2022-03-25 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!