Thursday, 2022-11-03

*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip00:07
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)03:21
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:45
*** uli_ <uli_!~uli@175.176.15.165> has joined #cip08:17
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip08:48
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip11:44
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip11:57
*** jki <jki!~jki@165.225.26.250> has joined #cip12:00
jkihi everyone!12:00
uli_hello12:00
masamihi12:00
fbezdekahi12:00
iwamatsuhi12:01
alicefmHi12:01
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbot`Meeting started Thu Nov  3 12:02:43 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
jki#topic AI review12:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
jki1. Add qemu-riscv to cip-kernel-config - patersonc12:02
jkino one here today to address this12:03
jkiother AIs I missed?12:03
jki312:03
jki212:03
jki112:03
jki#topic Kernel maintenance updates12:03
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:03
uli_still reviewing 5.10.15012:03
masamiThis week reported 6 new CVEs and 3 updated CVEs.12:04
iwamatsuI reviewd   5.10.15212:04
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:8836:a9e5:f907:2f10> has joined #cip12:05
jkiseems we don't have much to coordinate here this week12:08
jkianything else on maintenance?12:08
jki312:09
jki212:09
jki112:09
jki#topic Kernel testing12:09
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:09
alicefmNo updates this week12:10
fbezdekaAs Pavel is not here today we might have to skip it: we still have https://github.com/kernelci/kernelci-core/issues/1053 open. My understanding was that the test report for the 4.4-cip tree/branch was usable now. I guess we can close it soon...12:10
pave1I'm here now. Sorry.12:10
pave1DST kicked in.12:10
jkihi, pavel!12:11
pave1Hi!12:11
jkican you quickly catch up - anything to add on the previous topic or on the testing question?12:11
pave1I was reviewing 5.10.152 and am reviewing 5.10.153. Otherwise not much updates from me.12:12
pave1I need to take another look at 4.4 testing effort, but feel free to close github issue.12:12
pave1gitlab does not work well today: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/68431325412:13
pave1The tasks with red status have already had 3 tries...12:14
jkiERROR: Job failed (system failure): pods "runner-ufmsyps-project-2678032-concurrent-02pt99" not found - Huh?!12:15
pave1Yep, that happens a lot. I normally just hit retry :-).12:15
pave14.4 testing -- there may be still some work to do on 4.412:16
pave1Latest reports I could find:12:16
pave1cip/linux-4.4.y-cip smc: 12 runs, 3 regressions (v4.4.302-cip69-517-g92709d8ae585) #kerne12:16
pave1cip/linux-4.4.y-cip baseline: 102 runs, 6 regressions (v4.4.302-cip69-517-g92709d8ae58512:16
pave1cip/linux-4.4.y-cip ltp-pty: 3 runs, 1 regressions (v4.4.302-cip69-517-g92709d8ae585) #ke12:16
pave1I know smc is problematic, but we have regressions elsewhere, too.12:16
pave1One of failures is: https://storage.kernelci.org//cip/linux-4.4.y-cip/v4.4.302-cip69-517-g92709d8ae585/arm64/defconfig/gcc-10/lab-broonie/baseline-qemu_arm64-virt-gicv2.html12:18
pave1I see no kernel logs, so I suspect it is something wrong with the test system.12:19
fbezdekaAt least some (if not all) of the smc failures are reported by qemu targets. I guess that's more a common kernelci testing issue12:19
pave1So perhaps don't close the gitlab issue just yet :-).12:19
jkihow to proceed here, who can help / needs to help?12:24
iwamatsuI re-run pavel's pipeline. Some jobs have worked and succeeded.12:27
fbezdekaBuild tests are looking good, only a few warnings. That might be something for Pavel to look at. I could try to talk to kernelci if testing smc on virtual targets has any value12:27
iwamatsuHowever, the following jobs have a problem with CI.12:28
iwamatsuhttps://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/326893575312:28
pave1Yep, disabling smc on qemu might be good idea.12:28
pave1What about baseline and ltp-pty regressions?12:28
fbezdekaThat would be the next steps.12:29
iwamatsuabout qemu/smc issue, it is not difficult. I will create MR for that.12:30
pave1fbezdeka: And for the record, I know about the ~ 1 warning,just was busy with other stuff. Sorry about that.12:30
fbezdekaIt's just a warning. I'm quite sure it doesn't bring up something serious12:31
fbezdekaqemu/smc: Maybe someone else should confirm that it has no value to test microcode related stuff on virtual targets. Maybe I/we miss something12:31
pave1fbezdeka: IIRC... trouble is that we are using KVM or something, so whether test works or not depends on configuration of host.12:32
fbezdekaHm... But even with KVM enabled we would get random results (depends on the job scheduling I guess)12:33
pave1fbezdeka: I suggest disabling smc on qemu. We have enough other stuff to work on.12:33
fbezdekaFine with that.12:33
iwamatsuAnd qemu machine option. user can contorol it with qemu option.12:34
iwamatsussbd spec-ctl etc..12:35
iwamatsuI use them to avoid the qemu/smc issue, but I'm still on the way.12:37
jkiok, seems there is a plan how to proceed12:39
jkianything else on this?12:39
jki312:40
jki212:40
jki112:41
jki#topic AOB12:41
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:41
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:8836:a9e5:f907:2f10> has quit IRC (Remote host closed the connection)12:41
jkiany topic?12:43
jki312:43
jki212:43
jki112:43
jki#endmeeting12:43
collab-meetbot`Meeting ended Thu Nov  3 12:43:46 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:43
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-03-12.02.html12:43
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-03-12.02.txt12:43
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-03-12.02.log.html12:43
*** 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 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/""12:43
pave1Thank you!12:43
jkithank you all!12:43
uli_thank you12:43
masamithanks12:44
iwamatsuthank you12:44
fbezdekaThanks!12:44
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:44
alicefmThanks12:44
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:aeb7:b91f:45ea:cd9a> has joined #cip12:44
jkibye!12:44
*** jki <jki!~jki@165.225.26.250> has quit IRC (Quit: Leaving)12:44
*** uli_ <uli_!~uli@175.176.15.165> has left #cip (Leaving)13:12
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip15:16
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:aeb7:b91f:45ea:cd9a> has quit IRC (Ping timeout: 268 seconds)18:48
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 246 seconds)22:55

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