Thursday, 2024-08-29

« Wednesday, 2024-08-28 Index Friday, 2024-08-30 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:33
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has joined #cip07:41
*** hiromotai <hiromotai!~Thunderbi@240f:75:5bc9:1:e85b:6bc:2845:b675> has quit IRC (Quit: hiromotai)09:06
*** masami <masami!~masami@FL1-119-241-170-31.tky.mesh.ad.jp> has joined #cip12:58
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has joined #cip12:58
*** jki <jki!~jki@195.145.170.202> has joined #cip13:00
jkihi all13:00
arisuthello13:00
masamihi13:01
iwamatsu__hello13:01
pave1hi!13:01
patersoncHello!13:03
jkiok, let's go13:03
jki#startmeeting CIP IRC weekly meeting13:03
collab-meetbotMeeting started Thu Aug 29 13:03:45 2024 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
collab-meetbotThe 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
jki#topic AI review13: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:04
jkino update, except that I want to have something before the conf13:04
jki- clarify role of linux-6.1.y-cip-rebase tag [iwamatsu-san]13:04
jkiiwamatsu__: is this resolved now?13:04
iwamatsu__Yes. I have confirmed that this problem does not occur.13:06
jkiok13:07
jkiand the tag has been removed?13:07
iwamatsu__Yes.13:07
jkiperfect13:07
jkithen moving on...13:07
jki513:07
jki413:07
jki313:07
jki213:07
jki113:07
jki#topic Kernel maintenance updates13:07
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:07
pave1I am reviewing 6.1.107 and AUTOSEL.13:07
ulii'm preparing the next 4.4 release13:08
masamiThis week reported 90 new CVEs and 1 updated CVEs.13:08
iwamatsu__I am reviewing 6.1.107.13:08
jkianything else?13:11
jki513:11
jki413:11
jki313:11
jki213:11
jki113:11
jki#topic Kernel release status13:11
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:11
jkiall green13:11
jkianything to add?13:11
jki513:12
jki413:12
jki313:12
jki213:12
jki113:12
jki#topic Kernel testing13:12
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:12
patersoncHello!13:12
arisutpatersonc,  hello13:12
arisutno updates from me13:12
patersoncI'm here for once, although not much to report. I've been away for most of August tbh.13:13
patersoncIt looks like the CI infrastructure has been behaving (for a change)13:13
pave1Umm.13:13
arisutpatersonc, wb13:13
pave1I needd to press "retry" way too many times when 6.1.107-rc1 was out.13:13
patersoncAh. Was that relating to the dodgy qemu machine a couple of weeks back?13:14
pave1Looked like network problems this time.13:14
jkiany specific machine/lab again?13:15
pave1https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/142949340413:15
pave1You can have sample here.13:15
pave1It is build time.13:15
patersoncThanks13:15
patersoncSo it's failing to clone from kernel.org13:16
pave1I was ably to retry so no huge problem, but ... :-)13:16
patersoncNot ideal13:16
pave1Not ideal.13:16
jkiare we being throttled?13:16
patersoncIt looks like this issue occurred a lot yesterday13:16
patersoncNot sure how to work out if we're being throttled or not13:19
pave1We already clone kernel.org data to gitlab, then we run the tests.13:19
pave1Would gitlab be more suitable source for the clones?13:19
patersoncWe don't clone linux-stable-rc in gitlab because the repo is larger than the limits GitLab allows us13:20
jkiI came from there with isar-cip-core (tarballs, though), and it was... not really13:20
pave1patersonc: aha. Would it make sense to do clone somewhere near the test infrastructure?13:21
jkibut maybe use PREMIRROR?13:21
jkiif that fails, the normal one is used13:21
pave1...so we would only pull from kernel.org once, then do the local clones inside AWS?13:21
jkiand, yes, local caching/mirroring would also be nicer13:21
jkiare we doing shallow clones at least (does not help if there is no connection at all, though)13:22
jki?13:22
pave1I don't remember ever having "git pull" failing, and I don't have particulary great connection here.13:22
patersoncI believe it's a shallow clone13:23
patersoncWe could investigate setting up some sort of mirror in AWS I guess13:24
pave1I guess it would make sense from "being good net citizen" standpoint, too.13:25
patersoncyea13:26
jkiok... anything else on testing?13:27
jki513:28
jki413:28
jki313:28
jki213:28
jki113:28
jki#topic AOB13:28
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:28
jkicurious: who all will be in Vienna now?13:29
ulio/13:29
pave1o/13:29
patersonco/13:29
iwamatsu__o/13:30
patersoncI heard there will be free cocktails :)13:30
jkiyeah, for some even parallelized :)13:30
jki(RT reception is competing with CIP, tss, tss)13:31
jkiok, seems we should also use Vienna for some live kernel WG meet-up13:31
jkinot only over cocktails ;)13:32
jkimaybe some joint lunch break again?13:32
pave1I don't have exact place ATM, but yes, that would work.13:33
patersoncSounds good13:33
iwamatsu__+113:34
jkiI'll check the agenda again an propose some slot first of all13:34
uli+113:34
jkiperfect13:34
jkianything else for today?13:34
jki513:36
jki413:36
jki313:36
jki213:36
jki113:36
jki#endmeeting13:36
collab-meetbotMeeting ended Thu Aug 29 13:36:15 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:36
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-29-13.03.html13:36
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-29-13.03.txt13:36
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2024/08/cip.2024-08-29-13.03.log.html13:36
*** 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:36
arisutthanks13:36
pave1Thank you!13:36
jkithanks you all!13:36
ulithanks13:36
masamithank you13:36
iwamatsu__thank you13:36
*** jki <jki!~jki@195.145.170.202> has quit IRC (Quit: Leaving)13:36
*** masami <masami!~masami@FL1-119-241-170-31.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:38
patersoncThanks13:38
*** iwamatsu__ <iwamatsu__!~iwamatsu_@2405:6581:5360:1800:e310:9694:6a97:c2a3> has quit IRC (Quit: Client closed)13:44
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)14:35
*** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has quit IRC (Ping timeout: 276 seconds)14:56
*** arnd <arnd!sid21101@id-21101.hampstead.irccloud.com> has joined #cip14:59
patersoncpave1: For linux-stable-rc-ci I've changed it to pull from the googlesource mirror of kernel.org. Seems to be okay so far but let's give it some time.15:28
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Ping timeout: 252 seconds)17:50
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has joined #cip17:52
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has quit IRC (Ping timeout: 272 seconds)20:47
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.158> has joined #cip20:48
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.158> has quit IRC (Ping timeout: 246 seconds)21:01
*** prabhakalad <prabhakalad!~prabhakar@165.225.17.161> has joined #cip21:02
« Wednesday, 2024-08-28 Index Friday, 2024-08-30 »

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