On Mon, Feb 12, 2024 at 9:16 PM Michael Peddie michael.peddie@gallagher.com wrote:
I have tried uuu for deplo, and I kept getting the following error: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error Or it would simply get stuck and load for a while before I cancelled the job (with an error message before that saying /lava-x/bin/lavatest couldn't be found)
uuu is for NXP boards: https://github.com/nxp-imx/mfgtools Looking at the source, uuu deployment adds an overlay. So if you're on the NXP board and you don't have any signature verification this should work OK. I've never done it though.
So I think if I'm going to do an overlay, regardless of the read-only nature of the fs, I need to get an image that is compatible. Unless it can be booted on a device other than the DUT (virtual or no) and the tests run over serial. I have tried starting a QEMU device on the worker and running over serial from there (kind of ridiculous I know), but that has it's limits with telnet and exiting cleanly.
qemu is good to start with.
For the overlay part it consists of a few scripts that are part of LAVA source code: https://gitlab.com/lava/lava/-/tree/master/lava_dispatcher/lava_test_shell?r... On top of that there will be a set of test-definitions (if you include them in the test job). Some deployments methods modify the software you're delivering to the board beforehand, so once you have the software running on your HW the overlay is already there. There will still be some limitations coming from read-only fs, but you should be able to run more complex tests. Here is the source: https://gitlab.com/lava/lava/-/blob/master/lava_dispatcher/actions/deploy/ap... This won't work if you have any boot signing process in place as LAVA will attempt to modify images and this will invalidate their signatures.
I have tried the interactive tests you sent before, and those are great for smoke tests, but I'm unsure about their use for longer or more complex tests that may be better run with scripts. Unless it's possible to run scripts stored locally on the worker through it, or downloaded from a git repo? (the latter I know isn't strictly possible, as Lava Test Def 1.0 tests are for that purpose). Which is why I'm back trying to get deploy working, so I can write a Lava Test Def 1.0 job and run it.
Interactive tests are meant for the environments where you don't have a POSIX compliant shell (like u-boot shell). I guess they can also be used to overcome the read-only filesystem. But for complex cases where you need scripting it won't be a viable replacement.
I will try tftp, though I will probably spend more time looking for those urls then writing and waiting for the job to run. Thank you very much.
learning curve is steep here :/
Best Regards, Milosz
Best regards, Michael _______________________________________________ lava-users mailing list -- lava-users@lists.lavasoftware.org To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s