| *** pekkari <pekkari!~pekkari@user/pekkari> has joined #cip | 04:19 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip | 06:34 | |
| *** toscalix <toscalix!~toscalix@84.78.241.83> has joined #cip | 07:01 | |
| *** toscalix <toscalix!~toscalix@84.78.241.83> has quit IRC (Quit: Konversation terminated!) | 07:16 | |
| *** uli <uli!~uli@55d4ece6.access.ecotel.net> has joined #cip | 11:22 | |
| *** masami <masami!~masami@FL1-220-144-160-220.tky.mesh.ad.jp> has joined #cip | 11:41 | |
| *** jki <jki!~jki@165.225.26.238> has joined #cip | 11:48 | |
| jki | #startmeeting CIP IRC weekly meeting | 12:01 |
|---|---|---|
| collab-meetbot` | Meeting started Thu Jun 23 12:01:11 2022 UTC and is due to finish in 60 minutes. The chair is jki. 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 | |
| jki | Hi all! | 12:01 |
| patersonc[m] | Hello | 12:01 |
| uli | hello | 12:01 |
| masami | hi | 12:01 |
| alicef | hi | 12:02 |
| pave1 | hi | 12:02 |
| jki | got distracted - let's start | 12:08 |
| jki | #topic AI review | 12:08 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:08 | |
| jki | 1. Resolve/filter irrelevant failures of KernelCI for 4.4-cip - patersonc & alicefm | 12:08 |
| patersonc[m] | Nope | 12:08 |
| alicef | there is a issue open or a pull request about this? | 12:08 |
| alicef | ah found | 12:08 |
| jki | 2. Check cip devices on kernelci old pull request - patersonc | 12:10 |
| patersonc[m] | I'm looking into that now | 12:10 |
| patersonc[m] | Nothing to report yet though | 12:10 |
| alicef | jki: why are you asking to drop 4.4.cip checks ? looks like the problem is only on few boards | 12:11 |
| alicef | I cannot see the kernelci log as too much time passed by the way | 12:11 |
| alicef | looks like is failing only on mips boards | 12:12 |
| jki | alicef: we discussed long ago that the current 4.4-cip kernelci results contain too much noise for our scope | 12:12 |
| jki | pavel remarked this e.g. | 12:12 |
| alicef | too much noise ? the last time it run was last month | 12:13 |
| jki | therefore the idea was born to look into make the report more focused | 12:13 |
| alicef | 2022-05-18 | 12:13 |
| jki | pavel: can you comment on that? | 12:13 |
| alicef | also the link you are linking on the bug issue is about stable-rc and not cip | 12:14 |
| alicef | See https://linux.kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.302/ | 12:14 |
| alicef | this is stable-rc not cip | 12:14 |
| alicef | I think the solution is solving the issues not suppress the tests | 12:15 |
| jki | the primary goal is to have reports that quickly point our new regressions | 12:15 |
| pave1 | alicef: if someone is able to say which issues are real | 12:16 |
| jki | the secondary would be finding and resolving potential existing ones | 12:16 |
| pave1 | alicef: we should solve them. | 12:16 |
| pave1 | alicef: take a look, tell me what to solve and I ll solve it. | 12:17 |
| *** pekkari <pekkari!~pekkari@user/pekkari> has quit IRC (Quit: Konversation terminated!) | 12:17 | |
| alicef | we should make a kanboard like the kernelci is doing https://github.com/orgs/kernelci/projects/6 | 12:17 |
| alicef | for each issue | 12:17 |
| alicef | pave1: that's not the a good way of solving issues | 12:18 |
| jki | well, we likely have no time spend on mips | 12:18 |
| pave1 | alicef: so suggest something else. Last time I looked, most issues seemed "not real" | 12:19 |
| alicef | "not real" means on machine not related to cip i suppose | 12:19 |
| pave1 | Not real meaning it was not kernel that was failing. | 12:20 |
| alicef | so it was a kernelci problem ? is it fixed yet? | 12:21 |
| jki | it seems the first to-do remains to start looking into the issue, so a board can be step forward | 12:22 |
| jki | but that alone will not change the picture | 12:22 |
| pave1 | It is long tine since I investigated. | 12:22 |
| alicef | jki: the issue is too much ambiguos for expecting us to do something | 12:22 |
| alicef | if you can pinpoint what is broken is better | 12:23 |
| pave1 | Go through reports, point me at kernel problem. | 12:23 |
| alicef | pave1: that's not just reading kernelci reports? | 12:23 |
| pave1 | I could not find single one so I gave up. | 12:24 |
| jki | ...and that's where the "filtering" idea came from | 12:25 |
| jki | maybe not the best but a pragmatic reaction | 12:25 |
| jki | anyway, someone needs to drive this who is familiar with the setup, I'm afraid | 12:25 |
| jki | that's why the AI landed on your table | 12:26 |
| jki | better concrete suggestions always welcome! | 12:27 |
| alicef | I'm still not sure of what you want kernelci to do | 12:27 |
| patersonc[m] | Only run CIP configs and arches on CIP kernel builds? | 12:28 |
| alicef | if you a concrete solution is more than welcome | 12:28 |
| patersonc[m] | So in effect reduce build and testing coverage? | 12:28 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 12:29 | |
| jki | pavel is your main "user" here, he should define the final result | 12:29 |
| pave1 | I dont think it is too much coverage problem. | 12:29 |
| jki | I'm happy to moderate and help defining what needs to be done between kernelci and that result | 12:30 |
| pave1 | Begining would be "show me single report I should work on". | 12:30 |
| alicef | that's not how kernelci work | 12:31 |
| pave1 | I see. | 12:31 |
| pave1 | If you cant show me single good report, how do you expect me to find one? | 12:32 |
| alicef | you expect to get a summary for all cip kernels with only bugs you are interested on? | 12:33 |
| patersonc[m] | https://linux.kernelci.org/job/cip/ | 12:33 |
| alicef | based on what decisions? | 12:33 |
| pave1 | I expect to be able to find single good report in all the noise. | 12:34 |
| pave1 | Based on any reasonable decisions. | 12:34 |
| alicef | my proposal would be that you start a issues board and write down issues that you are not iterested and one that you are interested | 12:34 |
| alicef | instead of tagging everything as noise | 12:34 |
| pave1 | Give me one good report to start with. | 12:36 |
| pave1 | If it is not noise, it should not be hard. | 12:36 |
| alicef | good is not a objective definition of something | 12:36 |
| jki | maybe start with one concrete error of that report? | 12:38 |
| alicef | I have no idea of your definition of good | 12:38 |
| jki | https://linux.kernelci.org/build/id/61fbabe0cb6f27a6ce5d6f03/logs/? | 12:39 |
| alicef | and you are getting mail for each report that came from kernelci about cip | 12:39 |
| alicef | you should start make a filter list and me and patersonc[m] could help filtering out upstream | 12:39 |
| alicef | also usually kernelci accept only working kernels | 12:40 |
| alicef | so if you get errors is usually a regression | 12:40 |
| alicef | maybe not relevant for cip but still a regression | 12:41 |
| alicef | for exemple mips error from what I can see as I cannot see the logs. there was no error on the previous kernel cip 4.4 build | 12:42 |
| *** toscalix <toscalix!~toscalix@185.124.31.238> has joined #cip | 12:42 | |
| pave1 | that is not what I remembered. I can look at jki's link. | 12:43 |
| alicef | if is a board failure, it happen. is nothing that we can do about | 12:43 |
| alicef | I cannot prevent a board failure before it fail | 12:43 |
| pave1 | What you can do is pointing me issues you believe should be fixed. | 12:44 |
| pave1 | Then I can look for similar issues. | 12:44 |
| jki | pavel: ideally, you should once be able to see them as well, I think | 12:44 |
| jki | but it seems we are playing ping-pong here | 12:45 |
| jki | who needs to do a first step | 12:45 |
| alicef | pave1: I have no idea what issues you want to fix | 12:45 |
| jki | pavel, alicef: please list one issue each about which you think it should be filtered or fixed | 12:46 |
| jki | then let us discuss about these two issues next time | 12:46 |
| jki | want do you think? | 12:46 |
| pave1 | Ok, lets do that over email? | 12:46 |
| jki | also fine for me | 12:46 |
| alicef | we already have the kernelci issue that is frozen | 12:47 |
| alicef | i'm still not sure what you expect me to do | 12:47 |
| alicef | https://github.com/kernelci/kernelci-core/issues/1053#issuecomment-1050679725 also gtucker replayed to your request | 12:48 |
| jki | ok, so someone needs to come up with a reasonable blocklist for 4.4 first | 12:50 |
| jki | for that, pavel could start with a proposal of one (or more) entries? | 12:51 |
| jki | alicef: would that help you then? | 12:51 |
| pave1 | Ok, let me take a look. | 12:51 |
| jki | thanks a lot in advance | 12:52 |
| jki | move on? | 12:52 |
| alicef | yes | 12:52 |
| jki | 3. Update https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware - iwamatsu-san | 12:53 |
| jki | any news on the qemu entries? | 12:53 |
| jki | ah, iwamatsu is not participating :) | 12:55 |
| jki | then move on | 12:55 |
| jki | #topic Kernel maintenance updates | 12:55 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:55 | |
| uli | done with reviewing 5.10.121 | 12:55 |
| pave1 | Reviews -- 5.10.123 and 124. | 12:55 |
| masami | This week reported 6 new CVEs and 4 updated CVEs. | 12:55 |
| masami | Most of new CVEs were fixed in mainline and stable kernels. | 12:56 |
| pave1 | Applied Uli's backports after some tweaking. May still break bisectability. | 12:58 |
| pave1 | I would not mind someone looking at 4.4-cip to double-check. | 12:59 |
| jki | uli? or better even a third person? | 13:00 |
| pave1 | Whatever review I can get :-) | 13:01 |
| jki | ok, other topics here? | 13:02 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #topic Kernel testing | 13:02 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| alicef | jki: can you confirm that isar-cip-core kernelci deploy script is working again? | 13:03 |
| alicef | I remember you told that was not working | 13:03 |
| jki | hmm, honestly, I only checked if it does not fail during the execution | 13:03 |
| jki | didn't check the pushed artifacts | 13:03 |
| alicef | looks like is starting to send artifacts again | 13:04 |
| jki | good | 13:04 |
| jki | let me know if they do not look like as they should | 13:04 |
| alicef | last artifact is of 20220622 | 13:04 |
| alicef | ok | 13:05 |
| jki | anything else? | 13:06 |
| jki | 3 | 13:07 |
| jki | 2 | 13:07 |
| jki | 1 | 13:07 |
| patersonc[m] | Iwamatsu-san got the kernel config we needed for nfs on the openblocks board, and we've tested that it works in LAVA. I've fixed the healthcheck and one of the boards is online now. When Minda-san creates an MR on cip-kernel-config we'll be able to start including testing of the openblocks board in our CI. | 13:07 |
| alicef | nice ! | 13:07 |
| jki | cool | 13:07 |
| patersonc[m] | Nothing else from me | 13:08 |
| jki | then let's move on | 13:08 |
| jki | 3 | 13:08 |
| jki | 2 | 13:08 |
| jki | 1 | 13:08 |
| jki | #topic AOB | 13:08 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:08 | |
| patersonc[m] | I've got a Q about cip-core, if it's not completely the wrong place? | 13:10 |
| patersonc[m] | Are the package versions from cip-core-isar and deby kept in sync? | 13:10 |
| jki | I don't think so | 13:10 |
| jki | for deby, best ask kazu | 13:10 |
| patersonc[m] | Should they be? | 13:11 |
| jki | and for cip-core, we are pulling from upstream debian of the day | 13:11 |
| jki | we don't do any extra work on top of the current debian packages to justify a gating or freezing at this point | 13:11 |
| jki | but that would indeed be a better topic for the cip-core WG | 13:12 |
| jki | maybe ask your question on the list, providing more details on why things should be sync'ed? | 13:12 |
| patersonc[m] | Sure | 13:13 |
| patersonc[m] | Thanks Jan | 13:13 |
| jki | anything else? | 13:13 |
| patersonc[m] | Not from me | 13:14 |
| jki | 3 | 13:14 |
| jki | 2 | 13:14 |
| jki | 1 | 13:14 |
| jki | #endmeeting | 13:15 |
| collab-meetbot` | Meeting ended Thu Jun 23 13:15:01 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:15 |
| collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-23-12.01.html | 13:15 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-23-12.01.txt | 13:15 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/06/cip.2022-06-23-12.01.log.html | 13:15 |
| *** 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/"" | 13:15 | |
| jki | thank you all! | 13:15 |
| uli | thanks | 13:15 |
| pave1 | thank you! | 13:15 |
| masami | thank you | 13:15 |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 13:15 | |
| alicef | thank you | 13:16 |
| patersonc[m] | ttfn! | 13:16 |
| *** jki <jki!~jki@165.225.26.238> has quit IRC (Quit: Leaving) | 13:17 | |
| *** uli <uli!~uli@55d4ece6.access.ecotel.net> has left #cip (Leaving) | 13:29 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 13:40 | |
| *** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC (Remote host closed the connection) | 16:02 | |
| *** toscalix <toscalix!~toscalix@185.124.31.238> has quit IRC (Quit: Konversation terminated!) | 16:44 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 18:13 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 19:37 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 248 seconds) | 22:05 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!