Hi Sebastian, ---- On Tue, 11 Feb 2025 12:20:18 -0300 Sebastian Andrzej Siewior wrote --- > On 2025-02-11 08:33:56 [-0300], Gustavo Padovan wrote: > > Hi Sebastian, > Hi Gustavo, > > > Thank you for your email. We are happy that KernelCI is helping you with tests. > ;) > > > Since PREEMPT_RT is now available upstream, would it work to compile and > > > enable some of its tests for the supported architectures on Linus' tree > > > and maybe the -next tree? I don't think that happens at the moment, I > > > saw only a few stable-rt trees. > > > > https://github.com/kernelci/kernelci-pipeline/pull/1010 > > > > This will get it enabled for mainline and next. Allow us a few days for processing and > > deploying this in production. > > Sure. Just poke if you have something to inspect or look at because of > $reason. > > The architectures, that support RT are what you see in > | git grep ARCH_SUPPORTS_RT arch/ > > so this does not include arm at current stage for instance. So in > general, if you can't select CONFIG_PREEMPT_RT you can skip the > config/ build/ test. > > RiscV on the other hand is supported. Right. Let me look at how we can limit this to x86 only. Unfortunatelly, we don't have much RISC-V hw support in KernelCI yet. > > > Beyond that, we would love any feedback you have to us. A lot of the infra > > we have today is new, so there are still rough edges to work on. > > Sure. How do I see easily what is tested/ done? I could maybe wait a few > days and check the dashboard. The link from above showed timerlat has > been but I didn't manage to figure what has been. I guess there is a > script somewhere handling the logic. That is one the current limitations in the dashboard. The CI systems are not sending a clear signal yet that they completed all tests they wanted to run. They just submit test result individually as they get finished. Imo, it is a priority to fix this as it is second time this week I get this feedback. Best, - Gus
