-
Notifications
You must be signed in to change notification settings - Fork 36
config: expand ramdisk-based kselftest pipeline with new job definitions #1367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This change expands the ramdisk-based kselftest pipeline by adding a new job definition and parameters suitable for ramdisk boot. Signed-off-by: Yogesh Lal <[email protected]>
|
I wonder if we can add some example job and run somewhere on staging? maybe in some qemu |
|
We could add the networking kselftest perhaps - that can't run from NFS root due to messing with the network configuration? I'd be happy to have that scheduled in my lab - running it on the i.MX8MP-EVK should be a good fit, it's got 6G of RAM which should be good for ramdisks and there's a decent amount of availability. |
let me add it but will not able to test due to lack of env as of now. |
Deployed in Qualcomm LAVA Lab, following are few examples: kselftest-cpufreq-ramdisk : https://lava-oss.qualcomm.com/scheduler/job/12113 Will update PR as infra migrated to gcc-14 |
Looks good. FWIW I think coredump failed because coredump isn't built, so looks like a build issue. |
This change expands the ramdisk-based kselftest pipeline by adding a new job definition and parameters suitable for ramdisk boot.
This will address #1366