On Wed, 15 Apr 2020 at 08:24, Larry Shen larry.shen@nxp.com wrote:
Hi, there,
Frequently, I found when a job becomes incomplete there will immediately a health check job on that device happen automatically to check the status of the device.
But strange, some times I won’t see that healthy check job.
So, my question is: when I see that healthy check job, is it just by chance? Or it really designed that there will be a healthy check after incomplete job? Thanks.
IIRC health check is triggered always after 'infrastructure error'. So if your test job goes incomplete due to timeout in a test shell there won't be a health check after it. But if there is an error caused by infrastructure (in LAVA terms), for example 'connection closed', a health check will be triggered. You can also configure LAVA to run health check after N ordinary jobs. I can imagine N=1. This has a practical application. For example health check might bring the board to the desirable condition.
milosz
Regards,
Larry
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users