On Tue, 17 Mar 2020 at 12:30, koti koti <kotisoftwaretest(a)gmail.com> wrote:
> I have successfully booted the Beagelbone board from "https://github.com/danrue/lava.therub.org" . (corresponding ymal is https://github.com/danrue/lava.therub.org/blob/master/server-overlay/etc/la…)
> But, now I am trying to run one more scenario (may be new scenario and not sure is it supported by LAVA lab?) i.e
> 1. Run the tests on already provisioned (boot) beagelbone board. (Basically I am skipping the booting mentioned and trying to run on the already provisioned/boot board)
> a) boot the target
> b) Connect Board to LAVA lab
> c) Just check the login prompt ("#") is available or not?
> c) Run the using below test definition file (Basically this test definition file runs "ls"/"ifconfig" commands in the already provisioned(boot) board).
> device_type: beaglebone-black
> job_name: beaglebone-black healthcheck
> minutes: 10
> minutes: 5
> priority: high
> visibility: public
> - test:
> - name: ls test
> prompts: ["#"]
> echo: discard
> - name: ls
> command: ls
> - message: "ls simple test successes"
> - message: "TIMEOUT"
> exception: InfrastructureError
> error: "ls command failed"
> - name: ifconfig
> command: ifconfig
> - name: wait for the prompt
> I have tried to run this. But, my test failed with the error ""Connection closed"" (Attached screenshot)
Connection closed is usually not sth wrong with LAVA but with serial.
Are you able to connect to the board by telneting to your ser2net
port? I assume you use ser2net as in Dan's example. If not, could you
explain how do you connect to the BBB's UART?
> Can some one let me know solution to fix this error?
> Lava-users mailing list