| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 00:39 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 244 seconds) | 04:39 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 07:46 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 244 seconds) | 10:34 | |
| *** uli <uli!~uli@55d4215f.access.ecotel.net> has joined #cip | 11:13 | |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip | 11:40 | |
| *** jki <jki!~jki@195.145.170.166> has joined #cip | 12:00 | |
| jki | Hi all! | 12:00 |
|---|---|---|
| masami | hello | 12:00 |
| pave1 | hi! | 12:00 |
| alicef | hi | 12:01 |
| *** patersonc <patersonc!~patersonc@pc.renesas.eu> has joined #cip | 12:02 | |
| jki | let's go: | 12:03 |
| jki | #startmeeting CIP IRC weekly meeting | 12:03 |
| collab-meetbot | Meeting started Thu Oct 20 12:03:40 2022 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:03 |
| collab-meetbot | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:03 |
| collab-meetbot | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:03 |
| *** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | #topic AI review | 12:03 |
| *** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:03 | |
| jki | 1. Add qemu-riscv to cip-kernel-config - patersonc | 12:03 |
| patersonc[m] | No updates | 12:04 |
| jki | 2. Ask Florian to support with 4.4 kernel-ci reports - jki | 12:04 |
| jki | done, Florian will look into that soon | 12:05 |
| jki | he said only one issue was remaining if he was recalling correctly | 12:05 |
| jki | any other AIs? | 12:05 |
| pave1 | If 4.4 reports are useful or close to being useful... should I take another look? | 12:06 |
| jki | I asked Florian to approach you on that | 12:06 |
| jki | but you may also give feedback earlier, if you like | 12:06 |
| pave1 | Ok :-). | 12:07 |
| jki | ok, moving on in... | 12:08 |
| jki | 3 | 12:08 |
| jki | 2 | 12:08 |
| jki | 1 | 12:08 |
| jki | #topic Kernel maintenance updates | 12:08 |
| *** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:08 | |
| pave1 | I did reviews on 5.10.149 and .150. | 12:09 |
| masami | This week reported 23 new CVEs that three of them are remote code execution vulnerabilities. | 12:09 |
| masami | These vulnerabilities have been fixed in stable kernels. | 12:09 |
| pave1 | (.150 is huge, still a lot to do). | 12:09 |
| uli | i did 5.10.150 | 12:10 |
| jki | anything else for this topic? | 12:13 |
| jki | 3 | 12:15 |
| jki | 2 | 12:15 |
| jki | 1 | 12:15 |
| jki | #topic Kernel testing | 12:15 |
| *** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:15 | |
| alicef | replaying to florian issue | 12:16 |
| patersonc[m] | It appears that a lot of our RT tests aren't completing properly. The tests run, but the Python script that collates the results at the end doesn't run. | 12:16 |
| patersonc[m] | Need to investigate further. | 12:16 |
| patersonc[m] | Have you noticed this before Pavel? Do you just check the latency results and not worry about the script at the end? | 12:17 |
| pave1 | I just watch for green ticks :-). Have not noticed that before, sorry. | 12:17 |
| patersonc[m] | Does anyone check test results? Or just that the lava job ran until the end? | 12:18 |
| pave1 | patersonc: I suspect noone does. | 12:19 |
| patersonc[m] | So how are we confirming that we don't see regressions? If we don't look at the results it's just a load of boot tests | 12:20 |
| alicef | most of the issues that Florian pointed out about 4.4 looks solved upstream by the way | 12:20 |
| alicef | https://github.com/kernelci/kernelci-core/issues/1053#issuecomment-1285433617 | 12:20 |
| pave1 | Yeah, and a bunch of compile tests :-). A lot of kernel issues manifest by kernel not booting. | 12:21 |
| alicef | we have no more errors on 4.4 only some warnings | 12:22 |
| pave1 | alicef: Ok, thanks. | 12:22 |
| jki | pavel: do we need/want to resolve those as well? | 12:22 |
| alicef | pave1: sorry I couldn't find not booting kernel on the last 4.4 | 12:22 |
| pave1 | alicef: So I can just ignore the warnings, and only care if errors appear? | 12:22 |
| alicef | I'm currently looking a some strange smc regression on 4.4 qemu | 12:22 |
| pave1 | jki: Ignoring warnings should be simple enough. Getting rid of warnings would be nice, but is not high priority. | 12:23 |
| *** patersonc <patersonc!~patersonc@pc.renesas.eu> has quit IRC (Quit: Connection closed) | 12:24 | |
| alicef | pave1: I also don't know about that. Depend from the warnings and errors. I will give a shallow look if there is any warning that is interesting | 12:24 |
| pave1 | patersonc: ? | 12:25 |
| pave1 | alicef: Thanks. | 12:26 |
| alicef | pave1: actually you can just give a look at the end of this page and looks if there is something that is interesting. but I don't think there is https://linux.kernelci.org/build/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip70-98-g7f7838c92740f/ | 12:26 |
| alicef | I will look if something as been not inserted that | 12:27 |
| alicef | like I cannot find the smc regression on that list | 12:27 |
| pave1 | alicef: Ok, let me do that over the week. | 12:27 |
| alicef | they are really few warning. they are mostly like suggest parentesis and similar. thanks | 12:28 |
| patersonc[m] | Great | 12:29 |
| jki | cool! | 12:29 |
| pave1 | patersonc: Could we get three results in the gitlab-ci? | 12:29 |
| pave1 | patersonc: Green -- nothing to see, noone needs to look here. | 12:29 |
| pave1 | Red -- something is wrong in the kernel, either it failed to boot or some test failed. | 12:30 |
| pave1 | Yellow or something -- something is wrong in the labs. Power failed, docker stuff is acting funny, ... | 12:30 |
| patersonc[m] | GitLab CI doesn't support this, sorry | 12:31 |
| pave1 | Its important that we dont get green when theres some problem hidden in the logs. | 12:31 |
| alicef | pave1: following is the strange smc regression | 12:31 |
| pave1 | Ok, next best thing: can we get last line of the log saying what is it? | 12:31 |
| jki | why should gitlab not support this? | 12:32 |
| jki | Lava runs can be translated into pipeline states - if they return clear results | 12:32 |
| patersonc[m] | pave1: We could trawl the test case results and make the whole thing a red cross if there is a single error? | 12:32 |
| alicef | on v4.4.302-cip70 all cve pass https://storage.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip70/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.html | 12:33 |
| jki | or did you mean the yellow state? | 12:33 |
| alicef | on v4.4.302-cip70-98-g7f7838c92740f we have a CVE-2020-0543: fail https://storage.kernelci.org/cip/linux-4.4.y-cip/v4.4.302-cip70-98-g7f7838c92740f/x86_64/x86_64_defconfig/gcc-10/lab-collabora/smc-qemu_x86_64.html | 12:33 |
| alicef | CVE-2020-0543: VULN (Your CPU microcode may need to be updated to mitigate the vulnerability) but is same board | 12:34 |
| patersonc[m] | Let me look into it. But last time I looked it wasn't something we can control, other then pass (green tick) or fail (red cross) | 12:34 |
| pave1 | patersonc: Can we have two phases? We currently have build, test. | 12:35 |
| pave1 | Have build, tests finish, tests report passing result? | 12:35 |
| alicef | looks like same board some toolchain but different smc test results O_o | 12:36 |
| patersonc[m] | pave1: Yea we could do something like this. And then just have to look into the collated test results in the last job | 12:37 |
| pave1 | alicef: If it is spectre/meltdown checker on Qemu.. then I suggest we don't have to care much. | 12:38 |
| alicef | pave1: ok thanks. than we have only the warning I pointed you | 12:39 |
| pave1 | alicef: Ok, let me look into that and report via email. | 12:40 |
| alicef | ok | 12:40 |
| patersonc[m] | It looks like we can set some exit codes now in GitLab CI: https://docs.gitlab.com/ee/ci/yaml/#allow_failureexit_codes | 12:41 |
| jki | great to see this progress! | 12:42 |
| patersonc[m] | Although actually, that looks like it's used to determine if a job fails or passes based on return codes from scripts. It's not controlling whether we can set a yellow warning in the pipelines view. | 12:43 |
| patersonc[m] | So not so useful | 12:43 |
| jki | yeah, a yellow state is not known to me either | 12:44 |
| jki | fail or pass, that's it | 12:44 |
| patersonc[m] | Bit annoying. | 12:46 |
| jki | well, open an issue with gitlab.com ;) | 12:47 |
| patersonc[m] | We can create some scripts to parse the results better, but at some point we may as well just use KernelCI as it is better for this kind of thing | 12:47 |
| pave1 | Is it possible to not finish, or finish without returning the result? | 12:47 |
| patersonc[m] | This was the main drive for using KernelCI - much more advanced than our gitlab CI setup | 12:47 |
| patersonc[m] | pave1: Not finishing would eventually lead to a timeout, which would be a red cross | 12:48 |
| jki | if you don't finish a job, you will empty out pockets with AWS bills ;) | 12:48 |
| patersonc[m] | The only option really is to fail the whole job if a single test case didn't pass | 12:49 |
| patersonc[m] | jki: That too :D | 12:49 |
| pave1 | patersonc: That is good option. And add a line at the end of log explaining "test returned failure" so that we know it is different from "lab does not have power". | 12:50 |
| patersonc[m] | We pretty much have this already | 12:52 |
| patersonc[m] | e.g. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/3184699360 | 12:52 |
| patersonc[m] | Test case results are all there | 12:52 |
| patersonc[m] | We just don't have a overall fail if a single test case fails - only if the entire lava job failed | 12:52 |
| patersonc[m] | Example with some fails: | 12:53 |
| patersonc[m] | https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/3141003858 | 12:53 |
| patersonc[m] | But then, in the case of SMC, some of those test cases are expected to fail. | 12:54 |
| patersonc[m] | So we'd need to have a way of knowing when failures are expected... | 12:54 |
| patersonc[m] | Or whether they are regressions | 12:54 |
| pave1 | Drop SMC for now :-). | 12:55 |
| pave1 | Or blacklist SMC from qemu targets. | 12:56 |
| patersonc[m] | I'm sure that all the LTP test cases don't pass.. | 12:56 |
| patersonc[m] | e.g. https://lava.ciplatform.org/results/763461 | 12:57 |
| jki | we've reached the top of the hour - anything else on testing? | 13:01 |
| jki | 3 | 13:02 |
| jki | 2 | 13:02 |
| jki | 1 | 13:02 |
| jki | #topic AOB | 13:02 |
| *** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:02 | |
| jki | anyone anything? | 13:03 |
| jki | 3 | 13:04 |
| jki | 2 | 13:04 |
| jki | 1 | 13:04 |
| jki | #endmeeting | 13:04 |
| collab-meetbot | Meeting ended Thu Oct 20 13:04:11 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:04 |
| collab-meetbot | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-20-12.03.html | 13:04 |
| collab-meetbot | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-20-12.03.txt | 13:04 |
| collab-meetbot | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/10/cip.2022-10-20-12.03.log.html | 13:04 |
| *** 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:04 | |
| pave1 | Thank you! | 13:04 |
| uli | thanks | 13:04 |
| jki | thanks, folks! | 13:04 |
| masami | thanks | 13:04 |
| patersonc[m] | Nope | 13:04 |
| jki | enjoy the rest of today! | 13:04 |
| patersonc[m] | Cheers all | 13:04 |
| *** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:04 | |
| pave1 | Let me take a look at the test results and report over the email. | 13:04 |
| alicef | thanks you | 13:05 |
| alicef | pave1: thanks you | 13:05 |
| alicef | I'm asking about some problem on asus-C523NA-A20057-coral that affect 4.4 even few builds on kernelci | 13:05 |
| *** jki <jki!~jki@195.145.170.166> has quit IRC (Remote host closed the connection) | 13:05 | |
| alicef | looks broken for almost every kernel ... :/ | 13:06 |
| *** jki <jki!~jki@195.145.170.147> has joined #cip | 13:06 | |
| alicef | every few test that board is going in panic | 13:06 |
| pave1 | I don't know what asus-coral is. | 13:06 |
| alicef | I think is asus chromebook c523na | 13:07 |
| alicef | anyway probably we can just filter it out | 13:07 |
| pave1 | Chromebook not having good support in 4.4 or crashing randomly would not be surprising. | 13:08 |
| alicef | mmm is not only 4.4 | 13:08 |
| pave1 | Chromebooks often have vendor kernels... and are not well (or at all) supported with mainline. | 13:08 |
| pave1 | Lets do the rest over email? | 13:09 |
| alicef | I see | 13:09 |
| alicef | sure :) | 13:09 |
| pave1 | Thank you, bye! | 13:09 |
| alicef | see you | 13:09 |
| *** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving) | 13:09 | |
| *** jki <jki!~jki@195.145.170.147> has quit IRC (Remote host closed the connection) | 13:09 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 21:14 | |
| *** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 252 seconds) | 21:59 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!