| *** Guest84521 has joined #cip | 07:13 | |
| yoshidak[m] | @freenode_masashi910:matrix.org: I cannot attend today's IRC due to schedule conflict. There is no update from SWG this week. | 07:45 |
|---|---|---|
| *** alicef_ has joined #cip | 07:53 | |
| *** samwilson has joined #cip | 08:04 | |
| *** fujita has joined #cip | 08:08 | |
| *** masashi910 has joined #cip | 08:51 | |
| *** pave1 has joined #cip | 08:57 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
| brlogger | Meeting started Thu Mar 11 09:00:01 2021 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 | |
| masashi910 | please say hi if you're around | 09:00 |
| pave1 | hi | 09:00 |
| masashi910 | Today, Iwamatsu-san is not here. Let's get started. | 09:01 |
| patersonc | hi | 09:01 |
| masashi910 | #topic AI review | 09:01 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
| masashi910 | 1. Combine root filesystem with kselftest binary - iwamatsu | 09:01 |
| masashi910 | According to Iwamatsu-san, "No update". | 09:01 |
| masashi910 | 2. Do some experiment to lower burdens on CI - patersonc | 09:01 |
| patersonc | No updates | 09:01 |
| masashi910 | patersonc: Noted. Thanks. | 09:01 |
| masashi910 | Let's move on. | 09:01 |
| masashi910 | #topic Kernel maintenance updates | 09:01 |
| *** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:01 | |
| masashi910 | According to Iwamatsu-san, "I reviewed 4.4.260, 5.10.21 and 5.10.22". | 09:02 |
| pave1 | I did reviews on 5.10.21, 22, 23 and related 4.19 kernels". | 09:02 |
| pave1 | Oh and the camera series from the Renesas. | 09:02 |
| masashi910 | pave1: Thanks for your works! | 09:02 |
| masashi910 | wens: are you around? | 09:02 |
| wens | hi | 09:03 |
| masashi910 | wens: Hi! | 09:03 |
| wens | I'm still working on the report, sorry. | 09:03 |
| wens | Summary: seven new issues this week, all fixed. | 09:03 |
| pave1 | wens: Boring report. Good! :-) | 09:03 |
| wens | :) | 09:03 |
| masashi910 | wens: Thanks for your works! | 09:04 |
| masashi910 | any other topics? | 09:04 |
| masashi910 | 3 | 09:04 |
| masashi910 | 2 | 09:04 |
| masashi910 | 1 | 09:04 |
| masashi910 | #topic Kernel testing | 09:04 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:04 | |
| patersonc | The main issue is that lab-cip-renesas is down, which means that the CI is failing all over the place due to lack of Renesas boards | 09:05 |
| patersonc | Sorry about this | 09:05 |
| patersonc | We use a seperate network for the lab and a big power outage did funny things to the old router we're using | 09:05 |
| patersonc | A new one is on order | 09:05 |
| wens | it happens :( | 09:05 |
| patersonc | Ironically this is exactly why we're trying to get boards into multiple labs | 09:06 |
| patersonc | We have some that have arrived at Denx, but covid has slowed down getting them installed | 09:06 |
| patersonc | Sorry if this gets in the way of the planned releases tomorrow | 09:07 |
| patersonc | If needed I can run some manual testing in our internal lava lab on the Renesas boards? | 09:07 |
| pave1 | Are you talking to Denx? Maybe the Covid situation got better there. | 09:07 |
| patersonc | pave1: I'll send an email now and check | 09:07 |
| pave1 | It would be iwamatsu doing the releases. But yes, I guess testing them would be good idea. | 09:08 |
| masashi910 | patersonc: Thanks for your works. | 09:09 |
| masashi910 | patersonc: I have a question. | 09:09 |
| masashi910 | Cybertrust is planning to propose Xilinx zcu102 as an official platform. | 09:09 |
| masashi910 | According to my understanding, currently, as a candidate platform, boot testing and Spectre/Meltdown checking are executed on the boards. | 09:09 |
| masashi910 | Once it is accepted as an official, LTP will be executed on the boards as well? | 09:09 |
| patersonc | Ideally we'd test LTP on all boards. It's just a question of making a suitable filesystem and updating a script or two | 09:10 |
| patersonc | And if the LTP tests take a while to run - making sure we have enough boards in the labs | 09:11 |
| pave1 | Doing LTP run manually on that board might be good idea. | 09:11 |
| pave1 | But I don't expect problems there. | 09:11 |
| masashi910 | As you know, currently CTJ lab has two zcu102. Our target branch is 5.10 only. | 09:12 |
| patersonc | masashi910: Although currently there is only 1 online? https://lava.ciplatform.org/scheduler/device_type/zynqmp-zcu102 | 09:12 |
| patersonc | masashi910: Would you be able to send 2 boards to Denx to put in their lab? | 09:13 |
| masashi910 | patersonc: zcu102 is costly. I am afraid we cannot afford to do so. | 09:13 |
| masashi910 | patersonc: I will check the status about the other one internally. | 09:14 |
| patersonc | Ah yes I remember now. That's okay | 09:14 |
| masashi910 | patersonc: Thanks. | 09:15 |
| masashi910 | any other topics? | 09:15 |
| masashi910 | 3 | 09:15 |
| masashi910 | 2 | 09:15 |
| masashi910 | 1 | 09:15 |
| masashi910 | #topic CIP Security | 09:15 |
| *** brlogger changes topic to "CIP Security (Meeting topic: CIP IRC weekly meeting)" | 09:15 | |
| *** tpollard has joined #cip | 09:15 | |
| masashi910 | Yoshida-san, are you around? | 09:15 |
| masashi910 | So, let's skip. | 09:16 |
| masashi910 | #topic AOB | 09:16 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:16 | |
| masashi910 | Are there any business to discuss? | 09:16 |
| pave1 | I guess we should talk about the zcu102. | 09:16 |
| masashi910 | pave1: Sure. | 09:16 |
| wens | No progress made on the Gitlab cip-kernel-sec merge request rebase by me yet. | 09:17 |
| pave1 | The plan with 5.10 seems sane, given that the board already works in 5.10. | 09:17 |
| masashi910 | wens: Sure. Thanks. | 09:17 |
| pave1 | Might be nice to call it zcu102 in all the relevant places, people may not realize zynqmp refers to same board. | 09:17 |
| pave1 | I believe we should just go ahead. | 09:18 |
| masashi910 | pave1: Thanks for your comments. If things go well, I can propose this at the next TSC, next Tuesday. | 09:18 |
| wens | Another thing, futex were broken in v4.9.y, and there were some additional patches that were backported to v4.4.y, is anyone tracking those? | 09:19 |
| pave1 | You have my support for that. | 09:19 |
| masashi910 | pave1: And yes, we should change the name approriately. | 09:19 |
| masashi910 | pave1: Thanks very much for your support!!! | 09:19 |
| pave1 | wens: No idea about 4.4. If you have pointers, I can take a look... or maybe we can do it over the email. | 09:21 |
| wens | pave1: latest ones I've seen: https://lore.kernel.org/stable/20210309030605.3295183-1-zhengyejian1@huawei.com/ | 09:22 |
| wens | v2 here: https://lore.kernel.org/stable/20210311032600.2326035-1-zhengyejian1@huawei.com/ | 09:23 |
| pave1 | Thanks! | 09:23 |
| pave1 | I guess... let me take a look and discuss over the mailing list. | 09:24 |
| wens | thanks | 09:24 |
| masashi910 | wens: Thanks for raising this issue. | 09:24 |
| masashi910 | wens, pave1: Should I make this as AI? | 09:24 |
| wens | there's no definitive list of futex-related patches | 09:24 |
| pave1 | Huawei/upstream is taking look, I don't think we need an AI :-). | 09:24 |
| wens | masashi910: I think they'll get queued up as normal | 09:24 |
| masashi910 | pave1, wens: Sure, thanks. | 09:25 |
| masashi910 | any other topics? | 09:25 |
| wens | Here is today's cip-kernel-sec report: https://lore.kernel.org/cip-dev/CAGb2v66-bSg43E7k+HYJv0CniGDwrW3GP4ewysjr-zX1y2fo1g@mail.gmail.com/ | 09:25 |
| masashi910 | wens: Thanks very much as always. | 09:26 |
| masashi910 | Maybe, it's time to close the meeting. | 09:26 |
| masashi910 | #endmeeting | 09:26 |
| brlogger | Meeting ended Thu Mar 11 09:26:36 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:26 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2021/03/cip.2021-03-11-09.00.html | 09:26 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2021/03/cip.2021-03-11-09.00.txt | 09:26 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2021/03/cip.2021-03-11-09.00.log.html | 09:26 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:26 | |
| masashi910 | Thank you, and stay safe! | 09:26 |
| patersonc | Sorry, 1 more thing | 09:26 |
| pave1 | Thank you! Stay safe, stay away from Czech republic... | 09:26 |
| patersonc | Did anyone see the conversation about the CIP SLTS master branch? | 09:27 |
| patersonc | Should we change it to track mainline? | 09:27 |
| pave1 | Not... really. What is it currently tracking? | 09:27 |
| patersonc | our 4.4 branch, but it's not tracking - it's stuck on a version from 2 years ago | 09:28 |
| patersonc | I don't mind what it tracks, as long as it's kept up to date | 09:28 |
| patersonc | It's meaningless to have it sit still on an out of date kernel | 09:29 |
| pave1 | I don't see great reason to update that. We have three main branches, not one special. | 09:29 |
| pave1 | We might want to somehow indicate this one is not in use. | 09:30 |
| patersonc | Or just remove the master branch completely | 09:30 |
| pave1 | ...which version stuck on 2 years old does nicely I guess :-). | 09:30 |
| pave1 | I'd vote for remove... if git survives that. | 09:30 |
| wens | I think they need a default branch | 09:31 |
| pave1 | https://matthew-brett.github.io/pydagogue/gh_delete_master.html | 09:32 |
| pave1 | wens: Random documentation agrees with you. | 09:32 |
| pave1 | One possibility is to "park" it on 5.10. Because that's our base after all. | 09:35 |
| wens | Sounds like a good option. | 09:36 |
| pave1 | (And it also makes it rather clear that there's nothing to see there). | 09:36 |
| pave1 | Lets discuss over email? | 09:40 |
| patersonc | Sasha was making some points about if we change the target of the master branch it would screw up git pull for those who use it | 09:40 |
| pave1 | Well, noone should really use our master branch. That should be clear by now :-). | 09:42 |
| patersonc | :P | 09:42 |
| *** masashi910 has quit IRC | 09:46 | |
| *** sashal has quit IRC | 10:07 | |
| *** fujita has quit IRC | 10:15 | |
| *** pave1 has quit IRC | 10:59 | |
| *** cp- has quit IRC | 11:11 | |
| *** cp- has joined #cip | 11:11 | |
| *** cp- has quit IRC | 11:21 | |
| *** cp- has joined #cip | 11:22 | |
| *** cp- has quit IRC | 11:23 | |
| *** cp- has joined #cip | 11:23 | |
| *** monstr has joined #cip | 11:24 | |
| *** cp- has quit IRC | 11:24 | |
| *** cp- has joined #cip | 11:41 | |
| *** sashal has joined #cip | 12:31 | |
| *** brlogger` has joined #cip | 13:03 | |
| *** iwamatsu` has joined #cip | 13:05 | |
| *** adds68_ has joined #cip | 13:07 | |
| *** brlogger has quit IRC | 13:07 | |
| *** iwamatsu has quit IRC | 13:08 | |
| *** adds68 has quit IRC | 13:08 | |
| *** cp- has quit IRC | 13:08 | |
| *** cp- has joined #cip | 13:08 | |
| *** samwilson has quit IRC | 13:40 | |
| *** samwilson has joined #cip | 13:45 | |
| *** cp- has quit IRC | 13:54 | |
| *** cp- has joined #cip | 13:55 | |
| *** pave1 has joined #cip | 14:02 | |
| *** pave1 has quit IRC | 14:11 | |
| *** adds68_ is now known as adds68 | 14:46 | |
| patersonc | FYI, lab-cip-renesas is fixed, however the internet connection is very unstable | 15:04 |
| patersonc | And if the internet dies mid-job sometimes the jobs don't timeout properly and will stay running forever until cancelled | 15:04 |
| patersonc | A new router is being installed on Monday | 15:05 |
| *** monstr has quit IRC | 16:10 | |
| *** samwilson has quit IRC | 16:58 | |
| *** samwilson has joined #cip | 16:58 | |
| *** tpollard has quit IRC | 17:39 | |
| *** samwilson has quit IRC | 19:08 | |
| *** samwilson has joined #cip | 19:48 | |
| *** toscalix has joined #cip | 19:52 | |
| *** samwilson has quit IRC | 20:29 | |
| *** samwilson has joined #cip | 20:36 | |
| *** samwilson has quit IRC | 20:41 | |
| *** samwilson has joined #cip | 20:47 | |
| *** samwilson has quit IRC | 20:52 | |
| *** samwilson has joined #cip | 21:05 | |
| *** samwilson has quit IRC | 21:13 | |
| *** pave1 has joined #cip | 21:16 | |
| *** pave1 has quit IRC | 21:30 | |
| *** Guest84521 has quit IRC | 23:05 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!