IRC logs for #cip for Thursday, 2021-08-26

« Wednesday, 2021-08-25 Index Friday, 2021-08-27 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:22
*** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has joined #cip10:55
*** masashi910 <masashi910!~masashi.k@122x216x27x145.ap122.ftth.ucom.ne.jp> has joined #cip11:43
*** masami <masami!~masami@FL1-60-237-215-110.tky.mesh.ad.jp> has joined #cip12:13
*** iwamatsu <iwamatsu!~iwamatsu@2405:6581:5360:1800:4f76:8eed:afa7:c68e> has joined #cip12:58
*** josiah|2 <josiah|2!~kvirc@pool-71-179-138-156.bltmmd.fios.verizon.net> has joined #cip12:58
*** pavel <pavel!~pavel@88.103.239.128> has joined #cip12:59
masashi910#startmeeting CIP IRC weekly meeting13:00
brlogger_Meeting started Thu Aug 26 13:00:01 2021 UTC and is due to finish in 60 minutes.  The chair is masashi910. 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
masashi910#topic rollcall13:00
*** brlogger_ changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)"13:00
pavelhi13:00
masashi910please say hi if you're around13:00
masamihi13:00
josiah|2Hi13:00
patersonc[m]hi13:00
masashi910Let's get started.13:01
masashi910#topic AI review13:01
*** brlogger_ changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:01
masashi9101. Combine root filesystem with kselftest binary - iwamatsu & alicef13:01
iwamatsuhi13:01
iwamatsuno update13:01
masashi910iwamatsu: Noted. Thanks.13:01
alicefhi13:01
masashi910alicef: Hi, do you have updates?13:01
masashi910We are checking AI#1: Combine root filesystem with kselftest binary - iwamatsu & alicef13:02
alicefno I currently don't13:03
masashi910alicef: Sure, thanks.13:03
masashi9102. Do some experiment to lower burdens on CI - patersonc13:03
patersonc[m]No updates13:04
masashi910patersonc[m]: Ok, thanks.13:04
masashi910any other topics?13:04
masashi910313:04
masashi910213:04
masashi910113:04
masashi910#topic Kernel maintenance updates13:04
*** brlogger_ changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:04
pavelI have reviewed 5.10.61.13:04
pavelAnd did some research on CVE-2021-36\13:05
pavel00:13:05
pavel(bpf)13:05
iwamatsuI revewed 4.4.282-rc , and reviewing  5.10.61-rc13:06
masamiThis week 2 new CVEs and no updated CVEs.13:06
masamiCVE-2020-3702: mainline is fixed13:06
masamiCVE-2021-3732: mainline and stable kernels are fixed13:06
masamithat's all13:06
masamipavel: I'll keep track of CVE-2021-360013:06
pavelI guess maybe we should talk about CVE-2021-3600.13:07
pavelIt is BPF in 4.19... and it is pretty much unfixable13:07
pavelIt is also quite high severity.13:07
pavelCould we ask companies if they are using BPF / planning to use BPF in their products13:08
pavel...and adjust the configs appropriately if not?13:08
masashi910pavel: Sure, shall I ask cip member companies?13:09
pavelAffected configs are siemens_imx6, plathome_obsvx2, siemens_iot2000, toshiba_atom_baytrail AFAICT.13:09
pavelIssue at hand is v4.19, but if we can get rid of BPF everywhere, it will not be bad result.13:10
pavelmasashi910: Yes, that would be nice.13:10
masashi910pavel: Sure.13:11
pavelThank you!13:11
masashi910pavel, iwamatsu, masami: Thanks for your updates.13:11
masashi910any other topics?13:11
masashi910313:11
masashi910213:11
masashi910113:11
masashi910#topic Kernel testing13:11
*** brlogger_ changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:11
patersonc[m]Hello13:12
patersonc[m]The LAVA server ran out of storage last week. But started working fine when I deleted some older backups13:12
patersonc[m]I've also pruned the database now so it's a lot smaller13:12
patersonc[m]So backups will be faster and smaller etc.13:12
patersonc[m]I'm not sure if CIP have a requirement to keep test job logs forever?13:13
patersonc[m]Does anyone here have a preference/requirement?13:13
pavelForever is an ugly word :-).13:13
alicefshould at least have more space as we are adding more testing framework from kernelci13:13
pavelIt may make sense to keep _some_ old logs.13:14
patersonc[m]For kernelCI jobs I culled all jobs older than 1 month13:14
patersonc[m]For CIP I culled all jobs older than a year13:14
alicefsounds good for me13:15
patersonc[m]Perhaps this is a Q for the mailing list13:15
alicefsure13:15
pavelIt would not be bad to keep old logs from some "significant" releases or something...13:15
patersonc[m]pavel: May be a plan. Harder to maintain though. I'm not sure how flexible the tooling is, but I can take a look13:16
alicefis difficult to define "significant"13:16
pavelYes... and I guess theoretically we can re-run the testing.13:16
pavelBut if some board goes flakey or something, old logs might beuseful.13:17
pavelKeep randomly one in 10 old logs?13:17
patersonc[m]alicef: Do you know if kernelci.org downloads a copy of the logs? Or does it just link to them in LAVA?13:17
alicefyes I was wondering same13:17
patersonc[m]If KernelCI keeps a copy of the logs, when CIP migrates to using KernelCI we won't have much need to keep them in LAVA long term13:18
patersonc[m]Anyway, I'll take an action to investigate13:18
aliceflooks like it keeps a copy for few days13:18
patersonc[m]Okay. Not so great13:19
alicefrockchip was failing here https://staging.kernelci.org/test/job/cip/branch/linux-4.19.y-cip/kernel/v4.19.196-cip53/plan/baseline/13:19
alicefbut we have no more logs13:20
alicefhttps://storage.staging.kernelci.org/cip/linux-4.19.y-cip/v4.19.196-cip53/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.txt13:20
alicefor could be that just failed and didn't copy anything13:20
alicefbut I don't think keeps much of a backhistory13:21
patersonc[m]alicef: Maybe staging behaves differently?13:21
alicefhttps://storage.kernelci.org/cip/linux-4.19.y-cip/v4.19.198-cip54/x86_64/allnoconfig/gcc-8/logs/13:22
alicefis anyway just keeping last logs13:22
alicefhttps://storage.kernelci.org/cip/13:22
alicefbut looks like each version have is own logs13:22
patersonc[m]Let's take this topic outside of this meeting?13:23
alicefbut still there are not all the logs13:23
alicefyes is something to look into13:23
masashi910patersonc[m], alicef: Could you just make sure the log status in kernelci? Could it be an AI?13:23
alicefAI ?13:24
masashi910action item13:24
alicefI think we will discuss thins outside the meeting13:24
masashi910yes, and what I am asking is to report the result at some IRC meeting.13:25
alicefyes but we can use this space13:26
alicefwe don't need a AI i think13:26
masashi910alicef: Ok.13:26
masashi910so thanks very much for these discussions.13:26
masashi910are there any other topics?13:27
alicefI'm instead working on using isar cip core on the kernelci builds13:27
alicefbut still need some changes for make it usable13:27
masashi910alicef: Thanks for your works.13:28
masashi910any other topics?13:28
masashi910313:29
masashi910213:29
masashi910113:29
masashi910#topic AOB13:29
*** brlogger_ changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:29
masashi910I have one topic.13:29
masashi910This is the last IRC meeting I chair, because the kernel chair will be switched to Jan-san on September 1st (Wed). After that, Jan-san will host meetings.13:29
masashi910I want to thank all for helping me to serve as the kernel chair for almost two years.13:29
masashi910Are there any business to discuss?13:30
pavelThank you for all the good work!13:30
patersonc[m]Thank you for all of your work Kudo-san!13:30
iwamatsuThank you for all your work!13:30
masamimasashi910: Thank your for your work!13:30
alicefThanks you13:30
masashi910Thanks for saying so, all!13:30
masashi910513:31
masashi910413:31
masashi910313:31
masashi910213:31
masashi910113:31
masashi910Let's close today's meeting.13:31
masashi910#endmeeting13:31
brlogger_Meeting ended Thu Aug 26 13:31:30 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:31
brlogger_Minutes:        https://irclogs.baserock.org/meetings/cip/2021/08/cip.2021-08-26-13.00.html13:31
brlogger_Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/08/cip.2021-08-26-13.00.txt13:31
brlogger_Log:            https://irclogs.baserock.org/meetings/cip/2021/08/cip.2021-08-26-13.00.log.html13:31
*** brlogger_ changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"13:31
masashi910Thanks, Bye Bye!13:31
masamithank you!13:31
pavelThank you!13:31
iwamatsuThank you13:31
*** iwamatsu <iwamatsu!~iwamatsu@2405:6581:5360:1800:4f76:8eed:afa7:c68e> has quit IRC13:32
*** masashi910 <masashi910!~masashi.k@122x216x27x145.ap122.ftth.ucom.ne.jp> has quit IRC13:32
*** pavel <pavel!~pavel@88.103.239.128> has quit IRC13:32
*** josiah|2 <josiah|2!~kvirc@pool-71-179-138-156.bltmmd.fios.verizon.net> has quit IRC13:35
patersonc[m]alicef: So how long does kernelci keep results for?13:42
patersonc[m]The default view is the last 20 results13:42
patersonc[m]Is this something we can change for CIP?13:43
alicefif I remember correctly they are using cronjobs for remove old logs13:44
patersonc[m]And do we know what KCIDB's policy is?13:45
alicefKCIDB is keeping everything afaik13:45
patersonc[m]Okay13:45
patersonc[m]Including logs?13:45
alicefchromeos asked for their own storage space by the way13:53
alicefhttps://storage.chromeos.kernelci.org/13:53
alicefmaybe we could do same13:53
patersonc[m]alicef: Good idea. We could even see if we could use our current storage provider to save stressing KernelCi's storage13:57
*** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has quit IRC18:03
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC18:45
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip18:45
*** punit_ <punit_!~punit@v118-27-30-150.1qlq.static.cnode.io> has joined #cip20:59
*** arnd_ <arnd_!sid21101@id-21101.stonehaven.irccloud.com> has joined #cip21:00
*** arnd <arnd!sid21101@id-21101.stonehaven.irccloud.com> has quit IRC21:01
*** punit <punit!~punit@v118-27-30-150.1qlq.static.cnode.io> has quit IRC21:01
*** arnd_ is now known as arnd21:01
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC21:57
« Wednesday, 2021-08-25 Index Friday, 2021-08-27 »

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