| *** kazu has joined #cip | 01:29 | |
| *** kazu has quit IRC | 02:04 | |
| *** rajm has joined #cip | 07:01 | |
| *** kazu has joined #cip | 08:02 | |
| *** therisen has joined #cip | 08:13 | |
| *** masashi910 has joined #cip | 08:27 | |
| *** suzuki15 has joined #cip | 08:57 | |
| *** pave1 has joined #cip | 08:58 | |
| masashi910 | #startmeeting CIP IRC weekly meeting | 09:00 |
|---|---|---|
| brlogger | Meeting started Thu Feb 20 09:00:00 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 | |
| masashi910 | please say hi if you're around | 09:00 |
| kazu | hi | 09:00 |
| punit | hi | 09:00 |
| patersonc | hi | 09:00 |
| suzuki15 | hi | 09:00 |
| pave1 | hi | 09:00 |
| *** bwh has joined #cip | 09:00 | |
| bwh | hi | 09:00 |
| masashi910 | #topic AI review | 09:00 |
| *** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 09:00 | |
| masashi910 | 1. Combine rootfilesystem with kselftest binary - Iwamatsu-san | 09:00 |
| masashi910 | Iwamatsu-san, are you around? | 09:01 |
| *** fujita3 has joined #cip | 09:01 | |
| masashi910 | Let me come back later. | 09:01 |
| masashi910 | 2. Document a process on how to add tests to the CIP test setup - patersonc | 09:01 |
| patersonc | No updates.... I do have a ticket for this btw. Up to you if you keep the action or not. | 09:01 |
| masashi910 | patersonc: You mean, you have contents to write down, and to go or not should be decided? | 09:03 |
| iwamatsu | hi | 09:03 |
| wens | hi | 09:03 |
| patersonc | I mean that I have this task planned. It may not be that important to keep an action live in this meeting. | 09:04 |
| iwamatsu | AI-1 : No update | 09:04 |
| *** yoshidak[m] has joined #cip | 09:05 | |
| masashi910 | patersonc: I understood. Thanks. Then let me close this AI. If issues are identified, let's re-open. | 09:05 |
| masashi910 | iwamatsu: Noted. Thanks | 09:05 |
| masashi910 | #topic kernel maintenance updates | 09:06 |
| *** brlogger changes topic to "kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 09:06 | |
| wens | did a round of updates for classify-failed-patches and cip-kernel-sec: CVE-2020-8992 (ext4 related soft-lockup) fixed in 5.6-rc; nothing else stands out | 09:06 |
| masashi910 | wens: Thanks! | 09:07 |
| pave1 | I have reviewed 4.19.104 / 4.19.105, and am working on "Renesas RZ/G2E USB Type-C Backport" series. | 09:07 |
| wens | classify-failed-patches will now filter per-branch (tagged with specific version number) patches | 09:07 |
| patersonc | Thank you pave1 | 09:07 |
| bwh | I've reviewed MRs for kernel repositories, and prepared an update to the source lists in kernel-config | 09:07 |
| masashi910 | pave1, bwh: Thanks! | 09:07 |
| pave1 | Plus I have backport of "mac80211: Fix TKIP replay protection immediately...". That was reasonably easy but what to do with it now? | 09:08 |
| masashi910 | iwamatsu: Do you have updates? | 09:08 |
| iwamatsu | I reviewed 4.4.214 without "f6e5b0409e18 KVM: VMX: Add non-canonical check on writes to RTIT address MSRs" | 09:08 |
| iwamatsu | commit f6e5b0409e18 is too big. | 09:09 |
| bwh | pave1: Send it to stable@? | 09:09 |
| pave1 | bwh: I guess so. I don't think anybody here can test it before I do so? | 09:09 |
| iwamatsu | pave1: I suggested sending it by RFC. | 09:10 |
| bwh | iwamatsu: Oh, that commit is broken. It is adding a source file that won't be used. It should be reverted. | 09:10 |
| masashi910 | iwamatsu, bwh: So, commit f6e5b0409e18 should be reverted? | 09:12 |
| bwh | masashi910: yes | 09:12 |
| masashi910 | bwh: Thanks for your advice! | 09:13 |
| iwamatsu | bwh: I see. Thanks for your comment! Is this already pointed out by stable@? I haven't seen all the ML yet. | 09:13 |
| bwh | iwamatsu: I don't have time to follow stable but I can check | 09:13 |
| masashi910 | iwamatsu, all: Thanks for all your works! | 09:14 |
| masashi910 | Any other topics? | 09:14 |
| pave1 | Yes, actually. | 09:15 |
| masashi910 | 3 | 09:15 |
| masashi910 | pave1: Do you have something to discuss? | 09:15 |
| pave1 | First, are there more commits I should look at backporting? | 09:15 |
| iwamatsu | bwh: thanks, so if the reverting patch has not been posted yet, I will do this. | 09:16 |
| wens | pave1: I haven't noticed anything really critical | 09:16 |
| pave1 | Second, there's realtime meeting today, but I don't think I can make it. iwamatsu: can you make it? | 09:16 |
| pave1 | wens: Thanks. | 09:16 |
| wens | pave1: that ext4 soft-lockup fix is really new, and according to the report, it only hits crafted or really large volumes | 09:16 |
| wens | pave1: plus the fix is just a one-liner reschedule call | 09:17 |
| bwh | iwamatsu: I just mailed to say this is wrong (on all 4.4-4.19 branches) | 09:17 |
| pave1 | wens: Ok, that does not look too critical. | 09:18 |
| iwamatsu | pave1: I will join RT meeting. | 09:18 |
| pave1 | iwamatsu: Thanks a lot! | 09:18 |
| iwamatsu | pave1: you are welcome. | 09:18 |
| iwamatsu | bwh: thanks! | 09:19 |
| masashi910 | Thanks, all! | 09:19 |
| pave1 | Third, we are currently discussing differences between 4.4-cip and 4.4-cip-rebase privately. | 09:19 |
| pave1 | I believe we should do it on the mailing list (or here?) | 09:19 |
| wens | mailing list is probably better? unless you're looking for quick feedback | 09:20 |
| masashi910 | pave1: I suggest that the discussion had better be done after IRC or on ML. | 09:20 |
| pave1 | Ok :-). | 09:20 |
| masashi910 | pave1: Thanks! | 09:21 |
| masashi910 | Any other topics? | 09:21 |
| masashi910 | 3 | 09:21 |
| masashi910 | 2 | 09:21 |
| masashi910 | 1 | 09:21 |
| masashi910 | #topic Kernel testing | 09:21 |
| *** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 09:21 | |
| masashi910 | patersonc: the floor is yours | 09:21 |
| patersonc | Thanks | 09:21 |
| patersonc | I'm still only working part time at the moment so not much has been done from my end (sorry!) | 09:22 |
| patersonc | CI testing of the stable-rc and CIP branches continues | 09:22 |
| patersonc | We keep seeing very slow download times at the Mentor LAVA lab which can cause jobs to fail (e.g. "5MB downloaded in 230.17s (0.02MB/s)") | 09:22 |
| patersonc | I plan to move the AWS storage to Europe, but this may only slightly improve the download speeds | 09:22 |
| patersonc | The x86 board has been offline for a few days, I've just got it working again, so the backlog of 20 or so tests should start clearing now although I expect a lot of them to timeout. | 09:22 |
| patersonc | e.g. https://lava.ciplatform.org/scheduler/job/11285 has already been going 10 minutes and it's still downloading the rfs | 09:23 |
| patersonc | Any queries from anyone? | 09:23 |
| masashi910 | patersonc: Not from me. Thanks for your works! | 09:24 |
| masashi910 | Does anybody have any queries? | 09:24 |
| masashi910 | 3 | 09:24 |
| masashi910 | 2 | 09:24 |
| masashi910 | 1 | 09:24 |
| masashi910 | #topic CIP Core | 09:24 |
| *** brlogger changes topic to "CIP Core (Meeting topic: CIP IRC weekly meeting)" | 09:24 | |
| masashi910 | kazu: the floor is yours | 09:25 |
| kazu | hello | 09:25 |
| kazu | 1. Package proposal #2: Getting TSC's approval (voting) => No reply yet?? | 09:25 |
| kazu | 2. Package proposal #1: Based on today's discussion with security WG, we decided to change the approach to confirm these security packages | 09:25 |
| kazu | I will announce this to cip-members later | 09:25 |
| kazu | 3. GitLab CI: Adding test submission to LAVA master https://gitlab.com/cip-project/cip-core/deby/issues/7 | 09:25 |
| kazu | I'm Still facing permission issues | 09:25 |
| kazu | please tell me if you find something wrong in S3/LAVA settings... | 09:26 |
| kazu | 4. Quirin reported that some kernel configs are missing for some targets to boot Debian 10 (Generic profile) | 09:26 |
| kazu | https://lists.cip-project.org/pipermail/cip-dev/2020-February/004403.html | 09:26 |
| kazu | Examples: https://gitlab.com/Quirin.Gy/cip-kernel-config/-/commit/92979dba2e3c03a422b5b9e8f9c592db9ff43f30 | 09:26 |
| kazu | I guess CIP kernels are tested with the original configs (without the additional configs above) and no issue, so CIP Core should not change them and create separated configs and cat them? | 09:26 |
| kazu | That's all from me, any comments? | 09:27 |
| patersonc | kazu: Yes, I'm currently testing the Kernel with the exact configs from cip-kernel-config | 09:27 |
| patersonc | kazu: I'll take a look at https://gitlab.com/cip-project/cip-core/deby/issues/7 now | 09:28 |
| kazu | patersonc Thank you for the information, we will decide how we solve this based on this fact | 09:28 |
| masashi910 | kazu, patersonc: Thanks! | 09:28 |
| masashi910 | any other topics? | 09:28 |
| masashi910 | 3 | 09:28 |
| masashi910 | 2 | 09:29 |
| masashi910 | 1 | 09:29 |
| masashi910 | #topic Software update | 09:29 |
| *** brlogger changes topic to "Software update (Meeting topic: CIP IRC weekly meeting)" | 09:29 | |
| masashi910 | Suzuki-san, the floor is yours | 09:29 |
| suzuki15 | Hello | 09:29 |
| suzuki15 | Now I'm clarifying our WG's tasks. (Ref: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/1) | 09:29 |
| suzuki15 | I'll make our next iteration plan once the above task is completed. (Ref: https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/issues/2) | 09:29 |
| suzuki15 | That's all from me. | 09:29 |
| masashi910 | suzuki15: Thanks! | 09:30 |
| masashi910 | any other topics? | 09:30 |
| masashi910 | 3 | 09:30 |
| masashi910 | 2 | 09:30 |
| masashi910 | 1 | 09:30 |
| masashi910 | #topic AOB | 09:30 |
| *** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 09:30 | |
| masashi910 | 1. Cancellation of "F2F" meetings in Nuremberg | 09:30 |
| masashi910 | By looking at the current situation, all F2F meetings were cancelled. | 09:31 |
| masashi910 | 2. "F2F" Kernel Team Meeting is now Kernel Team "Call" which will be held as follows. | 09:31 |
| masashi910 | TZ:TokyoTaipeiBerlinLondonNYLA | 09:31 |
| masashi910 | ---------------------------------------------------------- | 09:31 |
| masashi910 | Start:21:0020:0013:0012:0007:0004:00 | 09:31 |
| masashi910 | End:22:0021:0014:0013:0008:00 05:00 | 09:31 |
| masashi910 | Hard to look. Sorry. | 09:31 |
| bwh | The cip-dev list is now archived at https://lore.kernel.org/cip-dev/ | 09:32 |
| kazu | CIP Core Call is under voting: https://doodle.com/poll/8xr7diiiazb7wsg2 Please join if you are interested in | 09:32 |
| masashi910 | bwh: Right. Thanks for pointing this out. | 09:32 |
| masashi910 | kazu: Thanks. | 09:33 |
| masashi910 | Are there any business matters to discuss? | 09:33 |
| masashi910 | 3 | 09:33 |
| masashi910 | 2 | 09:33 |
| masashi910 | 1 | 09:33 |
| masashi910 | #endmeeting | 09:33 |
| brlogger | Meeting ended Thu Feb 20 09:33:30 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:33 |
| brlogger | Minutes: https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-20-09.00.html | 09:33 |
| brlogger | Minutes (text): https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-20-09.00.txt | 09:33 |
| brlogger | Log: https://irclogs.baserock.org/meetings/cip/2020/02/cip.2020-02-20-09.00.log.html | 09:33 |
| *** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/" | 09:33 | |
| masashi910 | Thanks! | 09:33 |
| wens | thank you! | 09:33 |
| pave1 | Thank you! | 09:33 |
| suzuki15 | Thank you! | 09:33 |
| iwamatsu | thank you! | 09:33 |
| punit | Thank you | 09:34 |
| pave1 | iwamatsu: Is it okay to discuss 4.4 -cip vs. -rebase now? | 09:34 |
| kazu | patersonc Regarding GitLab issue, most parts of the script are based on resources in linux-cip-ci, and using the same command to upload binaries to AWS & submitting the tests to LAVA. I'm not sure if any differences in GitLab or Docker image side. | 09:34 |
| *** suzuki15 has quit IRC | 09:34 | |
| patersonc | kazu: Okay | 09:36 |
| wens | patersonc: regarding download speeds, what are the physical locations of the labs and the storage? | 09:37 |
| patersonc | wens: Current storage is west usa. Lab location is india... | 09:38 |
| wens | I guess that explains the bad performance | 09:39 |
| pave1 | wens, patersonc: 50KB/sec... is quite low even for "going around the world" setup. | 09:39 |
| patersonc | Indeed | 09:40 |
| wens | it really depends on the ISP | 09:40 |
| wens | where I work (in Taipei), downloads from our datacenter (US west) only does 15x KB/s sustained sometimes | 09:41 |
| pave1 | Would it be possible to determine where the bottleneck is? It may be that link to the lab is having problems or something like that. | 09:41 |
| pave1 | wens: Aha... I have not seen that kind of speeds for a long time :-(. I'm normally limited by local DSL line... or even by local wifi. | 09:42 |
| wens | you could try to approximate it with `mtr`, using both ICMP and TCP modes, and doing it in both directions | 09:42 |
| wens | I looked into a lot of last-mile ISPs in various south-east Asian countries a few months ago | 09:43 |
| wens | India was particularly bad in some cases. | 09:43 |
| pave1 | other option might be wget some reasonably large file (5MB?) from US/EU/India/... servers... | 09:43 |
| wens | One possible reason is that it's almost equal distance to the US, either going east or west | 09:44 |
| wens | that and some funky peering/transit agreements between ISPs give you 300+ ms RTTs | 09:44 |
| pave1 | But if ISPs are really that bad there, the only option is going to be a mirror with big files close to the lab... | 09:45 |
| wens | AWS has nodes in Mumbai, or slightly further, Singapore, which you could try? | 09:46 |
| wens | official and non-official AWS speed tests are all browser (javascript) based though | 09:49 |
| patersonc | Ideally we'd use one S3 bucket for all the CI testing, as in theory multiple labs can have the same boards so we won't know before hand where the tests will physically be run. | 09:53 |
| patersonc | We did some rough testing with a German based bucket a while ago and it seemed better, sometimes doubling the speed if I remember correctly | 09:53 |
| patersonc | The reason I went for Germany is that we have a lab in the UK, India and soon another lab in Germany | 09:54 |
| wens | that makes sense | 09:55 |
| pave1 | bye! | 10:20 |
| *** pave1 has quit IRC | 10:20 | |
| *** kazu has quit IRC | 10:29 | |
| patersonc | iwamatsu: I've seen your PR on linux-cip-ci. Thanks. Please check my replies. | 10:30 |
| *** fujita3 has quit IRC | 10:49 | |
| *** brlogger has joined #cip | 11:00 | |
| *** laurence- has quit IRC | 11:04 | |
| *** Guest47977 has quit IRC | 11:04 | |
| *** jward has joined #cip | 11:11 | |
| *** jward is now known as Guest47411 | 11:11 | |
| *** laurence- has joined #cip | 11:11 | |
| *** laurence- has quit IRC | 11:30 | |
| *** Guest47411 has quit IRC | 11:30 | |
| *** jward has joined #cip | 11:30 | |
| *** jward is now known as Guest66541 | 11:31 | |
| *** laurence- has joined #cip | 11:36 | |
| *** therisen has quit IRC | 11:55 | |
| *** therisen has joined #cip | 11:59 | |
| *** CTtpollard has joined #cip | 13:07 | |
| *** tpollard has quit IRC | 13:11 | |
| *** CTtpollard has quit IRC | 14:10 | |
| *** tpollard has joined #cip | 14:11 | |
| *** masashi910 has quit IRC | 15:00 | |
| *** masashi910 has joined #cip | 15:02 | |
| *** masashi910 has quit IRC | 15:06 | |
| *** alicef has quit IRC | 15:30 | |
| *** alicef has joined #cip | 15:34 | |
| *** alicef has quit IRC | 15:42 | |
| *** alicef has joined #cip | 15:45 | |
| *** therisen has quit IRC | 16:15 | |
| *** rajm has quit IRC | 17:16 | |
| *** rajm has joined #cip | 19:06 | |
| *** masashi910 has joined #cip | 22:35 | |
| *** rajm has quit IRC | 22:57 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!