Michael,
I'm not sure I understand your problem here. Deploy action is meant to deliver software to your hardware. Do you mean that the software doesn't change on your board?
If you change the software, but there is no way to write anything (ro filesystem) you have 2 options: - interactive test: https://validation.linaro.org/static/docs/v2/actions-test.html#index-1 IIRC it doesn't create any overlay on the DUT
- monitor test: https://validation.linaro.org/static/docs/v2/actions-test.html#index-2 This one only listens to what the DUT produces on the console and tries to match the pattern (that you can define) to fish out your test results
Last alternative is to let the tests run and then postprocess the results yourself.
Best Regards, Milosz
On Wed, Feb 7, 2024 at 11:11 PM Michael Peddie michael.peddie@gallagher.com wrote:
Hi again,
Just a quick follow-up to this. I did some re-reading (paying a little more attention to make sure I didn't miss anything), and still don't think there is a to: for the deploy action that I can use for my purposes. As stated previously, the file system is read-only, so is there a deploy that goes to the dispatcher and runs the commands over serial from there? From your explanation about the test job, that seems possible, but I'm not sure because (at least to me) the documentation on the deploy action is unclear.
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