Hi,
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/lav... )
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 timeouts: job: minutes: 10 action: minutes: 5 priority: high visibility: public actions: - test: interactive: - name: ls test prompts: ["#"] echo: discard script: - name: ls command: ls successes: - message: "ls simple test successes" failures: - message: "TIMEOUT" exception: InfrastructureError error: "ls command failed" - name: ifconfig command: ifconfig - name: wait for the prompt command: "
I have tried to run this. But, my test failed with the error ""Connection closed"" (Attached screenshot)
Can some one let me know solution to fix this error?
Regards, koti
On Tue, 17 Mar 2020 at 12:30, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
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/lav...)
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
- 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 timeouts: job: minutes: 10 action: minutes: 5 priority: high visibility: public actions:
- test:
interactive:
- name: ls test
prompts: ["#"] echo: discard script:
- name: ls
command: ls successes:
- message: "ls simple test successes"
failures:
- message: "TIMEOUT"
exception: InfrastructureError error: "ls command failed"
- name: ifconfig
command: ifconfig
- name: wait for the prompt
command: "
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?
milosz
Can some one let me know solution to fix this error?
Regards, koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Tue, Mar 17, 2020 at 12:46:19PM +0000, Milosz Wasilewski wrote:
On Tue, 17 Mar 2020 at 12:30, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
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/lav...)
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
- 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 timeouts: job: minutes: 10 action: minutes: 5 priority: high visibility: public actions:
- test:
interactive:
- name: ls test
prompts: ["#"] echo: discard script:
- name: ls
command: ls successes:
- message: "ls simple test successes"
failures:
- message: "TIMEOUT"
exception: InfrastructureError error: "ls command failed"
- name: ifconfig
command: ifconfig
- name: wait for the prompt
command: "
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?
I think he's asking if he can skip the provisioning (deploy/boot) part of the job. That's his complete job above. I told him I don't think it is possible, is it?
Dan
milosz
Can some one let me know solution to fix this error?
Regards, koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-devel mailing list Lava-devel@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-devel
Hi Dan/Milosz/ivoire,
Really appreciated your support.
Finally now I am able to run the tests on Provisioned board successfully with your awesome support using LAVA. (I am successfully done on both beagleblack and Dragon)
Steps: ####### 1. Install the LAVA in local host (initially using docker) 2. Connect the Provision board. (boot board) 3. Setup Serial ports confirmation files. 4. Run the below tests (Initially) a) ls b) ifconfig b) reboot c) shutdown etc....
As per your suggestions , It is worked as expected using below test definition yaml file. ( Even though I have couple of errors/queries to resolve . Hope I can resolve those also from mailing list)
" device_type: beaglebone-black job_name: beaglebone-black healthcheck timeouts: job: minutes: 30 action: minutes: 15 connection: minutes: 5 priority: medium visibility: public context: test_character_delay: 10 actions: - boot: timeout: minutes: 15 method: minimal auto_login: login_prompt: '.* login:' username: root prompts: - root@bblack:~# - test: interactive: - name: ls test prompts: ["#"] echo: discard script: - name: ls command: ls successes: - message: "ls simple test successes" failures: - message: "TIMEOUT" exception: InfrastructureError error: "ls command failed" - name: ifconfig command: ifconfig - name: wait for the prompt command: uname -a - boot: timeout: minutes: 15 method: minimal auto_login: login_prompt: '.* login:' username: root prompts: - root@bblack:~# - test: interactive: - name: ls test prompts: ["login"] echo: discard script: - name: reboot command: reboot successes: - message: "reboot test" failures: - message: "TIMEOUT" exception: InfrastructureError error: "reboot command failed" " Note: 1. Dan, Really appreciated your time and support in initially to setup my Docker LAVA lab. 2. milosz, I have setup serial port as per "Dan" suggestion and tested from "telnet ser2net 5001". Its working as expected yesterday it self.
Regards, Koti
On Tue, 17 Mar 2020 at 18:40, Dan Rue dan.rue@linaro.org wrote:
On Tue, Mar 17, 2020 at 12:46:19PM +0000, Milosz Wasilewski wrote:
On Tue, 17 Mar 2020 at 12:30, koti koti kotisoftwaretest@gmail.com
wrote:
Hi,
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/lav... )
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
- 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 timeouts: job: minutes: 10 action: minutes: 5 priority: high visibility: public actions:
- test:
interactive:
- name: ls test
prompts: ["#"] echo: discard script:
- name: ls
command: ls successes:
- message: "ls simple test successes"
failures:
- message: "TIMEOUT"
exception: InfrastructureError error: "ls command failed"
- name: ifconfig
command: ifconfig
- name: wait for the prompt
command: "
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?
I think he's asking if he can skip the provisioning (deploy/boot) part of the job. That's his complete job above. I told him I don't think it is possible, is it?
Dan
milosz
Can some one let me know solution to fix this error?
Regards, koti _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Lava-devel mailing list Lava-devel@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-devel
-- Linaro LKFT https://lkft.linaro.org
lava-users@lists.lavasoftware.org
-
Dan Rue -
koti koti -
Milosz Wasilewski