On Mon, 17 Sep 2018 at 12:14, john zhang email@example.com wrote:
In lava job definition, boot action can use "connection-namespace" to indicate use previous namespace's connection.Does deploy action have such as "deploy-namespace" to indicate to use previous deploy image?
I think you have misunderstood namespaces.
connection-namespace is a specialised feature to reuse serial connections.
For example in an application scenario, it need to sequential execution two phases pipeline(deploy,boot,test), it can be solved by define two namespace in job definiton. When run it executed in serial as : phase1(namespace1) deploy->boot->test -> phase2(namespace2) deploy->boot->test. If phase2 deploy images(kernel,dtb,rootfs) are exactly same as phase2 deploy images,how to speed up phase2 deploy execution?
Namespaces cannot help with that directly. Namespaces are about separating the dynamic data within the test job.
Please attach your current test job definition so that we can describe how to improve it. Depending on how the device integration works, you may be able to simply skip the second deploy step and just do deploy boot test boot test all in a single namespace. This won't work for some deployments like TFTP.
I guess if deploy action have such as "deploy-namespace" to indicate previous deploy,then phase2 deploy process can be pass.
Lava-users mailing list Lavafirstname.lastname@example.org https://lists.linaro.org/mailman/listinfo/lava-users