Hi,
I'm trying to run some android tests using multi-node API. In order to make sure both nodes of the multi-node job are in known state I'm using lava-wait test_started/test_finished signals to sync between nodes. Signals are prefixed so they identify host-target lava-test-shell pairs with unique names. This works well when there is only one test scheduled in a job. If anything goes wrong, the worst case is tests will time out. However in case there are more tests scheduled in a single job, the flow control sometimes fails. It happens when lava-test-shell times out on one node. In this scenario I'm doing:
1. host (wait for test_started from target) 2. target -> test_started -> host
Tests are executed...
3. target (wait for test_finished from host) 4. time out on host
So in this scenario target waits for the test_finished signal and eventually times out as well (as the signal never comes). At the same time host node already starts executing next lava-test-shell when it waits for test_started signal from target. So nodes go out of sync and the job produces no results. Is there any way to avoid such situation?
Best Regards, milosz
Hi Milosz,
On Monday 18 August 2014 05:57 PM, Milosz Wasilewski wrote:
I'm trying to run some android tests using multi-node API. In order to make sure both nodes of the multi-node job are in known state I'm using lava-wait test_started/test_finished signals to sync between
Can you point me to a job where you observe this? I can take that as an example and see what could be done on lava side to have a proper solution.
Thank You.
On 20 August 2014 19:09, Senthil Kumaran senthil.kumaran@linaro.org wrote:
Hi Milosz,
On Monday 18 August 2014 05:57 PM, Milosz Wasilewski wrote:
I'm trying to run some android tests using multi-node API. In order to make sure both nodes of the multi-node job are in known state I'm using lava-wait test_started/test_finished signals to sync between
Can you point me to a job where you observe this? I can take that as an example and see what could be done on lava side to have a proper solution.
Hi Senthil. Here is example: https://validation.linaro.org/scheduler/job/148409/ Not the best one as there is only one test shell, but shows the problem.
milosz
Thank You.
Senthil Kumaran http://www.stylesen.org/ http://www.sasenthilkumaran.com/
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
On Thursday 21 August 2014 03:17 PM, Milosz Wasilewski wrote:
https://validation.linaro.org/scheduler/job/148409/ Not the best one as there is only one test shell, but shows the problem.
Thanks Milosz, will find a solution for the same.
Thank You.
linaro-validation@lists.linaro.org
-
Milosz Wasilewski -
Senthil Kumaran