Hi
definition: DUT = device under test
I am not agree to change the dispatcher. The suggested solution will not solve the root problem LAVA is facing today (unstable system) and also put the unneccessary constraint on LAVA by only allow DUT based test scenario (I mean the tests run isolated in DUT).
There are many tests which require host / DUT communication during the test execution. Actually the test scenario is on host side and send command to target to perform action on the DUT.
Example if you test WLAN roaming, the test scenario is on the host, controlling both the WLAN simulator and the DUT.
Other example is multiple DUT tests.
The serial port problem is a side effect when LAVA server is overloaded. Same with the 'wget image' problem.
The solution is not overload the LAVA server. Possible solutions are :
* Make the scheduler more intelligent and scheduler out job evently (it make no sense to start more jobs than the lava server can handle) * Distribute heavy task to cloud instances * Update lava-dispatcher to retry if fail on some operations.
/Chi Thu