Hi,all: If devive have boot successed，can I skip deploy and boot step in job.yaml?
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Hi Xuelian,
What do you mean by boot successed? Could you please provide more details? If you don’t have boot and deploy step in job.yaml then LAVA will raise error like ‘No boot action result found’ and job will fail then.
I think it is necessary to have boot and deploy part in your job, even if they are totally empty and did nothing. :)
Neil please correct me if I am wrong.
-Yifan
From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Li, Xuelian Sent: Friday, June 30, 2017 4:15 PM To: lava-users@lists.linaro.org Subject: [Lava-users] job yaml
Hi,all: If devive have boot successed，can I skip deploy and boot step in job.yaml?
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
On 30 June 2017 at 09:32, Li, Yifan2 yifan2.li@intel.com wrote:
Hi Xuelian,
What do you mean by boot successed? Could you please provide more details? If you don’t have boot and deploy step in job.yaml then LAVA will raise error like ‘No boot action result found’ and job will fail then.
Not rebooting a device between tests has problems because the next test does not know whether the device is in a usable state - the previous test could have caused a kernel panic.
Not deploying between tests has problems that the next test does not know what system has been deployed, so could try to run a completely impossible test (e.g. installing an OpenEmbedded package on Android).
In both cases, you have all of the problems of persistence. https://validation.linaro.org/static/docs/v2/dispatcher-design.html#persiste...
Overall, it does not save you any time at all.
I think it is necessary to have boot and deploy part in your job, even if they are totally empty and did nothing. J
Not necessarily. However, persistence requires careful preparation and management of the device and *all* the test jobs.
It is *always* better to deploy and boot on every test, otherwise the results you get could be completely meaningless.
Neil please correct me if I am wrong.
-Yifan
*From:* Lava-users [mailto:lava-users-bounces@lists.linaro.org] *On Behalf Of *Li, Xuelian *Sent:* Friday, June 30, 2017 4:15 PM *To:* lava-users@lists.linaro.org *Subject:* [Lava-users] job yaml
Hi,all:
If devive have boot successed，can I skip deploy and boot step in job.yaml?
This email is intended only for the named addressee. It may contain information that is confidential/private, legally privileged, or copyright-protected, and you should handle it accordingly. If you are not the intended recipient, you do not have legal rights to retain, copy, or distribute this email or its contents, and should promptly delete the email and all electronic copies in your system; do not retain copies in any media. If you have received this email in error, please notify the sender promptly. Thank you.
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
-
Li, Xuelian -
Li, Yifan2 -
Neil Williams