Hi all

Problem 1:

I find Lava2 re-download Test case repository if more than two test suite needed test in a lava job. Personal think this is waste of time. How can I make lava download Test

case repository only once in a lava job ( ps : all of our test suite in some repository) .I want to know lava can do or cant not do, if can please tell me how to do THX.

Problem 2:

As all we know lava must install os before execute the test task in standard procedure. But in our practical application we find no need mechanical implementation of the

Process. In some case, we just need install os only ones and repeated test, even we install manually os and just use lava to do test. We want lava2 like M-lab install os and

execute test task uncoupling. we met the problems : can not judge the os installed in DUT(device under test ) whether is our SUT(system under test). All caused by very little

information can we read from DUT. I want to know how can I uncoupling install system and execute test ,user can choose only install os 、only execute test 、install os and execute

test 、install os ones and repeat execute test ...

problem 3:

According to your experience, optimally how many DUT can mount under a lava worker and what is a constrain bottleneck?

Best

coston