| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 00:12 | |
| *** punit_ is now known as punit | 02:04 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 02:32 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 07:00 | |
| *** toscalix <toscalix!~toscalix@44.red-79-155-67.dynamicip.rima-tde.net> has joined #cip | 08:54 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 10:50 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 11:10 | |
| *** uli <uli!~uli@55d4f9d5.access.ecotel.net> has joined #cip | 11:43 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip | 12:34 | |
| *** jki <jki!~jki@165.225.27.15> has joined #cip | 12:46 | |
| *** pav31 <pav31!~mobian@78-80-24-40.customers.tmcz.cz> has joined #cip | 12:59 | |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
|---|---|---|
| brlogger` | Meeting started Thu Dec 9 13:01:12 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 all! | 13:01 |
| pav31 | hi! | 13:01 |
| uli | hello | 13:01 |
| alicefm | Hi | 13:01 |
| masami | hi | 13:01 |
| *** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip | 13:01 | |
| iwamatsu | hi | 13:02 |
| josiah | 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 (finishing) - alicef | 13:04 |
| alicefm | Not yet done | 13:04 |
| jki | 2. Perform initial comparison of KernelCI results 5.10 LTS vs. CIP - iwamatsu & alicef | 13:04 |
| alicefm | Send the analysis on the announce thread | 13:05 |
| alicefm | Sent | 13:05 |
| iwamatsu | thanks | 13:05 |
| alicefm | I didn’t find any worth regression | 13:05 |
| alicefm | The two regression looks like caused by board problems | 13:06 |
| iwamatsu | https://lore.kernel.org/cip-dev/TYAPR01MB62524C420EECB609794B0587926B9@TYAPR01MB6252.jpnprd01.prod.outlook.com/T/#m3ce69fea19de4537cd422243e7b0cd3d0792a205 | 13:06 |
| jki | that's good news, indeed - thanks, alicefm | 13:07 |
| jki | means, we can now use the kernelci diff between to runs of the same branch in order to find regressions, right? | 13:09 |
| alicefm | Yes | 13:09 |
| jki | great | 13:10 |
| jki | 3. Propose tweet on KernelCI-CIP collaboration progress - alicef | 13:11 |
| alicefm | Not yet done. I’m currently busy with open source conference Japan 2021 presentation | 13:12 |
| alicefm | Skip | 13:12 |
| jki | ok, no problem! | 13:12 |
| jki | we had a tweet this week on the 5.10 release | 13:12 |
| jki | anything else for AIs? | 13:13 |
| jki | 3 | 13:13 |
| jki | 2 | 13:13 |
| jki | 1 | 13:13 |
| jki | #topic Kernel maintenance updates | 13:13 |
| *** brlogger` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:13 | |
| uli | finished 5.10.80 review | 13:14 |
| masami | There is three new CVEs. They have already been fixed in the mainline. | 13:14 |
| pav31 | I was reviewing 5.10.84. | 13:14 |
| pav31 | Also 5.10-rt is now released. | 13:14 |
| iwamatsu | I am reviewing 5.10.84 | 13:14 |
| iwamatsu | thanks for release -rt tree! | 13:15 |
| pav31 | You are welcome, and thanks for 5.10-cip :-). | 13:15 |
| pav31 | Timing worked well. | 13:16 |
| iwamatsu | ;-) | 13:16 |
| jki | indeed :) | 13:16 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 13:17 | |
| jki | anything else here? | 13:18 |
| jki | 3 | 13:18 |
| jki | 2 | 13:18 |
| jki | 1 | 13:18 |
| jki | #topic Kernel testing | 13:18 |
| *** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:18 | |
| alicefm | I’m currently enabling cip 5.10 rt on KernelCI but we have problem finding a machine that can run preemptrt test | 13:19 |
| jki | what are the restrictions? | 13:20 |
| alicefm | The only board that we have enabled is failing the boot now we are looking some different machine | 13:21 |
| alicefm | Not sure what you mean by restriction | 13:21 |
| alicefm | We have enabled for preempt-rt | 13:22 |
| jki | thanks, that explains it | 13:22 |
| pav31 | You may want to try socfpga based boards. | 13:22 |
| pav31 | They have reasonable max latencies. | 13:22 |
| alicef | you can see the problem explanation here https://github.com/kernelci/kernelci-core/pull/908 | 13:23 |
| alicef | second topic about automation of check with cip and lts results and regression. | 13:23 |
| patersonc[m] | Can't KernelCI add the r8a779x_usb3_v3.dlmem firmware to the filesystem for the Renesas boards? | 13:24 |
| alicef | looks like is something that is needed also for some other tree like rc kernel versions | 13:24 |
| alicef | patersonc[m]: it should already build that module afaik | 13:24 |
| patersonc[m] | yep | 13:24 |
| alicef | anyway going back to results comparison | 13:25 |
| alicef | unfortunatly currently KernelCI is rewriting the KernelCI API and that from KernelCI Technical Sterring Committee point of view have priority over such work | 13:26 |
| alicef | and because the comparison system would be dependent of the KernelCI API we should implement it on the new API that is currently not finished yet | 13:27 |
| alicef | implementing on the old API is mostly a lost of time as that will be deprecated in the near future | 13:28 |
| jki | what is the rough timeline for this rewrite? | 13:29 |
| alicef | mmm that's a good question | 13:29 |
| alicef | they already working on it and the repository looks going on with steady pace | 13:30 |
| pav31 | Could we get some improvements to our gitlab testing? | 13:30 |
| alicef | this is the project panel about KernelCI new api https://github.com/orgs/kernelci/projects/10 | 13:30 |
| pav31 | It looks like it will be useful even with kernelci in place. | 13:31 |
| alicef | pav31: sorry, what do you mean ? | 13:31 |
| pav31 | The tests we are running with each gitlab push... | 13:31 |
| alicef | the comparison results use KernelCI results as the format is standardized | 13:32 |
| alicef | currently working on gitlab is mostly duplicating the work as KernelCI is already covering most of the work | 13:32 |
| pav31 | Yes, Im talking about the old system. | 13:32 |
| pav31 | I dont see kernelci as a replacement. | 13:33 |
| alicef | I don't think we have reasons to go on adding new tests to the old system | 13:33 |
| pav31 | By running tests on our systems we can run them as needed, without competing with kernelci stuff. | 13:34 |
| alicef | why not ? what we are missing ? we are using the same boards as the old system and the work on KernelCI is following your descriptions | 13:34 |
| pav31 | Old system was getting results in half an hour. | 13:35 |
| alicef | as patersonc[m] said we can your branch to kernelci and you can get your results | 13:35 |
| pav31 | Thats needed for development and not feasible with kernelci afaict. | 13:35 |
| alicef | you can send build requests also to KernelCI | 13:36 |
| iwamatsu | We haven't done any pre-release testing on kernelci with our test branch right now, so if we can do this, it's okay, I think. | 13:37 |
| alicef | is probably something to be discussed with KernelCI TSC but as also patersonc[m] said is something possible | 13:37 |
| alicef | developing both for KernelCI and the old system is not a feasible solution in the long run | 13:38 |
| alicef | and using KernelCI we can use KernelCI resources | 13:39 |
| alicef | both development and hardware related | 13:39 |
| pav31 | I'm not sure kernelci is suitable for all our needs. | 13:39 |
| jki | what is needed to find that out? | 13:40 |
| pav31 | We may need a lot of hardware resources if we'll need to chase a bug. | 13:40 |
| alicef | all the requirement I got for moving to KernelCI from CIP testing team are currently implemented | 13:41 |
| jki | pav31: is there anything concrete that should be tried out with kernelci? or explained how to do that? | 13:42 |
| alicef | I got a list from patersonc[m] about all the requirement that KernelCI should satisfy and currently that list is almost done | 13:42 |
| pav31 | I am worried about latency between submitting test tree and getting results back. | 13:43 |
| alicef | if you want you can ask to patersonc[m] | 13:43 |
| jki | pav31: is anything still missing for you to actually test that? | 13:44 |
| jki | numbers would likely help with this discussion | 13:44 |
| alicef | sorry I don't have much time open to discussion today. if you have request, please add a issue to kernelci-core with the label cip | 13:44 |
| pav31 | I guess we'll find out when we try to debug real problem. | 13:45 |
| alicef | pav31: KernelCI build can be limited to only a laboratory | 13:45 |
| alicef | but if you want a account on the jenkins staging for pushing new build you need to ask to request for a account | 13:46 |
| alicef | and you can make your own push request with only your rt kernels and only lab cip laboratory for example | 13:47 |
| alicef | ok | 13:48 |
| alicef | but if need something just send a request | 13:48 |
| iwamatsu | If my underdtanding is correct, I thought the issue was that the flow from push a branch to sending test results from KernelCI was unclear. | 13:48 |
| alicef | or I don't know what you need | 13:49 |
| iwamatsu | Will push be hooked on kernelCI immediately? | 13:49 |
| alicef | in case that you can get a account on kernelCI staging yes | 13:50 |
| alicef | that is a possibility | 13:51 |
| alicef | I will ask to TSC for ideas on how I can get you an account | 13:52 |
| alicef | if is needed | 13:52 |
| pav31 | I guess at least me and iwamatsu will need an account... | 13:53 |
| jki | ok, thanks in advance! | 13:53 |
| iwamatsu | I see. | 13:53 |
| jki | and a guided test run might also help, I think | 13:53 |
| iwamatsu | Same test as now, I want the test result in a few hours after pushing. | 13:54 |
| alicef | I will try to ask | 13:55 |
| alicef | but please make a list of what you need | 13:55 |
| iwamatsu | OK, thanks. | 13:56 |
| alicef | because from patersonc[m] requirements list the work on kernelCI is pratically done | 13:56 |
| alicef | and I already worked on that | 13:56 |
| jki | good - anything else regarding testing? | 13:58 |
| jki | 3 | 13:58 |
| jki | 2 | 13:58 |
| jki | 1 | 13:58 |
| jki | #topic AOB | 13:58 |
| *** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:58 | |
| jki | anyone any business? | 13:59 |
| alicef | no | 13:59 |
| jki | 3 | 13:59 |
| jki | 2 | 13:59 |
| jki | 1 | 13:59 |
| jki | #endmeeting | 14:00 |
| brlogger` | Meeting ended Thu Dec 9 14:00:00 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:00 |
| brlogger` | Minutes: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-09-13.01.html | 14:00 |
| brlogger` | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-09-13.01.txt | 14:00 |
| brlogger` | Log: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-09-13.01.log.html | 14:00 |
| *** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 14:00 | |
| pav31 | Thank you, stay safe. | 14:00 |
| jki | then thank you all for your time! | 14:00 |
| jki | you too, bye! | 14:00 |
| uli | bye | 14:00 |
| alicef | ah iwamatsu the development changes on what branch are they ? | 14:00 |
| masami | thank you | 14:00 |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC | 14:00 | |
| iwamatsu | thank you | 14:00 |
| alicef | are you using any special branch that I'm not aware ? | 14:00 |
| alicef | anyway you could also keep a copy of kernelci-core under your github username and use changes from that fork to send push request to a branch that is not upstream | 14:02 |
| iwamatsu | well, we are using ci/USER/* branch. | 14:02 |
| alicef | but that is all due to if TSC agree to give you a account or they found a different way. | 14:03 |
| *** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC | 14:03 | |
| alicef | like keeping a special for of kernelci for cip | 14:03 |
| alicef | anyway gtg | 14:03 |
| alicef | let's talk at the next meeting | 14:04 |
| iwamatsu | For example, I am using ci/iwamatsu/linux-5.10.y-rc for pre-release testing. | 14:04 |
| alicef | bye | 14:04 |
| iwamatsu | ok | 14:04 |
| alicef | bye iwamatsu | 14:04 |
| iwamatsu | bye | 14:04 |
| *** pav31 <pav31!~mobian@78-80-24-40.customers.tmcz.cz> has quit IRC | 14:04 | |
| alicef | yes that should work | 14:05 |
| alicef | you can keep a fork of kernelci-core with such branch as testing tree and sending push for that from jekins staging | 14:06 |
| alicef | just you will get results on staging instead of production | 14:07 |
| alicef | I'm doing it sometime for testing my kernelci code changes and others pull requests | 14:08 |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has joined #cip | 14:17 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 14:42 | |
| *** jki <jki!~jki@165.225.27.15> has quit IRC | 15:10 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC | 15:40 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 15:40 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC | 15:48 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 15:53 | |
| *** gavinlai <gavinlai!~gavin@139.59.249.25> has quit IRC | 16:13 | |
| *** gavinlai <gavinlai!~gavin@139.59.249.25> has joined #cip | 16:13 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 16:56 | |
| *** pav31 <pav31!~mobian@78-80-121-121.customers.tmcz.cz> has joined #cip | 17:11 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::45a> has quit IRC | 18:02 | |
| *** toscalix <toscalix!~toscalix@44.red-79-155-67.dynamicip.rima-tde.net> has quit IRC | 18:31 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 18:47 | |
| *** pav31 <pav31!~mobian@78-80-121-121.customers.tmcz.cz> has quit IRC | 19:29 | |
| *** toscalix_ <toscalix_!~agustinbe@44.red-79-155-67.dynamicip.rima-tde.net> has joined #cip | 20:31 | |
| *** toscalix_ <toscalix_!~agustinbe@44.red-79-155-67.dynamicip.rima-tde.net> has joined #cip | 20:35 | |
| *** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC | 20:48 | |
| *** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC | 20:49 | |
| *** pav31 <pav31!~mobian@37-48-11-82.nat.epc.tmcz.cz> has joined #cip | 21:36 | |
| *** pav31 <pav31!~mobian@37-48-11-82.nat.epc.tmcz.cz> has quit IRC | 21:52 | |
| *** toscalix_ <toscalix_!~agustinbe@44.red-79-155-67.dynamicip.rima-tde.net> has quit IRC | 22:01 | |
| *** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip | 22:24 | |
| *** alicefm <alicefm!~alicefm@user/alicefm> has joined #cip | 22:43 | |
| *** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has quit IRC | 22:47 | |
| *** alicefm <alicefm!~alicefm@user/alicefm> has quit IRC | 22:48 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 22:55 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!