| *** pekkari <pekkari!~pekkari@user/pekkari> has joined #cip | 06:06 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 06:57 | |
| *** uli <uli!~uli@55d4e0d9.access.ecotel.net> has joined #cip | 09:48 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 10:22 | |
| *** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has joined #cip | 11:18 | |
| *** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has quit IRC (Max SendQ exceeded) | 11:18 | |
| *** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has joined #cip | 11:19 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 11:38 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 11:39 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 11:40 | |
| *** jki <jki!~jki@195.145.170.200> has joined #cip | 11:55 | |
| *** pave1 <pave1!~pavel@88-103-227-15.rci.o2.cz> has joined #cip | 11:56 | |
| pave1 | #startmeeting CIP IRC weekly meeting | 12:01 |
|---|---|---|
| collab-meetbot` | Meeting started Thu Jul 14 12:01:00 2022 UTC and is due to finish in 60 minutes. The chair is pave1. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:01 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
| pave1 | Hi! And say hi if you are around. | 12:01 |
| uli | hello | 12:01 |
| masami | hi | 12:01 |
| alicef | hi | 12:01 |
| flo2 | Hi! | 12:01 |
| pave1 | Hello, Florian. Nice to meet you! | 12:02 |
| pave1 | I'd like iwamatsu and patersonc... | 12:03 |
| alicef | oh right, maybe wait some more time ? | 12:04 |
| alicef | jki is not here today ? | 12:05 |
| alicef | hello patersonc[m] iwamatsu | 12:05 |
| pave1 | jki said he may not be able to make it. | 12:06 |
| alicef | I see. thanks for chairing today | 12:06 |
| pave1 | :-) | 12:06 |
| alicef | :D | 12:06 |
| pave1 | Let's start. | 12:06 |
| pave1 | #topic AI review | 12:06 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:06 | |
| alicef | yeah | 12:07 |
| pave1 | 1. Resolve/ignore failures of KernelCI on 4.4-cip - alicefm | 12:07 |
| alicef | I replay to your mail. I hope you have see it :) | 12:07 |
| alicef | replayed | 12:07 |
| alicef | I see flo2 replay | 12:07 |
| pave1 | Yes. I also seen flo2 starting to work on that. | 12:07 |
| flo2 | jki asked me to have a look. | 12:08 |
| alicef | yes, unfortunatly kernelci is just keeping 28days of logs | 12:08 |
| alicef | and that is 4TB | 12:08 |
| flo2 | No active working yet, but starting to get in touch with kernelci and the build/test configuration | 12:08 |
| pave1 | alicef: Yes, that's one of the problems. I wonder if having logs per-project would make sense? I don't believe we produce that much of logs. | 12:09 |
| pave1 | flo2: Thank you. | 12:09 |
| alicef | pave1: we can make some change in the cleaning logs script specifically for CIP | 12:10 |
| pave1 | flo2: For the record, lot of kernelci messages can be found in cip-dev mailing list logs. | 12:10 |
| *** pekkari <pekkari!~pekkari@user/pekkari> has quit IRC (Quit: Konversation terminated!) | 12:11 | |
| alicef | pave1: how much time would make sense? | 12:11 |
| flo2 | Could someone ACK that it should be possible to trigger cip builds (on staging) by pushing to the kernelci repository by opening a merge request? | 12:11 |
| alicef | flo2: merge request to what kernelci repository? | 12:12 |
| pave1 | alicef: We'd need like 3 months, I'm afraid. We are moving quite slowly. | 12:12 |
| alicef | kernelci-core ? | 12:12 |
| flo2 | Yes, I think it was kernelci-core... | 12:12 |
| alicef | flo2: yes that's correct | 12:12 |
| pave1 | flo2: I think I can trigger build by doing push to test tree. Also -st-rc is currently ahead of -st, I guess I can use that to trigger build. | 12:13 |
| pave1 | flo2: Should I/ | 12:13 |
| pave1 | ? | 12:13 |
| alicef | pave1: As I wrote in the mail, yes you can trigger rebuild on your test tree. | 12:13 |
| alicef | pave1: I will look about giving 3 months of logs | 12:14 |
| flo2 | At least one recent build (that is expected to fail) would help to check which tests we should exclude for now | 12:14 |
| alicef | to cip builds on linux.kernelci.org | 12:15 |
| alicef | flo2: I have triggered the test, it takes sometime for the results as I triggered it on every laboratory | 12:16 |
| pave1 | flo2: I have updated 4.4.y-cip. That should do the trick. | 12:17 |
| pave1 | 3 | 12:17 |
| flo2 | Thanks! | 12:17 |
| alicef | pave1: could you open a issue on kernelci-core about the logs or I should do by myself? both is not problem | 12:17 |
| alicef | just for keeping track of it | 12:17 |
| pave1 | alicef: Please do. | 12:17 |
| alicef | ok | 12:18 |
| pave1 | Thank you! | 12:18 |
| pave1 | 3 | 12:18 |
| pave1 | 2 | 12:18 |
| pave1 | 1 | 12:18 |
| alicef | pave1: anything other about this? | 12:18 |
| pave1 | I guess flo2 is looking into that, so I'm happy :-). | 12:18 |
| alicef | flo2: here is last cip 4.4 build https://staging.kernelci.org/job/cip/branch/linux-4.4.y-cip/ | 12:18 |
| alicef | builded now | 12:18 |
| pave1 | 2. Check cip devices on kernelci old pull request - patersonc | 12:19 |
| pave1 | Patrsonc is not around here. Skip? | 12:19 |
| alicef | patersonc[m] | 12:19 |
| alicef | I think patersonc is not pinging patersonc[m] | 12:19 |
| alicef | usually tab should autocomplete the name | 12:20 |
| alicef | but depend from your client | 12:20 |
| alicef | :) | 12:21 |
| pave1 | I'm not sure how pinging is supposed to work, but it seems he is not here. I don't think my client supports that. | 12:21 |
| pave1 | 3. Update https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware - iwamatsu-san | 12:21 |
| pave1 | iwamatsu does not seem to be here, either. | 12:22 |
| pave1 | Anything else? | 12:22 |
| alicef | not from me. | 12:22 |
| pave1 | 3 | 12:22 |
| pave1 | 2 | 12:23 |
| pave1 | 1 | 12:23 |
| alicef | I think we are only in 3 today | 12:23 |
| alicef | 5 sorry | 12:23 |
| pave1 | #topic Kernel maintenance updates | 12:23 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:23 | |
| pave1 | 5 is the right number. | 12:23 |
| alicef | we already discussed on the AI of 4.4 | 12:24 |
| pave1 | I'm reviewing 5.10.130/131 and did some work moving 4.4 forward. | 12:24 |
| alicef | I discussed with kernelci about your issues | 12:24 |
| uli | reviewed 4.4 backports, now reviewing 5.10.131 | 12:24 |
| masami | There was 8 new CVEs and 8 updated CVEs. | 12:24 |
| masami | Luckly, Retbleed's CVSS score isn't high. | 12:24 |
| pave1 | masami: retbleed is currently being reviewed as part of 5.10.131 ... AFAICT. There's also something called straight-line-speculation, mixed in to make it more fun. | 12:26 |
| pave1 | uli: Thanks! | 12:26 |
| uli | np | 12:27 |
| masami | pavel: such bugs are so bad :( | 12:27 |
| pave1 | I'll be on holidays, likely w/o internet next week. | 12:27 |
| pave1 | masami: Yes. Basically advantage of x86 is that it is backward compatible. Except that it is not compatible if you care about security. | 12:29 |
| pave1 | masami: People should really avoid out-of-order CPUs when security is needed. | 12:29 |
| masami | pavel: that's true. | 12:30 |
| alicef | is also really expensive to mitigate retbleed | 12:30 |
| alicef | in term of overhead | 12:31 |
| alicef | between 14% and 39% overhead | 12:31 |
| pave1 | Hmm. 14%..39% :-(. Fortunately kernel is usually smart part of total workload. | 12:31 |
| pave1 | Otoh this probably affects more than kernel. Fun. | 12:32 |
| alicef | it also involve changes to 68 files ... | 12:32 |
| pave1 | At some point we'll boot qemu on bare metal, just to emulate bug-free CPU :-). | 12:32 |
| alicef | that's a big backporting | 12:32 |
| pave1 | And backporting may be easy compared to testing a) it still works and b) it really fixes the problem. | 12:33 |
| pave1 | Anything else here? | 12:34 |
| pave1 | 3 | 12:34 |
| pave1 | 2 | 12:34 |
| pave1 | 1 | 12:34 |
| pave1 | #topic Kernel testing | 12:35 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:35 | |
| pave1 | alicef> we already discussed on the AI of 4.4 | 12:35 |
| pave1 | alicef> I discussed with kernelci about your issues | 12:35 |
| pave1 | Thank you! | 12:35 |
| pave1 | Anything else? | 12:35 |
| alicef | yes sorry I miss read maintainenance with testing | 12:35 |
| alicef | and started to write | 12:35 |
| pave1 | Yes, it took me few seconds but I figured it out :-). | 12:35 |
| pave1 | 3 | 12:35 |
| uli | i only figured that out now :) | 12:35 |
| pave1 | 2 | 12:36 |
| pave1 | 1 | 12:36 |
| alicef | I disscussed your issues with kernelci and will figure it out | 12:36 |
| pave1 | Thank you. I'm still not sure our testing needs are good fit for kernelci, but as long as gitlab testing works, additional testing should not hurt. | 12:37 |
| pave1 | 3 | 12:38 |
| pave1 | 2 | 12:38 |
| pave1 | 1 | 12:38 |
| pave1 | #topic AOB | 12:38 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:38 | |
| alicef | why you think we are not good fit for kernelci? | 12:38 |
| pave1 | With 4.4 backports, I basically apply a patch and need to see if it builds etc. | 12:39 |
| pave1 | (For automatically-applied patches, I simply apply whole batch, but for manual backports, I see enough errors that batching does not make sense). | 12:40 |
| pave1 | So it is ... say 15 minutes backporting, submit for a test, fix it up for next one, submit for a test. | 12:40 |
| pave1 | That's quite a high load and I need the results quite fast. | 12:40 |
| alicef | currently KernelCI is building CIP for many boards and configurations, that could be blocklisted. | 12:42 |
| alicef | Also KernelCI is currently working on many changes for new KernelCI tools. | 12:43 |
| alicef | and creating a new version of KernelCI | 12:45 |
| alicef | I understand that gitlab is more fast currently but is also testing in few boards | 12:45 |
| alicef | fewer | 12:46 |
| pave1 | I guess we should let flo2 do the work, then we can time how long it takes kernelCI to do the tests and if it is suitable replacement for gitlab testing. | 12:46 |
| pave1 | Yes, gitlab runs on fewer boards, and also (AFAIK) we pay for builders so it is okay if we use it a lot. | 12:47 |
| alicef | your developer branch for kernelci is too slow? | 12:47 |
| pave1 | I have not really timed it yet, but I assume it will not be 15 minutes? | 12:48 |
| alicef | maybe we can make many blocks on your developer branch and enable only few boards for having results faster | 12:48 |
| alicef | if that is better for you | 12:48 |
| pave1 | That may make sense if we want to replace gitlab at some point. | 12:48 |
| alicef | I doubt that paying gitlab give you the same bords that KernelCI is using for building (I could be wrong) | 12:49 |
| pave1 | I don't really know. I guess we can discuss after flo2 makes the results useful. | 12:50 |
| alicef | pave1: sure | 12:50 |
| pave1 | Anything else? | 12:51 |
| pave1 | 5 | 12:51 |
| pave1 | 4 | 12:51 |
| pave1 | 3 | 12:52 |
| pave1 | 2 | 12:52 |
| pave1 | 1 | 12:52 |
| pave1 | #endmeeting | 12:52 |
| collab-meetbot` | Meeting ended Thu Jul 14 12:52:12 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:52 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-14-12.01.html | 12:52 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-14-12.01.txt | 12:52 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/07/cip.2022-07-14-12.01.log.html | 12:52 |
| *** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"" | 12:52 | |
| pave1 | Thank you all! | 12:52 |
| alicef | thanks you pave1 | 12:52 |
| masami | thank you | 12:52 |
| uli | thanks | 12:52 |
| alicef | I suppose we need to update smc for retbleed on kernelci | 12:54 |
| alicef | not sure what version gitlab is using | 12:54 |
| alicef | on KernelCI you can get also much more detailed results | 12:55 |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 12:59 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 12:59 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 12:59 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 12:59 | |
| *** flo2 <flo2!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 13:01 | |
| pave1 | I got the results hour after submission. That's better than I expected... | 13:09 |
| pave1 | Anyway, bye for now! | 13:09 |
| *** pave1 <pave1!~pavel@88-103-227-15.rci.o2.cz> has quit IRC (Quit: Leaving) | 13:09 | |
| *** jki <jki!~jki@195.145.170.200> has quit IRC (Quit: Leaving) | 13:10 | |
| alicef | !note | 13:30 |
| alicef | !help note | 13:30 |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo) | 13:48 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 13:49 | |
| *** ChanServ sets mode: +o alicef | 13:49 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Client Quit) | 13:51 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 13:52 | |
| *** ChanServ sets mode: +o alicef | 13:52 | |
| *** uli <uli!~uli@55d4e0d9.access.ecotel.net> has left #cip (Leaving) | 13:55 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has quit IRC (Quit: install gentoo) | 13:57 | |
| *** alicef <alicef!~none@gentoo/developer/alicef> has joined #cip | 13:58 | |
| *** ChanServ sets mode: +o alicef | 13:58 | |
| *** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 14:01 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 14:11 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip | 14:32 | |
| *** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip | 16:05 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!