-
Notifications
You must be signed in to change notification settings - Fork 2
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
GKernelCI V2 #6
Comments
|
Topic: LAVA instance
Furthermore, having persistent LAVA instance permit developper to use them out-of-buildbot. (for hacking sessions for example) EXTRA-bonus: Having persistent LAVA instance permit to share them to other CI project. ( kernelci ;) ) |
Topic: rootfs type choice Very probably ramdisk should be avoided, a gentoo rootfs is too big, while on qemu-with-lot-of-ram it could work (but I fail on it), on real physical board it will be impossible. On qemu you could use rootfs as hard disk image but this method is not available on real boards. Note: unrelated to rootfs type LAVA will download it anyway, so your fileserver must be an HTTP server. |
yes, the LAVA instance will be persistent. |
Thanks I will take this in considerations.
yes the fileserver is http. |
|
hard disk space as been added to both machine (thanks gentoo-infra) |
GKernelCI is currently sending reports to KCIDB |
Currently we are not making our own rootfs but we are using stage3 instead. |
|
As currently GKernelCI v2 surpassed the features of GKernelCI v1 we can close this issue |
diagram:

docker-compose up -d
The text was updated successfully, but these errors were encountered: