Hello,
I would like to change path to /mnt from below: "lava_test_dir": "/lava-%s", "lava_test_results_dir": "/lava-%s",
I am using an immutable image and due to which don't have permission to write, so cannot create directory eg /lava-34 due to which cannot execute test. We have partition /mnt which we can mount and run the test cases over our os. But for that to work I need to change path. I tried changing it in /usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py , but jobs fails once I change it. I have only changed the debian section as the image we are using is a debian image.
Could you please help me if there is any option to make these changes while executing job or any other file for devices.
Thanks, Sweta
On Mon, Jul 8, 2024 at 2:09 PM sweta.ghosh@nagarro.com wrote:
Hello,
I would like to change path to /mnt from below: "lava_test_dir": "/lava-%s", "lava_test_results_dir": "/lava-%s",
These can be changes in the job context: context: lava_test_results_dir: "/mnt/lava-%s"
context is a top level element in the lava job yaml.
I am using an immutable image and due to which don't have permission to write, so cannot create directory eg /lava-34 due to which cannot execute test. We have partition /mnt which we can mount and run the test cases over our os. But for that to work I need to change path. I tried changing it in /usr/lib/python3/dist-packages/lava_dispatcher/deployment_data.py , but jobs fails once I change it. I have only changed the debian section as the image we are using is a debian image.
Could you please help me if there is any option to make these changes while executing job or any other file for devices.
One more thing you have to manage is delivering lava overlay to the board. After changing the context, lava will expect the test-shell scripts to be present in the proper path. In your case it will be /mnt/lava-%s/bin/. I don't know how you add overlay to the image, but please bear in mind that when creating overlay, the path from lava_test_results_dir is ignored. I think it's a bug, but fixing it seems pretty hard (a lot of potential problems to solve).
Best Regards, Milosz
Hi Milosz,
Thanks for replying, after adding it below context. But it is still trying to create /lava-%s : device_type: qemu job_name: CIS Benchmark Test on Debian QEMU timeouts: job: minutes: 15 action: minutes: 5 connection: minutes: 2 priority: medium visibility: public context: arch: amd64 lava_test_results_dir: "/mnt/lava-%s" actions: - deploy: timeout: minutes: 5 to: tmpfs
On Mon, Jul 8, 2024 at 2:41 PM sweta.ghosh@nagarro.com wrote:
Hi Milosz,
Thanks for replying, after adding it below context. But it is still trying to create /lava-%s :
Hmm, maybe there is a bug on qemu jobs. I'm getting the same result: https://lava.infra.foundries.io/scheduler/job/46687#L620
As I mentioned, there are a lot of places in lava dispatcher code that ignore lava_test_results_dir setting. Is qemu your final target? If not, maybe try on HW. The deployment code is different there.
Best Regards, Milosz
Actually we want to use LAVA to test both on HW and using qemu for initial image testing. Is there any bug opened for the same that I can follow ? As we are planning to use LAVA for all our testing requirements.
Thanks, Sweta
Sweta,
I'm not aware of any open bug. You can report one in gitlab project: https://gitlab.com/lava/lava/-/issues I noticed this very recently. When LAVA creates an overlay tarball it also ignores the lava_test_results_dir. So applying overlay using LAVA deployments (for example deploy-to-downloads) will result in a broken test job if lava_test_results_dir is present in the job context. I'm pretty sure there are many more places when the variable is not taken into account. I was planning on fixing it, but I'm not sure I want to wait several months to get my fixes reviewed and merged.
Best Regards, Milosz
On Tue, Jul 9, 2024 at 7:43 AM sweta.ghosh@nagarro.com wrote:
Actually we want to use LAVA to test both on HW and using qemu for initial image testing. Is there any bug opened for the same that I can follow ? As we are planning to use LAVA for all our testing requirements.
Thanks, Sweta _______________________________________________ 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
Thanks a lot Milosz for your quick inputs. I have raised an issue . Hope to see it fixed in upcoming releases. https://gitlab.com/lava/lava/-/issues/662 .
lava-users@lists.lavasoftware.org
-
Milosz Wasilewski -
sweta.ghosh＠nagarro.com