Hi everyone,
As I have probably mentioned in previous emails, Im using the yocto project to generate some linux images that I want to test using lava as part of the continuous integration development.
So far so good, i can submit the job description to lava using lava-tool and it will start the tests. I'm happy so far with all the results.
Now my question is to ask you what would be the correct way do this procedure. Do you think it is reasonable to have a lava-tool submit-job followed by a waiting step using lava-tool job-status to report the final build result? or there is a nicer way to do this?
Thanks a lot for your help in advance :)
Best,
Alfonso
On 20 October 2016 at 08:34, alfonso alfonso.ros-dos-santos@evosoft.com wrote:
Hi everyone,
As I have probably mentioned in previous emails, Im using the yocto project to generate some linux images that I want to test using lava as part of the continuous integration development.
So far so good, i can submit the job description to lava using lava-tool and it will start the tests. I'm happy so far with all the results.
Now my question is to ask you what would be the correct way do this procedure. Do you think it is reasonable to have a lava-tool submit-job followed by a waiting step using lava-tool job-status to report the final build result? or there is a nicer way to do this?
Yes, there is a nicer way to do this. We're in the process of creating examples and documentation as one of the tasks at the LAVA Sprint this week. It will use ZMQ and a project called ReactoBus to push notifications that the test job has finished instead of polling on XML-RPC. This solves the waiting step problem without adding load to the server by asking "are we there yet" every minute over XML-RPC.
http://ivoire.dinauz.org/linaro/bus/
https://github.com/ivoire/ReactOBus
We hope to have more detailed information on adopting this method soon.
lava-users@lists.lavasoftware.org