| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 01:04 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 04:02 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 08:37 | |
| *** uli <uli!~uli@55d4477d.access.ecotel.net> has joined #cip | 09:30 | |
| *** masami <masami!~masami@FLH1Aft167.tky.mesh.ad.jp> has joined #cip | 12:16 | |
| *** jki <jki!~jki@165.225.27.8> has joined #cip | 12:52 | |
| *** pave1 <pave1!~pavel@89-24-45-35.nat.epc.tmcz.cz> has joined #cip | 13:01 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
|---|---|---|
| brlogger | Meeting started Thu Dec 2 13:01:10 2021 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | Hi everyone! | 13:01 |
| pave1 | hi! | 13:01 |
| uli | hello | 13:01 |
| masami | hi | 13:01 |
| patersonc[m] | ay up | 13:01 |
| iwamatsu | hi | 13:01 |
| alicefm | Hi | 13:02 |
| jki | #topic AI review | 13:04 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| jki | 1. Combine root filesystem with kselftest binary (finishings) - iwamatsu & alicef | 13:04 |
| alicef | kernelci is currently testing cip with kselftest | 13:04 |
| alicef | I also replayed to pave1 mail about the current regressions | 13:05 |
| alicef | we are currently adding the kernelci automatic bisection feature to the CIP kernel tree | 13:05 |
| alicef | We should start to get cip kernel bisection mail in the future | 13:06 |
| alicef | anything to add ? or question ? | 13:06 |
| jki | what's missing to close this specific AI (and maybe start new ones)? | 13:06 |
| jki | isar-cip-core merge at least, anything else? | 13:07 |
| alicef | nothing other than isar-cip-core merge I think | 13:07 |
| iwamatsu | alicef: can anyone receive the build result email? is there an I/F to reguster? | 13:08 |
| alicef | iwamatsu: you mean bisection email ? | 13:09 |
| iwamatsu | test result for CIP kernel | 13:09 |
| alicef | all mail concerning cip kernel are already sended to cip-dev mailing list | 13:09 |
| pave1 | alicef: Thanks for the email reply. | 13:10 |
| pave1 | alicef: If we can get the automatic bisection to work, yes, that will be useful. | 13:10 |
| alicef | from what I could see we are not missing any mail from cip-dev | 13:10 |
| pave1 | alicef: Best way would be to bisect between v4.19.217 and v4.19.217-cip62, if that can be arranged. | 13:10 |
| iwamatsu | Can I receive it with other email address. e.g. personal email address. | 13:11 |
| pave1 | alicef: Plus, for this to be useful, we'd really need some way to submit patches/trees for testing. | 13:11 |
| alicef | iwamatsu: is not something that as been done. usually kernelci report to kernelci ml and cip-dev ml | 13:11 |
| patersonc[m] | We can set it up to report to other emails if we want, just need to submit an MR to kernelci | 13:12 |
| iwamatsu | alicef: I see. | 13:12 |
| alicef | pave1: no currently is not something that is supported by kernelci to do bisect between completely different tree | 13:12 |
| iwamatsu | got it | 13:12 |
| patersonc[m] | pave1: We could add another tree to Kernelci. Then you push to that tree to test etc. | 13:12 |
| pave1 | patersonc: That would be useful. ONe really needs a way to verify that patch fixes the issue, etc. | 13:13 |
| alicef | pave1: you could have a testing branch on cip | 13:13 |
| alicef | I don't think having another tree is needed | 13:13 |
| alicef | just some branch like 4.19-cip-test | 13:14 |
| alicef | is enough | 13:14 |
| pave1 | patersonc,alicef: Branch works, too. BUt it is going to be cluttered with test commits by different people. | 13:14 |
| pave1 | patersonc,alicef: How long will it take between push and getting results? | 13:14 |
| alicef | sure. whatever works for you | 13:14 |
| pave1 | patersonc,alicef: Plus I guess that will cause quite a lot of noise on the lists :-(. | 13:15 |
| alicef | pave1: it can take some time to get results. not sure how much time is not immediate afaik | 13:15 |
| pave1 | alicef: Is it more like hour, day or a week? | 13:16 |
| alicef | pave1: depends we could add a job on jenkins only for your tree where you get your results from staging. | 13:16 |
| alicef | pave1: need to be discussed with kernelci TSC | 13:17 |
| alicef | depend from the resources TSC have for such thing | 13:17 |
| alicef | but if you are just trying to reproduce tests you could also rebuild on your machine, push to a ftp server and send lava jobs with such artifacts | 13:18 |
| alicef | depend where you want to test such commits | 13:19 |
| alicef | if is just a board or if you want to test with a bunch of board | 13:19 |
| pave1 | alicef: Local builds don't really work too well. | 13:19 |
| alicef | having a personal tree for pushing test to kernelci is possible | 13:20 |
| pave1 | alicef: yep, that would be nice. | 13:20 |
| alicef | pave1: why not ? you are using the same enviroment anyway | 13:20 |
| pave1 | alicef: Maintaining all the cross-compilers (etc) is quite a pain, plus you need fast CPU and fast network for that. | 13:21 |
| alicef | ok | 13:22 |
| alicef | pave1: do you already have a tree for testing that you want tested ? | 13:23 |
| pave1 | alicef: I do have https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-test . | 13:24 |
| pave1 | alicef: I push random kernels there (4.4, 4.19, 5.10, -realtime versions) when I need something tested. | 13:24 |
| alicef | you can add it here https://github.com/kernelci/kernelci-core/blob/eae1f11042ae21383178595a675adfee0dac2412/config/core/build-configs-cip.yaml#L1 | 13:24 |
| pave1 | Ok, perhaps we can discuss this further over email? | 13:25 |
| patersonc[m] | https://github.com/kernelci/kernelci-core/issues/new?assignees=&labels=&template=new-kernel-branch.md&title=Add+branch+BRANCH+from+TREE | 13:25 |
| alicef | sure | 13:25 |
| alicef | patersonc[m]: that is not for cip branch, i suppose | 13:26 |
| patersonc[m] | I think it could be. You specify the tree as cip | 13:26 |
| alicef | ok | 13:26 |
| alicef | and you can call your repo like pave1: | 13:27 |
| alicef | and add some test to it | 13:27 |
| alicef | some other kernelci dev is doing it | 13:27 |
| alicef | we can also specify to send the email only to you from the jenkin task | 13:28 |
| alicef | iwamatsu: we can send mail from specific people from changing the jenkin task, but not sure about the main cip tree. I can look into it | 13:29 |
| iwamatsu | alicef: got it | 13:29 |
| alicef | do you need to get cip tree mail to some personal mail ? if yes you can write it on private and I can look into adding it | 13:30 |
| iwamatsu | answer is yes. company emails are limited... | 13:31 |
| alicef | ok | 13:31 |
| jki | ok, done with this topic? | 13:33 |
| jki | alicef: please send a new patch series for isar-cip-core - or let me know if I can help | 13:33 |
| alicef | iwamatsu: send me a mail and i will send a pull request to jenkins for adding your email | 13:33 |
| alicef | jki: ok | 13:34 |
| iwamatsu | alicef: thanks | 13:35 |
| alicef | iwamatsu: np, sorry for the confusion | 13:35 |
| jki | 2. Look into S3 artifact upload issues - patersonc | 13:36 |
| jki | done, right? | 13:36 |
| patersonc[m] | Done! | 13:36 |
| jki | thanks! | 13:36 |
| patersonc[m] | Issue is now fixed | 13:36 |
| patersonc[m] | Although please let me know if you see any more issues | 13:36 |
| iwamatsu | Yey | 13:36 |
| pave1 | Yep, will do. | 13:37 |
| jki | 3. Perform initial comparison of KernelCI results 5.10 LTS vs. CIP - iwamatsu & alicef | 13:37 |
| alicef | I did some comparison about 4.19 and sended by mail. not yet worked at 5.10 comparison | 13:38 |
| iwamatsu | Not yet. | 13:38 |
| jki | ah, sorry, maybe my mistake what was planned | 13:39 |
| jki | or was it 5.10? | 13:39 |
| iwamatsu | maybe all CIP kernel. | 13:39 |
| alicef | I thought was a general comparison about lts-lts+1 and cip-cip+1 | 13:39 |
| alicef | we want this to be automated ? | 13:40 |
| iwamatsu | I think so. | 13:40 |
| alicef | here is comparison with 4.19.217 and 4.19.217-cip62 https://www.diffchecker.com/JjmXiP7b | 13:41 |
| alicef | as example | 13:41 |
| iwamatsu | about 5.10.y, we may need to proceed with the release of the 5.10.y CIP kernel.. | 13:41 |
| alicef | that i sended today to pavel request | 13:41 |
| alicef | yes about 5.10 we still don't have a release. | 13:42 |
| alicef | we should release before doing comparison or i can just compare with the last commit | 13:42 |
| iwamatsu | is that diff email is automatic? | 13:43 |
| iwamatsu | I see. | 13:43 |
| alicef | not yet automatic but is possible to implement it to kernelci | 13:43 |
| iwamatsu | nice | 13:43 |
| iwamatsu | ok, lets discues email about this. | 13:43 |
| alicef | but is not straight forward it still need some function for make it work and probably also need to be talked with kernelci tsc | 13:44 |
| iwamatsu | I see | 13:44 |
| alicef | I could start by opening a issue to kernelci and see others opinions | 13:44 |
| alicef | currently I'm doing it manually by searching each email result | 13:46 |
| alicef | and because the result format is standard they can be easily diffed | 13:46 |
| alicef | I'm not sure if kernelci is keeping a list of previous sended email for comparison purpose | 13:47 |
| alicef | I don't think so | 13:47 |
| alicef | that could be a problem | 13:48 |
| alicef | I need to investigate on how to automate this | 13:48 |
| alicef | iwamatsu: any date on the 5.10 release ? | 13:49 |
| jki | so, alicef will discuss this topic with kernelci, iwamatsu will first release 5.10 and wait for alicef's results? | 13:49 |
| alicef | work for me | 13:50 |
| iwamatsu | not decide yet > release | 13:50 |
| iwamatsu | I do not wait for alice's work. | 13:51 |
| jki | ok | 13:51 |
| alicef | ok | 13:51 |
| jki | maybe discuss 5.10 release separately - anything else for this comparison topic? | 13:52 |
| alicef | something like the pasted diffchecker is enough as comparison format ? | 13:52 |
| alicef | or have you in mind something different ? | 13:53 |
| alicef | if such reports could be automated and sent by email would be enough ? | 13:53 |
| alicef | for closing this AI | 13:54 |
| iwamatsu | First of all, I think diff is fine. | 13:54 |
| jki | okay | 13:55 |
| jki | 4. Propose tweet on KernelCI-CIP collaboration progress - alicef | 13:56 |
| jki | alicef: I think you asked for this :) | 13:56 |
| alicef | my idea, as currently we have a CIP panel project on KernelCI, was to tweet about this event. | 13:57 |
| alicef | https://github.com/orgs/kernelci/projects/11 | 13:57 |
| alicef | that show the status of project testing on kernelci | 13:57 |
| alicef | also as we have enabled kselftest testing on kernelci, maybe tweet also about this | 13:58 |
| jki | yes, do you have some text to report on that? we are happy to help tweaking it if needed | 13:58 |
| alicef | cip kselftest testing on kernelci | 13:58 |
| alicef | mmm | 13:59 |
| jki | need not be now, of course | 13:59 |
| alicef | we need to think about the text to report | 13:59 |
| alicef | I don't have one now | 14:00 |
| jki | send some draft to chris and me, and then we can continue and ask neal to tweet | 14:00 |
| alicef | ok | 14:00 |
| jki | #topic Kernel maintenance updates | 14:01 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 14:01 | |
| alicef | thanks | 14:01 |
| pave1 | I am reviewing 5.10.83... and did 4.19-rt release. | 14:02 |
| uli | reviewing 5.10.80 | 14:02 |
| masami | There is 5 new CVEs, and two of them are not fixed in the mainline yet. | 14:02 |
| iwamatsu | I am reviewing 5.10.83 | 14:02 |
| masami | Patch to fix CVE-2021-4001 for stable/5.10 which sent last week, was merged. | 14:02 |
| pave1 | I should do 4.4-rt release, soon, I'm waiting -rt team to release their kernel, and it would make sense to coordinate 4.4-cip with that. | 14:02 |
| iwamatsu | And I am creating a review list creating/pushing tool | 14:03 |
| iwamatsu | pave1: I can ask ahbout this to RT project. | 14:04 |
| jki | ok, anything else? | 14:05 |
| pave1 | iwamatsu: That may make sense if they don't release it 'soon'. | 14:05 |
| iwamatsu | s/ahbout this/4.4-rt release/g | 14:05 |
| iwamatsu | pava1: ok | 14:06 |
| jki | what is missing / what are conditions for a 5.10 release? | 14:07 |
| pave1 | I believe we are ready for 5.10 release. | 14:07 |
| jki | head filled with latest or desired LTS version? | 14:08 |
| iwamatsu | I am going to work this tomorrow. | 14:08 |
| iwamatsu | yes. | 14:08 |
| iwamatsu | I am updating to latset LTS. | 14:09 |
| jki | cool! | 14:09 |
| jki | anything else? | 14:10 |
| alicefm | I can force a check from KernelCI on 5.10 current status if is needed | 14:10 |
| jki | #topic Kernel testing | 14:12 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 14:12 | |
| jki | nothing more here, I suppose | 14:12 |
| patersonc[m] | a bit | 14:12 |
| jki | ok, go ahead | 14:12 |
| patersonc[m] | I've started using an EU based S3 bucket for storing our CI artifacts. This speeds up our uploading/downloading which is good | 14:13 |
| alicefm | Nice | 14:13 |
| patersonc[m] | Currently I'm working on using the "latest" isar-cip-core image for our Kernel testing. | 14:13 |
| patersonc[m] | jki: I've got a question about that, perhaps for later if you're available | 14:13 |
| *** pav31 <pav31!~mobian@89-24-45-35.nat.epc.tmcz.cz> has joined #cip | 14:15 | |
| jki | yeah, we can do that | 14:15 |
| jki | #topic AOB | 14:16 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 14:16 | |
| jki | anything? | 14:16 |
| jki | 3 | 14:18 |
| jki | 2 | 14:18 |
| jki | 1 | 14:18 |
| jki | #endmeeting | 14:18 |
| brlogger | Meeting ended Thu Dec 2 14:18:39 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:18 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-02-13.01.html | 14:18 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-02-13.01.txt | 14:18 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-02-13.01.log.html | 14:18 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 14:18 | |
| jki | then thank you all! | 14:18 |
| alicefm | Thanks you | 14:18 |
| patersonc[m] | Thanks | 14:19 |
| *** pave1 <pave1!~pavel@89-24-45-35.nat.epc.tmcz.cz> has quit IRC | 14:19 | |
| uli | bye | 14:19 |
| masami | bye! | 14:19 |
| iwamatsu | Thank you! | 14:19 |
| patersonc[m] | jki: Are the isar-cip-core builds tested at all? Or just built in CI? | 14:19 |
| jki | they are not auto-booted so far in CIP context, except for those now used for kernelci | 14:20 |
| jki | is something broken? | 14:20 |
| *** masami <masami!~masami@FLH1Aft167.tky.mesh.ad.jp> has quit IRC | 14:22 | |
| jki | FWIW, here is a project where similar images are also LAVA-tested after their build: https://source.denx.de/Xenomai/xenomai-images/-/pipelines/10065 | 14:22 |
| jki | but in that case - just like for isar-cip-core - flashable images are not tested, only those tarballs prepared for lava specficially | 14:23 |
| jki | for auto-testing flashable images, we need different infrastructure in the lab | 14:24 |
| jki | e.g. https://github.com/siemens/mtda | 14:24 |
| jki | freshly published, forgot to mention, maybe also interesting for CIP | 14:24 |
| patersonc[m] | jki: I tried the iwg20m image and it doesn't boot: https://lava.ciplatform.org/scheduler/job/561386 | 14:25 |
| jki | that systemd errors, right? | 14:26 |
| jki | maybe we are missing features in the defconfig for that target... | 14:26 |
| patersonc[m] | YEa | 14:26 |
| jki | bullseye or buster? | 14:26 |
| jki | maybe the latter works | 14:26 |
| patersonc[m] | buster | 14:27 |
| jki | hmm, would have been too easy | 14:27 |
| jki | then "not tested for too long" | 14:27 |
| jki | possibly the last time with stretch :D | 14:27 |
| jki | didn't alicef feed that build into kernelci also for the iwg20m? | 14:28 |
| jki | or is that board not yet covered in kernelci? | 14:28 |
| patersonc[m] | Good question | 14:29 |
| patersonc[m] | Should be supported in kci | 14:29 |
| patersonc[m] | That board should be supported in kci | 14:29 |
| jki | cip-kernel-config/4.4.y-cip/arm/renesas_shmobile_defconfig | 14:30 |
| jki | that is the defconfig used for the board | 14:30 |
| patersonc[m] | Yes | 14:30 |
| jki | irrespective of the kernel version... | 14:30 |
| jki | can THAT work? | 14:30 |
| *** pav31 <pav31!~mobian@89-24-45-35.nat.epc.tmcz.cz> has quit IRC | 14:30 | |
| patersonc[m] | What do you mea? | 14:31 |
| jki | ok, you were testing 4.4... | 14:31 |
| jki | well, if the user selected a 4.19 kernel, still the 4.4 config would be used, but that might be fine as well | 14:32 |
| patersonc[m] | We have a 4.19 version of the config as well? | 14:32 |
| jki | no idea | 14:32 |
| patersonc[m] | We do | 14:33 |
| patersonc[m] | Sorry, not a question | 14:33 |
| patersonc[m] | I'll try bullseye | 14:34 |
| patersonc[m] | Test job is just in a queue | 14:34 |
| patersonc[m] | Also, is there a plan to add isar-cip-core support for all the reference platforms? | 14:35 |
| jki | conceptually yes, "just" needs people to work on that | 14:36 |
| patersonc[m] | Same issue with bullseye: https://lava.ciplatform.org/scheduler/job/561499 | 14:37 |
| alicefm | Sorry I’m not following. We need some change to KernelCI isar-cip-core? | 15:06 |
| patersonc[m] | I don't think so. | 15:08 |
| patersonc[m] | I'm trying to boot isar-cip-core on the iwg20m platform in CIP's CI | 15:08 |
| *** toscalix <toscalix!~toscalix@44.red-79-155-67.dynamicip.rima-tde.net> has joined #cip | 15:21 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 16:06 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 16:11 | |
| *** jki <jki!~jki@165.225.27.8> has quit IRC | 18:02 | |
| *** toscalix <toscalix!~toscalix@44.red-79-155-67.dynamicip.rima-tde.net> has quit IRC | 18:29 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 20:40 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 22:49 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 23:34 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!