| *** lchlan has joined #cip | 00:20 | |
| *** rynofinn has joined #cip | 00:33 | |
| *** rynofinn has quit IRC | 00:42 | |
| *** dl9pf has quit IRC | 00:42 | |
| *** lchlan has quit IRC | 00:42 | |
| *** rynofinn has joined #cip | 00:59 | |
| *** punit has joined #cip | 01:13 | |
| *** punit_ has joined #cip | 01:29 | |
| *** punit has left #cip | 01:29 | |
| *** rynofinn has quit IRC | 01:31 | |
| *** punit_ has quit IRC | 01:32 | |
| *** punit has joined #cip | 02:10 | |
| *** punit has quit IRC | 02:11 | |
| *** punit has joined #cip | 02:12 | |
| *** punit has quit IRC | 02:17 | |
| *** punit has joined #cip | 02:17 | |
| *** punit has joined #cip | 03:04 | |
| *** punit has quit IRC | 03:07 | |
| *** punit has joined #cip | 03:07 | |
| *** punit has quit IRC | 03:10 | |
| *** punit has joined #cip | 03:11 | |
| *** dl9pf has joined #cip | 06:55 | |
| *** lchlan has joined #cip | 06:59 | |
| *** rajm has joined #cip | 07:09 | |
| *** rynofinn has joined #cip | 07:11 | |
| *** therisen has joined #cip | 07:39 | |
| *** masashi910 has joined #cip | 07:58 | |
| *** pave1 has joined #cip | 08:57 | |
| *** fujita3 has joined #cip | 08:59 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger` | Meeting started Thu Jan 16 09:00:02 2020 UTC and is due to finish in 60 minutes. The chair is masashi910. Information about MeetBot at http://wiki.debian.org/MeetBot. | 09:00 |
| brlogger` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 09:00 |
| brlogger` | The meeting name has been set to 'cip_irc_weekly_meeting' | 09:00 |
| *** brlogger` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | #topic rollcall | 09:00 |
| *** brlogger` changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| pave1 | hi | 09:00 |
| masashi910 | please say hi if you're around | 09:00 |
| fujita3 | hi | 09:00 |
| masashi910 | #topic AI review | 09:01 |
| *** brlogger` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
| masashi910 | 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san | 09:01 |
| masashi910 | == Quote from Iwamatsu-san == | 09:01 |
| masashi910 | I tested on LAVA. But not finished. | 09:01 |
| masashi910 | https://lava.ciplatform.org/scheduler/job/9499 | 09:01 |
| masashi910 | ==== | 09:01 |
| masashi910 | I keep this AI open. | 09:01 |
| masashi910 | 2. Document a process on how to add tests to the CIP test setup - patersonc | 09:02 |
| masashi910 | patersonc: are you around? | 09:02 |
| pave1 | It seems that there's just three of us here. | 09:02 |
| masashi910 | pave1: right... | 09:02 |
| patersonc | I'm in traffic | 09:02 |
| bwh | (hi)) | 09:02 |
| masashi910 | patersonc: Hi! | 09:03 |
| patersonc | 15 mins I'll be online | 09:03 |
| masashi910 | bwh: Hi! | 09:03 |
| patersonc | Sorry | 09:03 |
| masashi910 | patersonc: I see. Then, I will revisit your topics later. | 09:03 |
| masashi910 | 3. Arrangement of F2F Kernel Meeting in Nuremberg - masashi910 | 09:04 |
| masashi910 | https://doodle.com/poll/73if9scwqrh5ge38 | 09:04 |
| *** kazu has joined #cip | 09:04 | |
| masashi910 | I keep this doodle poll open for a while, so, please fill your preference if you are interested in joining. | 09:04 |
| masashi910 | If you would like to attend remotely, please also let me know. | 09:05 |
| masashi910 | 4. Add config for qemux86-64 and BBB to both 4.4 and 4.19 - Iwamatsu-san | 09:05 |
| *** kazu71 has joined #cip | 09:05 | |
| *** kazu has quit IRC | 09:05 | |
| masashi910 | == Quote from Iwamatsu-san == | 09:05 |
| masashi910 | Qemux86-64's config already merged to cip-kernel-config. | 09:05 |
| masashi910 | BBB config is under testing. Please keep this A.I. | 09:05 |
| masashi910 | ==== | 09:05 |
| masashi910 | So, I keep this AI open. | 09:06 |
| masashi910 | #topic kernel maintenance updates | 09:06 |
| *** brlogger` changes topic to "kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:06 | |
| masashi910 | Pavel-san, do you have updates? | 09:06 |
| pave1 | I did reviews on 4.19.94, 95 and 96. New 4.19-cip-rt kernel was released. | 09:07 |
| masashi910 | pave1: Thanks very much for your works! | 09:08 |
| bwh | I've backported fixes for several CVEs, which should go into stable updates soon | 09:09 |
| masashi910 | bwh: Great! Thanks very much! | 09:09 |
| wens | hi, I'm late | 09:09 |
| masashi910 | wens: Hi! Do you have updates? | 09:10 |
| wens | I did a run of classify-failed-patches, haven't posted the results yet | 09:10 |
| wens | didn't see anything critical | 09:10 |
| masashi910 | wens: Thanks very much for your works! | 09:11 |
| pave1 | bwh: There was/is discussion on the mailing list regarding to 4.19 end-of-life | 09:11 |
| pave1 | Do we have indications that someone else (Debian?) will maintain 4.19 after regular -stable maintainance ends? | 09:12 |
| bwh | No but I may take that on for Debian if necessary | 09:13 |
| wens | IIRC buster is on 4.19? | 09:14 |
| pave1 | Ok :-). | 09:14 |
| bwh | wens: yes | 09:14 |
| masashi910 | pave1: BTW do you have pointers for such a discussion? | 09:14 |
| pave1 | masashi910: It was your mail AFAICT, "Kernel Team Roadmap for CY2020", "1. Readiness for the self-maintenance | 09:15 |
| masashi910 | pave1: I see. :) | 09:15 |
| masashi910 | Any other topics? | 09:16 |
| masashi910 | 3 | 09:16 |
| masashi910 | 2 | 09:16 |
| masashi910 | 1 | 09:16 |
| masashi910 | Because Chris-san is not here, I will jump to CIP Core session. | 09:17 |
| masashi910 | #topic CIP Core | 09:17 |
| *** brlogger` changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:17 | |
| kazu71 | hello | 09:17 |
| masashi910 | kazu71: the floor is yours | 09:18 |
| kazu71 | It's time for me, or chris? | 09:18 |
| kazu71 | ah, chis not attend today sorry | 09:18 |
| masashi910 | kazu71: it's yours | 09:18 |
| kazu71 | 1. Update PDP to v3.1 https://lists.cip-project.org/pipermail/cip-dev/2020-January/004143.html | 09:18 |
| kazu71 | Add a rule to satisfy all run-time dependencies | 09:18 |
| kazu71 | cip-pkglist scripts also updated to check the deps automatically | 09:18 |
| kazu71 | 2. Created the 2nd package proposal for Debian minimum base system https://lists.cip-project.org/pipermail/cip-dev/2020-January/004160.html | 09:19 |
| kazu71 | 58 source packages and 84 binary packages are inclulded | 09:19 |
| kazu71 | I though that these packages should be discussed before (or in parallel with) the security WG proposal because there are many overwraped packages | 09:19 |
| kazu71 | (To CIP Core member company) Please tell your opinion about this proposal by the next TSC :) | 09:19 |
| kazu71 | 3. Generic profile: (WIP) Support cip-kenrel-config, testing isar-cip-core with linux-cip-ci | 09:19 |
| kazu71 | That's all from me | 09:19 |
| masashi910 | kazu71: thank you for your works! | 09:19 |
| masashi910 | Any questions or comments? | 09:20 |
| masashi910 | any other topics? | 09:20 |
| fujita3 | kazu71: it is better to review the security WG proposal in parallel | 09:20 |
| kazu71 | fujita3 OK, I'm discussing with Kent about this topic already | 09:21 |
| fujita3 | kazu71: shoud we check both source packages and binary packages? | 09:21 |
| fujita3 | source packages have higher priority? | 09:22 |
| kazu71 | fujita3 Yes, but binary packages are the main target of this review | 09:22 |
| kazu71 | binary packages are generated from the corresponding source package | 09:22 |
| fujita3 | ok. binary is higher | 09:22 |
| * patersonc arrives | 09:23 | |
| masashi910 | any other topics? | 09:23 |
| masashi910 | 3 | 09:23 |
| masashi910 | 2 | 09:23 |
| masashi910 | 1 | 09:23 |
| masashi910 | Because Chris-san just joined, let me go back to the testing. | 09:23 |
| kazu71 | patersonc Hello! | 09:23 |
| masashi910 | #topic Kernel testing | 09:24 |
| *** brlogger` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:24 | |
| masashi910 | patersonc: the floor is yours | 09:24 |
| patersonc | Hello | 09:24 |
| patersonc | I started looking into RT testing | 09:24 |
| patersonc | Please see my email to cip-dev. | 09:25 |
| patersonc | It would be good to get some input. | 09:25 |
| pave1 | Thanks for starting this! :-) | 09:25 |
| patersonc | Main discussion points are a) what tests we should run b) what packages to add to cip-core | 09:25 |
| pave1 | So I guess even cyclictest alone is useful, but it would be nice to run it with some background load. | 09:26 |
| patersonc | pave1: Okay | 09:26 |
| patersonc | I played around with hackbench before | 09:26 |
| patersonc | It would be good to know what/how the RT project does | 09:26 |
| kazu71 | patersonc Thank you for the updates. a) depends on b), is it correct? | 09:26 |
| kazu71 | Oops, b) depends on a) I meant... | 09:26 |
| pave1 | I was using kernel build (make -j 5) as a background load.. | 09:27 |
| patersonc | kazu71: I guess so :) | 09:27 |
| pave1 | Would that be possible/easy to do? | 09:27 |
| patersonc | pave1: That would mean including the toolchains in cip-core. Is this something already done kazu71 ? | 09:28 |
| pave1 | Yep, so that does not sound exactly easy. | 09:28 |
| patersonc | Or we could add things like Dhrystone or other benchmarks | 09:28 |
| patersonc | Let me take an action to ask the RT project what they do | 09:28 |
| pave1 | Dhrystone I'd say is not exactly suitable. | 09:29 |
| patersonc | We may as well do the same so we can compare results easier | 09:29 |
| pave1 | We may want to replicate what they do, yes; but if we discover something else that results in high latencies, we get bonus points. | 09:29 |
| pave1 | Perphaps we can talk after the meeting? | 09:29 |
| patersonc | pave1: Sure | 09:30 |
| masashi910 | patersonc: noted. you take the AI "ask RT project what they do for RT testing." | 09:30 |
| masashi910 | patersonc: Thanks for your updates! | 09:30 |
| patersonc | pave1: Where was the discussion about extending v4.19LTS? | 09:30 |
| patersonc | Is Iwamatsu-san online? | 09:30 |
| masashi910 | patersonc: no. he is not attending this call. | 09:31 |
| patersonc | Okay. Thanks | 09:31 |
| bwh | patersonc: So far that was private mail | 09:31 |
| pave1 | patersonc: "Kernel Team Roadmap for CY2020", I see you in the cc list. | 09:31 |
| patersonc | Ah okay. I thought you meant a discussion on linux-stable | 09:31 |
| masashi910 | patersonc: Yes. I sent the local mail to you. | 09:32 |
| patersonc | Thanks | 09:32 |
| masashi910 | patersonc: Thanks for your updates! | 09:32 |
| patersonc | No updates on my action btw. | 09:32 |
| * patersonc testing report done. | 09:32 | |
| masashi910 | patersonc: I see. Noted. | 09:32 |
| masashi910 | Any other topics? | 09:32 |
| masashi910 | 3 | 09:33 |
| masashi910 | 2 | 09:33 |
| masashi910 | 1 | 09:33 |
| masashi910 | #topic Software update | 09:33 |
| *** brlogger` changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:33 | |
| masashi910 | Quote from Suzuki-san "SW Updates WG doesn't have any update this week." | 09:33 |
| masashi910 | any other topics? | 09:33 |
| masashi910 | 3 | 09:33 |
| masashi910 | 2 | 09:33 |
| masashi910 | 1 | 09:33 |
| masashi910 | #topic AOB | 09:33 |
| *** brlogger` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:33 | |
| masashi910 | Are there any business matters to discuss? | 09:34 |
| patersonc | Has anyone seen the email from Dennis Semakin? | 09:34 |
| kazu71 | sorry, not yet | 09:34 |
| masashi910 | patersonc: What about? | 09:34 |
| pave1 | Seen: Obtain full set of source code for cip image | 09:34 |
| patersonc | Maybe we should add a wiki page describing how to customise CIP-Core | 09:35 |
| pave1 | It is more of build system question. | 09:35 |
| patersonc | (email is on cip-dev btw) | 09:35 |
| pave1 | patersonc: We should be able to simply pointer to someone else's documentation, no? | 09:35 |
| patersonc | pave1: Maybe, but the more information we share on such topics the more people who will be drawn to the project | 09:36 |
| patersonc | It's good to see someone trying to use our Kernel/FS | 09:37 |
| masashi910 | patersonc: Thanks for raising this issue. Will continue to discuss next week? | 09:38 |
| patersonc | Sure. | 09:38 |
| patersonc | I've now booked hotel/flights for Embedded World now btw. | 09:39 |
| masashi910 | patersonc: Great! | 09:39 |
| patersonc | Just for the two days of CIP meetings though | 09:39 |
| masashi910 | same here. | 09:39 |
| masashi910 | Any other business matters to discuss? | 09:40 |
| masashi910 | 3 | 09:40 |
| masashi910 | 2 | 09:40 |
| masashi910 | 1 | 09:40 |
| masashi910 | #endmeeting | 09:40 |
| brlogger` | Meeting ended Thu Jan 16 09:40:33 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:40 |
| brlogger` | Minutes: https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00.html | 09:40 |
| brlogger` | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00.txt | 09:40 |
| brlogger` | Log: https://irclogs.baserock.org/meetings/cip/2020/01/cip.2020-01-16-09.00.log.html | 09:40 |
| *** brlogger` changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:40 | |
| masashi910 | Thanks very much! See you nepave1xt week! | 09:40 |
| pave1 | Thank you! | 09:40 |
| wens | thank you | 09:40 |
| fujita3 | thank you | 09:41 |
| patersonc | Thanks. Apologies for being late. | 09:42 |
| kazu71 | patersonc "toolchain" above means... some software to make CPU/memory/disk loads that affects cyclictest results? | 09:42 |
| pave1 | bwh: If you/Debian is willing to maintain 4.19-stable in 2021+, I believe easiest way forward for CIP project is to simply keep using that. | 09:42 |
| patersonc | kazu71: I was referring to build-essential etc. | 09:43 |
| pave1 | bwh: If not, I believe best way forward for CIP would be to take over 4.19-stable maintainance; but I believe that would be more effort. | 09:43 |
| kazu71 | patersonc In the target rootfs? if so, isar-cip-core could provide them | 09:43 |
| patersonc | pavel: More effort, but wasn't this the original aim of the project? We should be doing it already for 4.4 but we got lucky :) | 09:44 |
| kazu71 | patersonc Deby provides (cross-)toolchain but it's not for target but for development environment | 09:44 |
| patersonc | kazu71: Sure. I guess we're going to have to have a 'kernel testing' version of cip-core. | 09:45 |
| kazu71 | patersonc I think so too | 09:45 |
| pave1 | patersonc: Well, our goal is really _subset_ of the kernel. If we took over -stable maintainence, we'd have to maintain _whole_ kernel. | 09:45 |
| pave1 | patersonc: I still believe it would be good idea, because we'd get more testing if our tree was exposed as "stable". | 09:46 |
| patersonc | pave1: True. sorry. Whether Greg would let us take over the 'official' maintenance of 4.19-stable is another question ;) | 09:46 |
| pave1 | patersonc: OTOH if Debian wants to do the job, I obviously would not complain. | 09:46 |
| kazu71 | patersonc BTW, are there any requests about the profiles (tiny/generic) for kernel/RT testing now? Should we provide either or both profiles for kernel testing? | 09:47 |
| pave1 | patersonc: I'm pretty sure Greg would let us do that if noone else is interested. | 09:47 |
| patersonc | kazu71: I'll start drawing up a list. I know that Iwamatsu-san created his own RFS for LTP testing, presumably because there were missing packages in cip-core | 09:48 |
| patersonc | pave1: :) | 09:48 |
| masashi910 | kazu71: please let me know your opinion about Dennis's mail and Chris-san's comment. | 09:48 |
| masashi910 | kazu71: Have you read Dennis mail? | 09:49 |
| kazu71 | patersonc OK, we will discuss about this topic F2F | 09:49 |
| kazu71 | masashi910 Partially. Maybe CIP Core should reply with information Dennis is asking | 09:50 |
| pave1 | patersonc: Some background load is important for cyclictest. Daniel provided loads he is using on the mailing list. | 09:51 |
| masashi910 | kazu71: Thanks for your comment. | 09:51 |
| pave1 | patersonc: Would it be easy for you to say download big tar archive then unpack it? | 09:51 |
| punit | Maybe a bit off-topic, but why are CIP core images needed for CIP kernel testing? | 09:52 |
| patersonc | pave1: Internet connection to the boards under test isn't guarantied, hence the need to pre-install dependencies in the rfs. It is possible to do something like that though, if the tar archive is present in the repository that the test case is stored in. | 09:52 |
| patersonc | punit: Technically they aren't. It just makes sense to me to use our own filesystem for testing, as it'll also help test cip-core. | 09:53 |
| patersonc | Maybe it's less essential than I think though...? | 09:53 |
| pave1 | patersonc: That might be a good start. Actually even unpacking single tarball multiple times (so that total ammount of data is comparable to ammount of RAM) would be interesting. | 09:54 |
| pave1 | patersonc: Is root filesystem for a test local or on NFS? | 09:54 |
| patersonc | NFS | 09:54 |
| punit | It does, but then we run into two issues - 1. not having a wide test coverage as cip-core is expected to be minimal. 2. expanding cip-core to be a lot more than it is today to cover all the requirements of the various test suites | 09:54 |
| kazu71 | punit Hello! My understanding is that it's better to use the same user land as CIP Core to test kernel because CIP kernel & core assume to be used together. | 09:55 |
| kazu71 | by users of CIP | 09:55 |
| patersonc | I'm sorry everyone, I have to head to another meeting. I should be back in an hour or so for any follow ups if anyone is still online. | 09:56 |
| pave1 | paterson: Ok.. | 09:56 |
| kazu71 | patersonc Thank you for the discussion! | 09:56 |
| masashi910 | patersonc: see you. | 09:56 |
| punit | kazu71: I understand about them being tested together. But the kernel test surface is quite large. And if we rely on external test suites then the dependencies grow quite large | 09:56 |
| pave1 | paterson: Thank you! | 09:56 |
| kazu71 | punit One important thing is that providing packages for testing doesn't mean that CIP Core will be responsible to maintain them | 09:57 |
| punit | Exactly, that's the point I wanted to get across | 09:58 |
| fujita3 | Technically we can make another list for testing kernel, but I don't think it is necessary. | 09:59 |
| punit | So then we are talking about assembling the necessary packages (including maintained) in a suitable image to enable testing | 09:59 |
| kazu71 | punit Core should provide two package list: 1) the important packages that will be maintained, 2) Available package list (for testing, debugging, performance evaluation, etc.) | 09:59 |
| kazu71 | fujita3 I have the same opinion | 10:00 |
| punit | kazu71: Makes sense. For 2) I wonder if we can defer to external distro such as debian... | 10:00 |
| punit | Also the related question about should this also be available for tiny profile.. | 10:01 |
| *** kazu has joined #cip | 10:03 | |
| kazu | sorry, disconnected suddenly... | 10:04 |
| kazu | punit I have similar concerns about tiny because we need to implement recipes in meta-debian if the packages are not available yet. | 10:05 |
| punit | :) | 10:05 |
| kazu | Actually, in generic profile, I guess we can install all Debian packages (in main component) by adding one or two definitions in kas file | 10:05 |
| *** kazu71 has quit IRC | 10:07 | |
| punit | Yes, so we need to better understand how to test the filesystem themselves | 10:08 |
| *** kazu has quit IRC | 10:13 | |
| *** pave1 has quit IRC | 10:19 | |
| * patersonc returns | 10:25 | |
| *** masashi910 has quit IRC | 10:27 | |
| *** fujita3 has quit IRC | 11:02 | |
| *** rajm has quit IRC | 11:21 | |
| *** rajm has joined #cip | 11:27 | |
| *** rajm has quit IRC | 11:33 | |
| *** rajm has joined #cip | 11:43 | |
| *** masashi910 has joined #cip | 12:50 | |
| *** masashi910 has quit IRC | 13:18 | |
| *** therisen has quit IRC | 16:18 | |
| *** cttpollard has quit IRC | 16:58 | |
| *** rajm has quit IRC | 22:52 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!