Hi,
I hope to be able to test whether the system can boot normally after multiple restarts (10,000 times)
Because every boot requires the auto_login of the boot action, it seems that a loop needs to be implemented in yaml, and this loop needs to include the boot action. Are there any relevant examples that you can refer to?
There are roughly two types of test logic
1:
while (a<10000)
{
-boot
auto_login
- test
basic io test
software reboot in target board
a=a+1
}
2:
while (a<10000)
{
-boot
auto_login
- test
basic io test
a=a+1
hardware reboot in worker
}
Thanks
Hi,
I am trying to use transfer_overlay as the fs on my DUT is read-only, but the /data/ and /tmp/ directories are writeable to some extent.
I have a working method to use wget, and it works when I use it manually to download the overlay tarball over http, both on my DUT and on the worker device.
However, the LAVA test itself always returns the error 'Network Unreachable'
What are the possible reasons for this?
Best regards,
Michael
Hi Team
Currently for the developing and running of the lava tests, we always run on the Lava master machine through lavacli. But we would like to skip the part of the running the tests from the lava master machine while developing, testing and triaging the tests written in the lava. We only want to run tests which are tested correctly to be run on through ci/cd on the lava master and for development, triaging we want to only use the lava-worker and board. We only want to use the lava master only through CI/CD.
[cid:86e0132a-a975-4d04-9f31-9a89237339d8]
Is there any way to run tests directly from the lava worker instead of going through lava master. I tried "lava-test-shell" and "lava-dispatcher" but it didnt work for me. Can I use the lava api for developing and triaging the test scripts?
Can you please recommend the best practice or setup for developing, testing and triaging the tests written in the lava? so that anyone can run, develop or modify tests quickly and make sure its successful and then only it can run through the lava master machine.
Regards,
Swapnil Tilaye
Hi all,
over the last days I was trying to bring up a setup where we simply try
to boot up a kernel and initrd combination that is provided by Debian
"as is". Sounds trivial at first but I ran into a problem with the
initrd:
The initrd contains some microcode, shipped as prepended uncompressed
archive. The microcode is added because the intel-microcode package was
installed during image generation.
When such an initrd enters the LAVA machinery, where the initrd is
first unpacked and later re-packed the file gets corrupted in a way
that the kernel is unable to unpack/use it. The end result was that NFS
boot did not work as the mounting of the rootfs did not take place.
Interestingly there is no error message, not within the unpack/repack
step in LAVA and the kernel does not complain later during the boot
sequence either.
To disable the LAVA unpack/repack sequence I had to modify my deploy
action. Setting install_overlay and install_modules [2] to false seems
to qualify as workaround:
- deploy:
timeout:
minutes: 15
to: tftp
kernel:
url: <kernel-url>
ramdisk:
url: <initrd-url>
install_overlay: false
install_modules: false
Looking at the initramfs-tools implementation [1] I think that
something similar is missing in LAVA.
Does that make sense? Ideas / comments?
Best regards,
Florian
[1] https://gitlab.com/lava/lava/-/blob/master/lava_dispatcher/actions/deploy/a…
[2] https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/unmkinit…
--
Siemens AG, Technology
Linux Expert Center
Hi,
We are seeing below the "Proxy Error" message while loading log size logs
from the LAVA job .
Is there any solution to load a long size log file from a LAVA job ?
[image: image.png]
Hi All,
My board is configured at 55000 baud for serial communication. Can work
only at this baud, Can we use lava with this configuration to get console
prints in test method. Default lava is supporting telnet with standard baud
rates. Is there a way to make 55000 baud for uart and get prints on lava.
Regards
Nagendra S
Hi,
In a previous thread where I was getting help to do a serial connection, I also needed help with the deploy action towards the end, so I'm just continuing that here.
I have been trying to do a deploy action for a couple of days now, and have been unsuccessful thus far. The obvious first hurdle is the image URLs for the various things needed for a tftp deploy action. I have compiled a u-boot kernel, and a DTB came with it, and I managed to sort the few errors I got with those (for now at least). I'm not sure modules are necessary, but I can figure that out later. The biggest issue I'm having is with the ramdisk.
There are many resources online for creating a ramdisk, but it is just a space in the ram for things to be stored temporarily (which I don't mind). But this does not work for lava, as it seems to require a file. I have tried compressing the directory created, and passing that, but because it is still just a directory lava won't accept it after I start the job.
So I'm assuming I have to acquire some kind of image somehow, how can I do this? Is there an online source I can download from? Or if I have to make it, how?
Best regards,
Michael