On 19 April 2016 at 14:03, pradeepkumar pradeep.soman@u-blox.com wrote:
I have made a test setup with LAVA to run some test cases on my AM335X based platform. I want to execute some simple test cases like testing the status of "ifconfig eth0" command. I don't want to deploy any image and my goal is to execute only this test directly(target is booted with root file system mounted)
But it is booted into an image with a prompt that LAVA V1 does not recognise.
Lava dispatcher is able to connect to the target and start the job. But finally I am getting a timeout. Please find the attached log for details. I can see that after connecting with the target the dispatcher is checking/finding some information related to the file system, and looks like it is getting timed out there.
It is looking for a shell prompt:
4.0 <LAVA_DISPATCHER>2016-04-19 11:38:23 AM DEBUG: expect (10): '['root@master \[rc=(\d+)\]# ', <class 'pexpect.TIMEOUT'>]'
6.0 root@elin-w160-evk:~#
How can I avoid this and make the dispatcher to directly perform the test on the target platform?
The list of test shell prompts in LAVA V1 using the test_image_prompts variable in the device configuration.
<LAVA_DISPATCHER>2016-04-19 11:38:33 AM INFO: IN the system master image
You have set this device as a master image type device in the device configuration, so that mandates that the booted image *must* come up into a master image and that kind of image *always* has a 'master' hostname, so matches the root@master prompt.
You need to change the device configuration to not be a master device and change the test_image_prompts *or* change the hostname of the device.