| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC | 00:10 | |
| *** toscalix_ <toscalix_!~agustinbe@245.red-80-29-66.staticip.rima-tde.net> has quit IRC | 00:37 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:45 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC | 07:39 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 07:40 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 09:27 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip | 09:49 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC | 10:17 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip | 10:32 | |
| alicef | #startmeeting CIP IRC weekly meeting | 13:00 |
|---|---|---|
| brlogger | Meeting started Thu Dec 23 13:00:06 2021 UTC and is due to finish in 60 minutes. The chair is alicef. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:00 |
| brlogger | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| brlogger | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:00 |
| *** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:00 | |
| alicef | hello everyone! | 13:00 |
| iwamatsu | hi | 13:00 |
| patersonc[m] | Hello | 13:00 |
| masami | hi | 13:01 |
| alicef | ok I think we are everyone | 13:04 |
| alicef | let's get started | 13:04 |
| alicef | #topic AI review | 13:04 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| alicef | 1. Combine root filesystem with kselftest binary (finishing) - alicef | 13:05 |
| alicef | I'm just now re writing the cover letter for the isar-cip-core patch. hope to close this action in this week. | 13:06 |
| alicef | 2. Propose tweet on KernelCI-CIP collaboration progress - alicef | 13:06 |
| alicef | not worked on this yet | 13:06 |
| alicef | patersonc[m]: do you have any suggestion on this topic ? | 13:07 |
| patersonc[m] | Was there a specific feature/topic? | 13:07 |
| patersonc[m] | I think CIP retweeted KernelCI recently | 13:07 |
| alicef | oh nice :) | 13:07 |
| alicef | my suggestion was to tweet at least about the domain cip.kernelci.org and kernelci.cip.org | 13:08 |
| alicef | and maybe also about the kernelci cip dashboard with the work we are doing | 13:08 |
| patersonc[m] | okay | 13:09 |
| alicef | https://github.com/orgs/kernelci/projects/11 | 13:09 |
| patersonc[m] | https://twitter.com/cip_project/status/1458873920329814018 | 13:09 |
| alicef | :) | 13:09 |
| alicef | any other suggestion on this ? | 13:10 |
| alicef | 3 | 13:10 |
| alicef | 2 | 13:10 |
| alicef | 1 | 13:10 |
| alicef | 3. Clarify with KernelCI whether CIP maintainers can get accounts - alicef | 13:11 |
| alicef | I talked a bit yesterday at the TSC. KernelCI will try to enable it on staging and than depending on the traffic deciding further actions. still not sure about the time schedule that need to take for enabling it. | 13:12 |
| alicef | iwamatsu: can you give me the repositories and branches where this need to be enabled ? | 13:13 |
| alicef | something like for-kernelci | 13:14 |
| iwamatsu | OK, I and Pavel will create. | 13:15 |
| alicef | thanks, just send a mail to me with it when you have time :) | 13:15 |
| alicef | 3 | 13:16 |
| alicef | 2 | 13:16 |
| iwamatsu | o/ | 13:16 |
| alicef | 1 | 13:16 |
| alicef | #topic Kernel maintenance updates | 13:17 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| patersonc[m] | I'm sorry guys but I'm going to have to go - the office is shutting early :P | 13:17 |
| patersonc[m] | Have a good Christmas etc. | 13:17 |
| iwamatsu | we need to decide which gcc to support for each kernel. | 13:17 |
| masami | This week reported 12 new CVEs. Some of them aren't fixed yet. | 13:17 |
| alicef | patersonc[m]: i see, merry christmas | 13:17 |
| iwamatsu | patersonc: Happy holiday and new year. | 13:18 |
| masami | patersonc[m]: happy holidays! | 13:18 |
| alicef | iwamatsu: oh yes I read the mail about gcc, currently kernelci is using gcc 10 afair | 13:18 |
| iwamatsu | 4.19.y and 5.10.y can be matched to cip-core (Debian), but 4.4.y will probably be Debian 8 (Jessie) 's gcc. | 13:19 |
| alicef | oh because of debian compatibility, i see | 13:19 |
| alicef | what gcc is using cip-core ? | 13:20 |
| iwamatsu | maybe current cip-core is using gcc-8 | 13:21 |
| iwamatsu | this based on debian 10. | 13:21 |
| iwamatsu | current developing cip-core is using gcc-10. | 13:21 |
| iwamatsu | We are now using one container and gcc from kernel.org, so we need each container. | 13:22 |
| iwamatsu | Building this is not that difficult. | 13:22 |
| alicef | i see | 13:23 |
| iwamatsu | and Debian 8's gcc is gcc-4.9 | 13:23 |
| alicef | wow | 13:23 |
| alicef | so we will freeze a gcc version for each cip version? | 13:25 |
| alicef | minor version | 13:25 |
| alicef | s/minor/major/ | 13:26 |
| alicef | like 5.10 will have a gcc version and 4.4 will have a different one | 13:26 |
| iwamatsu | probably, yes. | 13:26 |
| alicef | maybe just adding revision updates to the freezed gcc version | 13:27 |
| alicef | that should not break compability i hope | 13:28 |
| alicef | iwamatsu: you will work on this ? | 13:28 |
| iwamatsu | I dont have a plan now, but I can do this | 13:29 |
| iwamatsu | (maybe I will work with patersonc) | 13:29 |
| alicef | sure, thanks :) | 13:30 |
| iwamatsu | So, I don't make any conclusions now, but I think it's better to decide at IRC meeting that will be held before the next TSC. | 13:30 |
| alicef | right, i agree | 13:30 |
| alicef | but still nice to know the current situation, thanks | 13:31 |
| alicef | masami: thanks for the report on the CVE | 13:31 |
| alicef | anything you want to add ? | 13:31 |
| iwamatsu | Perhaps the Jessie-based environment is difficult. This is old so he needs to build a cross environment..... | 13:31 |
| masami | alicef: no problems. | 13:31 |
| iwamatsu | BTW, I am reviewing 5.10.88. | 13:32 |
| alicef | I see, from KernelCI point there should no problem to build with gcc 8 and gcc 10. no idea about gcc-4.9 that's antiquate | 13:32 |
| iwamatsu | hehe | 13:33 |
| alicef | currently we are building cip 4.4 also with gcc 10. I'm surprised it works | 13:33 |
| *** pav31 <pav31!~mobian@nat-179.starnet.cz> has joined #cip | 13:34 | |
| pav31 | hi! | 13:34 |
| alicef | pav31: hi | 13:34 |
| iwamatsu | hi, Pavel. | 13:34 |
| pav31 | I was reviewing 5.10.88 and renesas patches. | 13:34 |
| masami | hi! | 13:34 |
| alicef | we are talking about cip-core using different gcc versions | 13:34 |
| pav31 | And .... sorry for being late. | 13:35 |
| alicef | emh cip kernel been build on different gcc versions | 13:35 |
| alicef | pav31: no problem :) | 13:35 |
| iwamatsu | some years ago, I created docker file for Jessie cross compile environment. | 13:36 |
| iwamatsu | https://github.com/iwamatsu/docker-jessie-cross-toolchain | 13:36 |
| pav31 | Yes. 5.10.87 or so will break gcc 8 plugins in our config. | 13:36 |
| alicef | anything else to add ? | 13:39 |
| alicef | pav31: will break gcc_plugins like been forcibly disabled ? | 13:40 |
| pav31 | I'm not sure I understand. | 13:41 |
| pav31 | We see broken builds on 5.10.88. | 13:42 |
| alicef | oh yes i see | 13:42 |
| pav31 | Likely we could fix it with changes to config or to build environment. | 13:42 |
| iwamatsu | CONFIG_GCC_PLUGINS | 13:43 |
| pav31 | Yes, that one. | 13:44 |
| pav31 | Could we simply disable it for now? | 13:44 |
| iwamatsu | probably yes. but we need to confirm. | 13:45 |
| pav31 | Do we have separate configs for cip and stable? | 13:46 |
| iwamatsu | current cip-kernel-config's config does not have CONFIG_GCC_PLUGINS. | 13:47 |
| alicef | i see, so that is disabled by default ? | 13:48 |
| iwamatsu | pav31: some builds use defconfg in kernel. | 13:49 |
| pav31 | Ay. Aha.... | 13:50 |
| iwamatsu | https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1911267343 | 13:51 |
| iwamatsu | https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1911267343#L911 | 13:52 |
| alicef | we have something to decide here? or can we move on and move back this to the mailing list ? | 13:52 |
| iwamatsu | This uses the config of cip-kernel-config, but I'm getting an error. | 13:53 |
| iwamatsu | A little resea | 13:53 |
| iwamatsu | research is needed. | 13:53 |
| pav31 | So probably better discussed on the list. | 13:55 |
| iwamatsu | +1 | 13:55 |
| alicef | yes, thanks | 13:55 |
| alicef | can we go on ? | 13:55 |
| alicef | 3 | 13:55 |
| alicef | 2 | 13:55 |
| alicef | 1 | 13:55 |
| alicef | #topic Kernel testing | 13:56 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:56 | |
| iwamatsu | aha, some config included CONFIG_HAVE_GCC_PLUGINS. | 13:56 |
| iwamatsu | This is the cause. | 13:56 |
| alicef | oh i see, that could cause the problem even without config_gcc_Plugins | 13:57 |
| alicef | about kernel testing we already discussed this. iwamatsu will send me the list of repo and branch that are for development and each commit will be tested by kernelci | 13:58 |
| alicef | I have nothing more to add, at now | 13:58 |
| alicef | 3 | 13:58 |
| alicef | 2 | 13:59 |
| alicef | 1 | 13:59 |
| alicef | #topic AOB | 13:59 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:59 | |
| alicef | vacations and lockdowns? | 13:59 |
| alicef | any vacation schedule ? | 13:59 |
| pav31 | Heh. Our government decided covid is not dangerous... | 14:00 |
| pav31 | So likely extended lockdown in january. | 14:00 |
| alicef | i see. we will have a meeting also 30 december ? | 14:00 |
| iwamatsu | Perhaps Japanese will be on vacation next week and next next week. | 14:01 |
| pav31 | I believe we decided not to at the last meeting. | 14:01 |
| alicef | right, so next meeting will be 6 january | 14:01 |
| alicef | 2022!... | 14:02 |
| iwamatsu | s/next next/week after next/ | 14:02 |
| alicef | is ok for 6 january ? or is better to move it later ? | 14:02 |
| masami | 6th is ok for me | 14:03 |
| pav31 | 6 is ok. | 14:03 |
| iwamatsu | me too. | 14:03 |
| alicef | is ok also for me | 14:03 |
| alicef | have a nice new year! | 14:03 |
| alicef | and let's close the meeting for today | 14:04 |
| alicef | 3 | 14:04 |
| alicef | 2 | 14:04 |
| alicef | 1 | 14:04 |
| alicef | #endmeeting | 14:04 |
| brlogger | Meeting ended Thu Dec 23 14:04:37 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:04 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-23-13.00.html | 14:04 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-23-13.00.txt | 14:04 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2021/12/cip.2021-12-23-13.00.log.html | 14:04 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 14:04 | |
| alicef | thanks everyone | 14:04 |
| pav31 | Happy holidays and stay safe... | 14:04 |
| masami | happy holidays ! see you next year. | 14:05 |
| iwamatsu | thank you and happy holidays. | 14:05 |
| alicef | p.s. we had a similar problem with gcc_plugins also on gentoo but a bit different | 14:05 |
| alicef | recently with gcc11 | 14:05 |
| alicef | happy holidays | 14:05 |
| alicef | see you on 6 January | 14:06 |
| *** pav31 <pav31!~mobian@nat-179.starnet.cz> has quit IRC | 14:14 | |
| *** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC | 14:47 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC | 22:29 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!