Thursday, 2024-02-22

« Wednesday, 2024-02-21 Index Friday, 2024-02-23 »
*** rajm <rajm!~robert@82.27.50.32> has joined #cip03:30
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:49
*** frieder <frieder!~frieder@i577B9367.versanet.de> has joined #cip07:42
*** jki <jki!~jki@62.156.206.36> has joined #cip12:58
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has joined #cip12:59
jkihi folks!13:00
pave1hi!13:00
masamihello13:00
ulihello13:00
iwamatsuhello13:01
patersoncHello13:02
jkiok... time to start13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Feb 22 13:02:32 2024 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 review13:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki- prepare blog entry on SLTS kernel state and challenges [Jan]13:02
jkinot yet happy, in a rewrite...13:03
jkiother AIs?13:03
jki313:03
jki213:03
jki113:03
jki#topic Kernel maintenance updates13:03
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:03
pave1I was reviewing 6.1.78 and .79.13:03
ulidone with 6.1.75, doing 4.4 next13:03
masamiThis week reported 15 new CVEs and 2 updated CVEs.13:03
iwamatsuI reviewed 6.1.78, and I am preparating 6.1.y-cip release13:04
jkiother topics here?13:06
jki513:06
jki413:06
jki313:06
jki213:06
jki113:06
jki#topic Kernel release status13:06
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:06
jkiso, only 6.1 is currently late13:07
jkiany blockers for it?13:07
iwamatsuYes, I am working it now.13:07
iwamatsuno blockers13:07
jkigood13:07
jkiany other issues upcoming?13:08
jki513:08
jki413:08
jki313:08
jki213:08
jki113:08
jki#topic Kernel testing13:08
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:08
patersoncHello13:09
patersoncSorry I was away last week13:09
arisutsorry no updates this week from me13:09
patersoncThere was some discussion on stopping kernelci emails going to cip-dev - I've actioned this now: https://github.com/kernelci/kernelci-jenkins/pull/13813:09
patersoncShould come into effect on Monday13:09
patersoncThey will go to the test-results ML instead13:10
arisutstill need to investigate the yaml files used by kernelci core api13:10
patersoncThanks arisut13:10
arisutpatersonc: thanks13:11
patersoncjki - some boards have been failing health-checks in the muc lab for a bit - could you get someone to take a look for me?13:11
patersonchttps://lava.ciplatform.org/scheduler/worker/lab-cip-siemens-muc13:11
jkisure, will check13:11
patersoncThanks13:11
patersoncIs the CIP release test report email still working okay for everyone?13:12
uliworks for me13:12
patersoncIf anyone wants to report the same on a build before the "release" email goes out, let me know. It would be nicer to have it as part of the actual release process13:13
jkiwhat is practically needed to move the report earlier?13:14
patersoncAll I'm doing is looking at the squad gui. I guess it takes an hour or so from push to kernel.org/gitlab to get results onto squad?13:15
patersoncMaybe more than an hour - I'm not sure tbh13:15
pave1It requires more coordination.13:15
jkiso, you would need a ping from a maintainer ready to release13:16
patersoncYea13:16
pave1Best option from my side would be -- we mail qa team,13:16
pave1qa team does the final announce when no problems are detected.13:17
patersoncOr, go to the squad dashboard, click on the build with the sha you're releasing, if there are no issues, release.13:18
patersonce.g. https://squad.ciplatform.org/linux-cip/linux-4.19.y-cip/build/4.19.306-cip107_800dfc28d/ shows no test failures13:18
jkihttps://lava.ciplatform.org/scheduler/worker/lab-cip-siemens-muc should be fine again - power control hick-up13:18
patersoncThanks jki13:18
jkiQuirin did it :)13:19
pave1Well -- if squad now works well enough, we can do it.13:19
pave1What about -- keep the same system for now13:19
pave1and we evaluate squad in next few weeks?13:20
jkior do one pilot, but maybe not with a late release ;)13:20
patersonceither, or, I don't mind :)13:20
jkiwhat would "we evaluate" concretely mean? who would do what?13:21
pave1next time i do releade I look at squad, and if I13:22
pave1can understand it, we do the switch13:22
arisutswitch from what?13:23
pave1Switch fromcurrent system where qa13:23
pave1team reports results over email after release.13:24
arisutcurren system you are referring to is the patersonc mail review?13:24
pave1yep.13:24
arisutso if I understand correctly if you can work with squad, review mail are no needed anymore?13:24
jkipoint is that all maintainer should check that for themselves before we do a general decision13:25
pave1if the squad can do clear yes/no decision, we can do that.13:25
patersoncOkay13:27
patersoncLet's see how it goes. Just shout if there are any uncertancies/issues13:27
pave1Ok.13:27
iwamatsuOK13:27
pave1In last meetings we talked about lot of testing13:28
pave1mails on cip-dev.13:28
pave1Can we turn them off?13:28
arisutpatersonc: currently squad is also getting kernelci information? or just discarding it?13:28
patersoncarisut: Currently the kernelCI testing isn't feeding back into SQUAD, it's a TODO to work that out13:29
patersoncpave1: As I said earlier, there's already an MR merged to stop the kernelCI emails going to cip-dev - they will move to the cip-testing-results ML13:30
pave1aha, ok, thanks.13:30
jkigood - further testing topics?13:31
jkidid you see Daniels -rt kernelci improvements?13:31
patersoncNope13:31
jkihttps://github.com/kernelci/kernelci-core/pull/239713:32
jkiadd you do CC ;)13:32
patersoncoh yes, sorry13:32
jkiplease provide further feedback if you have any - is that helpful? is more is needed?13:34
patersoncWill do13:34
patersoncThanks13:34
jkipavel: also addressing you13:34
jkigood13:34
pave1I'll take a look at the github link.13:35
jkiother testing topics?13:35
jki513:36
jki413:36
jki313:36
jki213:36
jki113:36
jki#topic AOB13:36
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:36
jkianything else for today?13:37
jki513:38
jki413:38
jki313:38
jki213:38
jki113:38
jki#endmeeting13:38
collab-meetbot`Meeting ended Thu Feb 22 13:38:12 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:38
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-22-13.02.html13:38
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-22-13.02.txt13:38
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/02/cip.2024-02-22-13.02.log.html13:38
*** 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:38
pave1Thank you!13:38
jkithanks, all!13:38
ulithanks13:38
iwamatsuthank you13:38
masamithank you13:38
*** masami <masami!~masami@FL1-219-107-72-235.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:38
arisutthanks13:39
patersoncarisut: Is it possible to get notifications from the new kernelCI API?13:39
patersonce.g. when a test job is completed13:40
*** jki <jki!~jki@62.156.206.36> has quit IRC (Remote host closed the connection)13:59
*** frieder <frieder!~frieder@i577B9367.versanet.de> has quit IRC (Remote host closed the connection)15:24
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)17:01
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Ping timeout: 264 seconds)20:49
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.92> has joined #cip20:50
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.92> has quit IRC (Ping timeout: 256 seconds)21:01
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #cip21:01
*** rajm <rajm!~robert@82.27.50.32> has quit IRC (Ping timeout: 260 seconds)22:00
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Quit: Konversation terminated!)23:09
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #cip23:09
« Wednesday, 2024-02-21 Index Friday, 2024-02-23 »

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