Michael,
On Wed, Jun 19, 2024 at 11:45 PM Michael Peddie michael.peddie@gallagher.com wrote:
Hi Milosz,
After some further looking and discussion with others, do you think it is possible that the way the command I'm running works could be the issue?
The command gets passed flags and arguments, and after processing that spawns a child thread, after which the parent thread from the initial call ends to let the child thread run. Is it possible that LAVA is picking up on the parent thread ending and not letting the child thread run through?
This sounds plausible. I don't think LAVA would stop execution for the background task or thread. Test execution in LAVA is pretty simple. It calls run.sh script that it creates from test-definition steps [1][2]. Once the steps exit, LAVA test execution completes. Anything running in the background is ignored.
I can't tell much without looking at the code. Your code is in the private repository, so there isn't much for me to comment on.
[1] https://gitlab.com/lava/lava/-/blob/master/lava_dispatcher/lava_test_shell/l... [2] https://gitlab.com/lava/lava/-/blob/master/lava_dispatcher/lava_test_shell/l...
Best Regards, Milosz
I am working on testing this with custom scripts, but that is the leading idea at the moment, please let me know what you think.
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