search

kernelci / kernelci-project

KernelCI Linux Foundation project documentation
9 stars 25 forks source link

Fully enable Baylibre's lab in the new infra #350

Open padovan opened 2 months ago

padovan commented 2 months ago

We had an initial enablement of the BayLibre lab on the new infra. Now we need to take the next steps to enable proper baseline and baseline-nfs at least on all boards. Enabling dt-kselftest would be great as well.

This will help us with #348 for example, which is currently a painful manual task Collabora team is doing.

khilman commented 1 month ago

It would be really helpful to have more details/docs/pointers on what this actually entails.

lab-baylibre is already running baseline in the legacy env (but not baseline-nfs ) and I thin we'd rather invest in dt-selftest than enabling NFS at this point.

So what exactly are the "next steps to enable proper baseline" tests in our lab?

khilman commented 1 month ago

For starters, how to we declare which boards in our lab should be available for the new infra. And similarily, can we just disable lab-baylibre for the legacy infra now?

nuclearcat commented 1 month ago

Sorry for late answer, we are implementing such feature, so each lab member can set list of boards available in lab directly under lab definition in config.

pawiecz commented 1 month ago

lab-baylibre is already running baseline in the legacy env (but not baseline-nfs ) and I thin we'd rather invest in dt-selftest than enabling NFS at this point.

So what exactly are the "next steps to enable proper baseline" tests in our lab?

baseline from the new system are already run in Baylibre's lab:

  1. Scheduler entries for submitting LAVA TestJobs: arm, x86
  2. Test node example with its LAVA TestJob

Enabling -nfs job would ensure that devices also work with a more feature-rich rootfs which will be used for more complex test suites. It would boil down to creating another scheduler entry (like the ones linked above in (1)) with boot_commands parameter set to nfs (similarly to baseline-nfs-arm64-mediatek job)

Enabling kselftest-dt job wouldn't be much different, it would involve:

  1. adding a jobs entry for Baylibre lab
  2. adding a scheduler entry which would trigger that ^ job
  3. adjusting runtime and platforms sections to select the lab and device types

For starters, how to we declare which boards in our lab should be available for the new infra.

Currently selection is done per scheduler entry (platforms section). PR linked in this issue might change it in the future.

And similarily, can we just disable lab-baylibre for the legacy infra now?

I'll look for a PR that makes similar change in the legacy config

padovan commented 22 minutes ago

@nuclearcat since you are going to disable lab-collabora on legacy already, can you disable lab-baylibre too, as per @khilman comments above.

Other than that, Is everything done here? can this issue be closed already?