| *** yamamodo has joined #cip | 01:33 | |
| *** therisen has joined #cip | 06:19 | |
| *** rajm has joined #cip | 06:39 | |
| *** therisen has quit IRC | 06:44 | |
| *** therisen has joined #cip | 06:48 | |
| *** angeloc has joined #cip | 08:32 | |
| *** kazu has joined #cip | 08:52 | |
| *** pave1 has joined #cip | 08:58 | |
| *** vidda has joined #cip | 08:59 | |
| szlin | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger | Meeting started Thu Aug 1 09:00:02 2019 UTC and is due to finish in 60 minutes. The chair is szlin. 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 | |
| szlin | #topic rollcall | 09:00 |
| *** brlogger changes topic to "rollcall (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| szlin | please say hi if you're around | 09:00 |
| pave1 | hi | 09:00 |
| kazu | hi | 09:00 |
| vidda | hi | 09:00 |
| patersonc | hi | 09:00 |
| bwh | hi | 09:00 |
| szlin | #topic AI review | 09:00 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| szlin | 1. Provide the script for CIP kernel config collection - bwh | 09:01 |
| fujita[m] | hi | 09:01 |
| szlin | #link https://lists.cip-project.org/pipermail/cip-dev/2019-June/002506.html | 09:01 |
| bwh | I think this is done | 09:01 |
| szlin | bwh: thank you | 09:01 |
| szlin | 2. Work out a solution for LAVA master backups - patersonc | 09:01 |
| yamamodo | hi | 09:01 |
| patersonc | Not done. Sorry! | 09:02 |
| szlin | patersonc: no worry | 09:02 |
| szlin | 3. Provide the cases to cip-testing to build up the test environment - Iwamatsu-san | 09:02 |
| szlin | Iwamatsu-san cannot attend today's meeting, I will ask him after the meeting | 09:02 |
| szlin | 4. Ask cip-dev which configurations need testing - patersonc | 09:03 |
| patersonc | I asked, no response yet though :( | 09:03 |
| szlin | patersonc: it's in my work queue, sorry for late | 09:03 |
| patersonc | np | 09:04 |
| pave1 | If you are collecting configurations, would it be possible to add the results to the README file? | 09:04 |
| pave1 | Name of target we normally use, name of target in the LAVA lab, config... | 09:04 |
| patersonc | pave1: That's my plan | 09:05 |
| pave1 | patersonc: Thanks! | 09:05 |
| patersonc | pave1: I just need to get the info from those who know :) | 09:05 |
| pave1 | :-) | 09:05 |
| szlin | 5. Confirm we can enable high-res timers for every board - pavel | 09:05 |
| pave1 | I guess I need to hear from people who konw about the configs... | 09:06 |
| pave1 | ...or we can just enable it and see what happens. I don't expect problems there. | 09:06 |
| *** angeloc has quit IRC | 09:06 | |
| patersonc | The RZ/G boards should be okay | 09:07 |
| szlin | How about sending the email to cip-members mailing list | 09:08 |
| pave1 | It was outlined in "plan for rt testing" email, but I did not get much response there. | 09:08 |
| pave1 | I can try again I guess. | 09:09 |
| szlin | pave1: thanks | 09:09 |
| szlin | 7. Test LTS (pre)releases directly - patersonc | 09:09 |
| patersonc | Nothing done on that front yet. | 09:10 |
| szlin | 8. Discuss the primary repository in CIP kernel development (kernel.org or gitlab) - kernel team | 09:10 |
| szlin | I plan to send the email to discuss this item before this week | 09:11 |
| szlin | #topic Kernel maintenance updates | 09:11 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:11 | |
| szlin | pave1: do you have any updates on kernel maintenance? | 09:11 |
| pave1 | There was ton of patches in stable. Reviewed 4.19.61, 4.19.62, 4.19.63. | 09:11 |
| pave1 | Hopefully it should now calm down now. | 09:12 |
| szlin | pave1: thank you. | 09:12 |
| szlin | bwh: do you have any updates with this topic? | 09:12 |
| bwh | no I don't | 09:13 |
| szlin | any other points? | 09:13 |
| szlin | 3 | 09:13 |
| szlin | 2 | 09:13 |
| szlin | 1 | 09:13 |
| szlin | #topic Kernel testing | 09:13 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:13 | |
| patersonc | Changes to the directory structure of cip-kernel-config broke my CI setup :( | 09:14 |
| szlin | oops | 09:14 |
| patersonc | So I've submitted some new versions of gitlab-ci.yml to the ML | 09:14 |
| patersonc | It would be good if they could be reviewed/applied asap | 09:14 |
| pave1 | Yep, thanks, I'll take a look and merge them. | 09:14 |
| patersonc | Thanks | 09:14 |
| patersonc | I'm still waiting on official approval to move the linux-cip-ci project to the cip-project namespace | 09:15 |
| szlin | #action Review and merge "gitlab-ci.yml" - pavel | 09:15 |
| patersonc | When I get approval, I'll submit more updates for gitlab-ci.yml - sorry for the churn. | 09:15 |
| patersonc | And when people tell me what configs they want to build, there will also be more updates to the CI files... | 09:15 |
| patersonc | Powerpc support is done, although not merged yet. I'm just waiting for confirmation from Toshiba that they are happy to ignore the build warnings triggered by gcc v8.1.0 | 09:16 |
| patersonc | Ideally we should fix these warnings though... | 09:17 |
| pave1 | patersonc: Well, they are known to be caused by gcc bug... | 09:17 |
| patersonc | Ah, so not a bug in the code then? | 09:17 |
| pave1 | ...and testing any changes there will not be trivial. | 09:17 |
| patersonc | Here's a question - did CIP ever decide on a GCC version we're meant to be using/supporting? | 09:18 |
| pave1 | I posted pointer to gcc bugzilla IIRC... so no, this not kernel problem. | 09:18 |
| pave1 | And yes, it could be solved by using different gcc version. | 09:18 |
| szlin | kazu: ^ do you have any idea ? | 09:18 |
| pave1 | But I believe just disabling the warning is also fine. | 09:18 |
| fujita[m] | GCC version should be follow to CIP core | 09:19 |
| kazu | We discussed about this topics, | 09:19 |
| szlin | kazu: let's have some discussion after the meeting | 09:20 |
| szlin | any other points? | 09:20 |
| szlin | 3 | 09:20 |
| szlin | 2 | 09:20 |
| szlin | 1 | 09:20 |
| szlin | #topic CIP Core | 09:20 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:20 | |
| kazu | then planning to drop the requirements about this issue | 09:20 |
| kazu | we would like to share the information later... | 09:21 |
| kazu | regarding CIP-Core, thank you very much for many discussion in OSSJ! | 09:21 |
| kazu | Package decision process (PDP): | 09:21 |
| kazu | [WIP] A script to generate run-time package lists are now being implemented | 09:21 |
| kazu | We would provide a draft in the next TSC meeting | 09:22 |
| kazu | CIP security depends on this work, so working with high priority | 09:22 |
| kazu | FYI: DebConf19 info: #link https://lists.cip-project.org/mailman/private/cip-members/2019-July/002034.html | 09:22 |
| kazu | regarding Reproducible Builds, | 09:22 |
| kazu | Short summary: The most (around 90%) packages CIP requested are reproducible, under the condition the build path is not variant | 09:23 |
| kazu | Now we (TOSHIBA) are planinng to | 09:23 |
| kazu | 1. try steps to reproduce packages with srebuild (in our local) | 09:23 |
| kazu | 2. look at remaining Reproducible Builds issues in buster/bullseye then consider creating patches to fix them | 09:23 |
| kazu | If you are interested in this topic, please let me know | 09:24 |
| kazu | Debian LTS/ELTS: | 09:24 |
| kazu | I've summarized the latest state, especially about ELTS (current target: wheezy). Please check the email to cip-members about this | 09:24 |
| kazu | [WIP] TOSHIBA is now confirming the requirements of ELTS for jessie. | 09:24 |
| kazu | We will send the summary to Renesas members then share our direction in TSC. | 09:25 |
| kazu | That's all from me, If any other AIs I'm missing, please let me know | 09:25 |
| szlin | kazu: thank you for your update. | 09:25 |
| szlin | any question? | 09:25 |
| szlin | 3 | 09:26 |
| szlin | 2 | 09:26 |
| szlin | 1 | 09:26 |
| szlin | #topic Software update | 09:26 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:26 | |
| szlin | kazu: is Daniel around? | 09:26 |
| kazu | No | 09:26 |
| kazu | sorry, I cannot tell the updates about this topic today... | 09:27 |
| szlin | kazu: thanks, I will jump to next topic | 09:27 |
| szlin | any other points? | 09:27 |
| szlin | 3 | 09:27 |
| szlin | 2 | 09:27 |
| szlin | 1 | 09:27 |
| szlin | #topic AOB | 09:27 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:27 | |
| szlin | any other business? | 09:27 |
| szlin | 3 | 09:28 |
| szlin | 2 | 09:28 |
| szlin | 1 | 09:28 |
| szlin | #endmeeting | 09:28 |
| brlogger | Meeting ended Thu Aug 1 09:28:16 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:28 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2019/08/cip.2019-08-01-09.00.html | 09:28 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2019/08/cip.2019-08-01-09.00.txt | 09:28 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2019/08/cip.2019-08-01-09.00.log.html | 09:28 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:28 | |
| szlin | thank you all | 09:28 |
| pave1 | Thank you! | 09:28 |
| yamamodo | thank you | 09:28 |
| fujita[m] | Thank you! | 09:28 |
| szlin | kazu: regarding the gcc version | 09:28 |
| szlin | kazu: IIRC, we use the version in Debian | 09:28 |
| bwh | thank you | 09:28 |
| kazu | I should confirm again but, we used the kernel 4.4 + that config for PPC target with Debian GCC in squeeze | 09:30 |
| kazu | Regarding GCC version supported in CIP, it would be gcc versions supported in Debian (9, 10, ...) | 09:32 |
| szlin | kazu: squeeze is Debian 6 | 09:32 |
| patersonc | FYI, at the moment for CI building the Kernel I'm using the prebuilt compilers from https://cdn.kernel.org/pub/tools/crosstool/files/bin | 09:32 |
| kazu | szlin:Yes, we used that with old Debian (4-5 years ago maybe) | 09:33 |
| *** vidda has quit IRC | 09:34 | |
| pave1 | I believe we should try to support newer gcc-s as well. | 09:35 |
| patersonc | pave1: Did you push my gitlab-ci changes? I've just seen a lot of test jobs come through :) | 09:35 |
| pave1 | Running old distributions is okay on targets, but not so much fun on development machines. | 09:36 |
| pave1 | patersonc: Not me :-). | 09:36 |
| szlin | kazu: that means we need to use gcc v8.3 (Debian 9) | 09:36 |
| pave1 | Actually, can you check? It seems that Iwamatsu applied your yml updates last night. | 09:37 |
| patersonc | It looks like Iwamatsu-san committed about an hour a go | 09:37 |
| patersonc | Happy days | 09:37 |
| patersonc | Anyway, back to GCC discussion... | 09:37 |
| kazu | szlin: Yes, I think it's OK for kernel testing... | 09:37 |
| pave1 | :-) Ok, so nothing to do for me here. | 09:38 |
| kazu | I didn't mean that we require old gcc (squeeze) for kernel testing | 09:39 |
| kazu | We (Toshiba) should check the config for PowerPC again... | 09:40 |
| szlin | kazu: you mean we have to use gcc v8.3 in testing, right? | 09:40 |
| kazu | szlin: sorry, I don't correctly understand the current kernel testing policy, but | 09:41 |
| kazu | Is gcc v8.3 is the current gcc version used in kernel testing? | 09:42 |
| kazu | or using newer one? | 09:42 |
| patersonc | kazu: At the moment I'm just using GCC from Kernel.org, v8.1.0. That's because it's the newest one there. What I want to know is, which compiler *should* I be using. What are CIP planning to support for 10+ years? Do we plan to use a different GCC version for each Kernel version? | 09:42 |
| szlin | According to the link which Chris provided, the version of gcc is v8.1 | 09:43 |
| kazu | patersonc:thank you, understand | 09:43 |
| kazu | Currently, we have several Debian versions that CIP should maintain | 09:44 |
| kazu | (stretch, buster, ...) | 09:45 |
| patersonc | Also, I'm currently building in an Ubuntu 18.04 container. Should I be switching to pure Debian? Or does it not really matter? | 09:45 |
| kazu | But, regarding the combination of tested kernel version & complier, as far as i know, we don't have clear decision yet. | 09:45 |
| patersonc | kazu: Okay. I'll hold off changing the compiler until a decision has been reached. | 09:46 |
| kazu | patersonc sorry, i would add this topic to my action items | 09:46 |
| patersonc | Okay. Thank you! | 09:47 |
| kazu | thank you too | 09:47 |
| pave1 | I'd say that Ubuntu container is okay for now. | 09:48 |
| szlin | kazu: we will use the version of gcc which will be maintained in cip-core | 09:49 |
| patersonc | Okay | 09:49 |
| kazu | I also think that there is no problem with this, at the moment | 09:49 |
| kazu | I guess it might be better to use one of gcc versions that are (or will be?) supported by CIP (Debian 9, 10, ...), but more discussion is required to select the best one... | 09:51 |
| kazu | patersonc I would like to reply about this topic ASAP | 09:52 |
| szlin | kazu: got it, thank you. | 09:52 |
| patersonc | kazu: Thanks | 09:52 |
| patersonc | kazu: Who at Toshiba is managing Kernel configurations? | 09:53 |
| kazu | patersonc Currently, daniel is mainly doing | 09:53 |
| *** pave1 has quit IRC | 09:53 | |
| patersonc | kazu: Okay | 09:54 |
| *** kazu has quit IRC | 09:54 | |
| *** kazu has joined #cip | 09:56 | |
| kazu | patersonc: I will make a decision with Daniel & Iwamatsu-san about this topic soon | 09:57 |
| *** kazu has quit IRC | 09:59 | |
| *** tpollard has joined #cip | 10:14 | |
| *** CTtpollard has quit IRC | 10:14 | |
| *** yamamodo has quit IRC | 10:59 | |
| *** therisen has quit IRC | 15:12 | |
| *** rajm has quit IRC | 22:09 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!