test/tests execution on provision (booted) board with out "-boot" section. (Basically I am skipping deploy and boot sections)
Hi,
I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
1. Basically I am facing the connection issue with out "-boot" section. 2. Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file) 3. Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive: - name: reset prompts: ["#"] script: - name: reset command: reset
"
Regards, Koti
Hi,
The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot" section.
- Why this dependency to connect terminal for boot section ? ( I am
able to connect serial port when I use "-boot" section in yaml file) 3. Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti kotisoftwaretest@gmail.com a écrit :
Hi,
The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board
using
attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned
(booted)
board with out "-boot" section. (you can see my YAML file as
mentioned
below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot"
section.
- Why this dependency to connect terminal for boot section ? ( I
am
able to connect serial port when I use "-boot" section in yaml file) 3. Please can some one provide me right YAML to run my tests with
out
"-boot" section. ( to resolve serial connection issue with out
"-boot"
section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
Hi Remi Duraffort,
Thanks for you reply.
1. beaglebone: (success) ############# a. Yes. it is working with "minimal" for begalbone. ( I am able to run the test with out deploy and falsh . attached the YAML file which I have used) b. I am fine with minimal for begalbone to run the tests for Provisioned board.
2. dragonboard-845c: (still I am facing the issue) ################## a). is any one tried Provision boot (bootee board) with "minimal" method for Dragonboards? b). I am facing the issue to run the health checkup using "minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
Please can some let me know your suggestions for "dragonboard" minimal boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort remi.duraffort@linaro.org wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti kotisoftwaretest@gmail.com a écrit :
Hi,
The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot"
section. 2. Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file) 3. Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
On Fri, 27 Mar 2020 at 13:57, koti koti kotisoftwaretest@gmail.com wrote:
Hi Remi Duraffort,
Thanks for you reply.
- beaglebone: (success)
############# a. Yes. it is working with "minimal" for begalbone. ( I am able to run the test with out deploy and falsh . attached the YAML file which I have used) b. I am fine with minimal for begalbone to run the tests for Provisioned board.
- dragonboard-845c: (still I am facing the issue)
################## a). is any one tried Provision boot (bootee board) with "minimal" method for Dragonboards? b). I am facing the issue to run the health checkup using "minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
In our instance this isn't possible as we deleted 'boot' partition. So the board will go to fasboot by default.
milosz
Please can some let me know your suggestions for "dragonboard" minimal boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort remi.duraffort@linaro.org wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti kotisoftwaretest@gmail.com a écrit :
Hi,
The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot" section.
- Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file)
- Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Thanks Milosz.
what do you mean by "as we deleted 'boot' partition " in your previous email?
But, I am seeing "-boot" partition for one of the Dragon board YAML file i.e https://staging.validation.linaro.org/scheduler/job/269261/definition#deflin... (line number 72).
Regards, Koti
On Fri, 27 Mar 2020 at 19:43, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Fri, 27 Mar 2020 at 13:57, koti koti kotisoftwaretest@gmail.com wrote:
Hi Remi Duraffort,
Thanks for you reply.
- beaglebone: (success)
############# a. Yes. it is working with "minimal" for begalbone. ( I am
able to run the test with out deploy and falsh . attached the YAML file which I have used)
b. I am fine with minimal for begalbone to run the tests forProvisioned board.
- dragonboard-845c: (still I am facing the issue)
################## a). is any one tried Provision boot (bootee board) with
"minimal" method for Dragonboards?
b). I am facing the issue to run the health checkup using"minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
In our instance this isn't possible as we deleted 'boot' partition. So the board will go to fasboot by default.
milosz
Please can some let me know your suggestions for "dragonboard" minimal
boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort remi.duraffort@linaro.org
wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti <
kotisoftwaretest@gmail.com> a écrit :
Hi,
The issue/error I am facing in results page with out "-boot" section
in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection
closed'
Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly.
Please report this error to LAVA admins.
case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com
wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board
using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned
(booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot"
section.
- Why this dependency to connect terminal for boot section ? ( I
am able to connect serial port when I use "-boot" section in yaml file)
- Please can some one provide me right YAML to run my tests with
out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser
ma brièveté.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Mon, 30 Mar 2020 at 11:17, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
what do you mean by "as we deleted 'boot' partition " in your previous email?
But, I am seeing "-boot" partition for one of the Dragon board YAML file i.e https://staging.validation.linaro.org/scheduler/job/269261/definition#deflin... (line number 72).
I meant boot partition on the board not boot action in LAVA. This means that we don't flash boot partition. In this case 1st stage bootloader always goes into fasboot mode so we can boot the board the same way always: https://staging.validation.linaro.org/scheduler/job/269261#L658
milosz
Regards, Koti
On Fri, 27 Mar 2020 at 19:43, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Fri, 27 Mar 2020 at 13:57, koti koti kotisoftwaretest@gmail.com wrote:
Hi Remi Duraffort,
Thanks for you reply.
- beaglebone: (success)
############# a. Yes. it is working with "minimal" for begalbone. ( I am able to run the test with out deploy and falsh . attached the YAML file which I have used) b. I am fine with minimal for begalbone to run the tests for Provisioned board.
- dragonboard-845c: (still I am facing the issue)
################## a). is any one tried Provision boot (bootee board) with "minimal" method for Dragonboards? b). I am facing the issue to run the health checkup using "minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
In our instance this isn't possible as we deleted 'boot' partition. So the board will go to fasboot by default.
milosz
Please can some let me know your suggestions for "dragonboard" minimal boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort remi.duraffort@linaro.org wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti kotisoftwaretest@gmail.com a écrit :
Hi,
The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote:
Hi,
I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml".
But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
Please can some one help me for the same?
- Basically I am facing the connection issue with out "-boot" section.
- Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file)
- Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
" device_type: beaglebone-black job_name: begalbone 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 ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~#
- test: interactive:
- name: reset prompts: ["#"] script:
- name: reset command: reset
"
Regards, Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
Thanks Milosz.
Is there any way to make fastboot as dummy section ? (Because , I want to connect the already provision board (booted board) to LAVA lab (I mean, we have flashed images already using fastboot and do not want go fastboot mode again through LAVA lab))
1. Is this implementation/support available for fastboot mode targets like Dragon, etc..? (this is available for begalbone target using "method: minimal" in "-boot" section) 2. It will be very use to users if they want to connect the already provisioned (Booted boards) targets to LAVA lab. 3. Can you let me know where I need to modify current LAVA code to achieve this?
Note: 1. This requirement can achieve for "Begalbone" boards using the sring " method: minimal " in "-boot" section. (this will be good if we implement this for "fastboot" targets also)
Regards, Koti
On Mon, 30 Mar 2020 at 15:53, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
On Mon, 30 Mar 2020 at 11:17, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
what do you mean by "as we deleted 'boot' partition " in your previous
email?
But, I am seeing "-boot" partition for one of the Dragon board YAML
file i.e https://staging.validation.linaro.org/scheduler/job/269261/definition#deflin... (line number 72).
I meant boot partition on the board not boot action in LAVA. This means that we don't flash boot partition. In this case 1st stage bootloader always goes into fasboot mode so we can boot the board the same way always: https://staging.validation.linaro.org/scheduler/job/269261#L658
milosz
Regards, Koti
On Fri, 27 Mar 2020 at 19:43, Milosz Wasilewski <
milosz.wasilewski@linaro.org> wrote:
On Fri, 27 Mar 2020 at 13:57, koti koti kotisoftwaretest@gmail.com
wrote:
Hi Remi Duraffort,
Thanks for you reply.
- beaglebone: (success)
############# a. Yes. it is working with "minimal" for begalbone. ( I am
able to run the test with out deploy and falsh . attached the YAML file which I have used)
b. I am fine with minimal for begalbone to run the testsfor Provisioned board.
- dragonboard-845c: (still I am facing the issue)
################## a). is any one tried Provision boot (bootee board) with
"minimal" method for Dragonboards?
b). I am facing the issue to run the health checkup using"minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
In our instance this isn't possible as we deleted 'boot' partition. So the board will go to fasboot by default.
milosz
Please can some let me know your suggestions for "dragonboard"
minimal boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort <
remi.duraffort@linaro.org> wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti <
kotisoftwaretest@gmail.com> a écrit :
Hi,
The issue/error I am facing in results page with out "-boot"
section in my YAML file is as follows i.e
" lava-dispatcher, installed at version: 2019.12 start: 0 validate Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) validate duration: 0.00 case: validate case_id: 339 definition: lava result: pass start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] start: 1.1 lava-test-interactive (timeout 00:15:00) [common] Connection closed end: 1.1 lava-test-interactive (duration 00:00:00) [common] case: lava-test-interactive case_id: 340 definition: lava duration: 0.00 extra: ... level: 1.1 namespace: common result: fail lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection
closed'
Connection closed end: 1 lava-test-interactive-retry (duration 00:00:00) [common] case: lava-test-interactive-retry case_id: 341 definition: lava duration: 0.00 extra: ... level: 1 namespace: common result: fail Cleaning after the job start: 2.1 power-off (timeout 00:00:10) [common] end: 2.1 power-off (duration 00:00:00) [common] case: power-off case_id: 342 definition: lava duration: 0.00 extra: ... level: 2.1 namespace: common result: pass start: 2.2 read-feedback (timeout 00:15:00) [common] end: 2.2 read-feedback (duration 00:00:00) [common] InfrastructureError: The Infrastructure is not working correctly.
Please report this error to LAVA admins.
case: job case_id: 343 definition: lava error_msg: Connection closed error_type: Infrastructure result: fail "
Regards, Koti
On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com
wrote:
> > Hi, > > I am able to boot and run the tests with Provisioned(booted)
board using attached YAML i.e "working_yaml.yaml".
> > But, I am facing the issue while running the tests on Provisioned
(booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now)
> > Please can some one help me for the same? > > 1. Basically I am facing the connection issue with out "-boot"
section.
> 2. Why this dependency to connect terminal for boot section ? (
I am able to connect serial port when I use "-boot" section in yaml file)
> 3. Please can some one provide me right YAML to run my tests
with out "-boot" section. ( to resolve serial connection issue with out "-boot" section)
> > > " > device_type: beaglebone-black > job_name: begalbone 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 > ## reset: false > ## auto_login: > ## login_prompt: '.* login:' > ## username: root > # prompts: > # - root@dragonboard-410c:~# > > - test: > interactive: > - name: reset > prompts: ["#"] > script: > - name: reset > command: reset > > " > > Regards, > Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez
excuser ma brièveté.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Mon, 30 Mar 2020 at 12:03, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
Is there any way to make fastboot as dummy section ? (Because , I want to connect the already provision board (booted board) to LAVA lab (I mean, we have flashed images already using fastboot and do not want go fastboot mode again through LAVA lab))
- Is this implementation/support available for fastboot mode targets like Dragon, etc..? (this is available for begalbone target using "method: minimal" in "-boot" section)
- It will be very use to users if they want to connect the already provisioned (Booted boards) targets to LAVA lab.
- Can you let me know where I need to modify current LAVA code to achieve this?
Note:
- This requirement can achieve for "Begalbone" boards using the sring " method: minimal " in "-boot" section. (this will be good if we implement this for "fastboot" targets also)
Remi can correct me here if I'm wrong but I think 'minimal' boot won't work on boards like dragonboard without deployment section. So if the only way to make the board go into fastboot mode is by deleting 'boot' partition, than deployment is required to provide at least boot partition image. I don't know if it would be possible to easily change this feature in LAVA.
milosz
Regards, Koti
On Mon, 30 Mar 2020 at 15:53, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Mon, 30 Mar 2020 at 11:17, koti koti kotisoftwaretest@gmail.com wrote:
Thanks Milosz.
what do you mean by "as we deleted 'boot' partition " in your previous email?
But, I am seeing "-boot" partition for one of the Dragon board YAML file i.e https://staging.validation.linaro.org/scheduler/job/269261/definition#deflin... (line number 72).
I meant boot partition on the board not boot action in LAVA. This means that we don't flash boot partition. In this case 1st stage bootloader always goes into fasboot mode so we can boot the board the same way always: https://staging.validation.linaro.org/scheduler/job/269261#L658
milosz
Regards, Koti
On Fri, 27 Mar 2020 at 19:43, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Fri, 27 Mar 2020 at 13:57, koti koti kotisoftwaretest@gmail.com wrote:
Hi Remi Duraffort,
Thanks for you reply.
- beaglebone: (success)
############# a. Yes. it is working with "minimal" for begalbone. ( I am able to run the test with out deploy and falsh . attached the YAML file which I have used) b. I am fine with minimal for begalbone to run the tests for Provisioned board.
- dragonboard-845c: (still I am facing the issue)
################## a). is any one tried Provision boot (bootee board) with "minimal" method for Dragonboards? b). I am facing the issue to run the health checkup using "minimal" boot method for already provision Dragon series boards. (I am not sure minimal boot is supported for Dragonboard series or not )
In our instance this isn't possible as we deleted 'boot' partition. So the board will go to fasboot by default.
milosz
Please can some let me know your suggestions for "dragonboard" minimal boot for already provision (booted board) board?
Regards, Koti
On Tue, 24 Mar 2020 at 21:04, Rémi Duraffort remi.duraffort@linaro.org wrote:
Hello, LAVA is starting the connection un the boot action. Without a boot action, the connection is not created.
Have you tried using a minimal boot?
Rgds
Le 23 mars 2020 19:45:32 GMT+01:00, koti koti kotisoftwaretest@gmail.com a écrit : > > Hi, > > The issue/error I am facing in results page with out "-boot" section in my YAML file is as follows i.e > > " > lava-dispatcher, installed at version: 2019.12 > start: 0 validate > Start time: 2020-03-23 18:31:11.011685+00:00 (UTC) > validate duration: 0.00 > case: validate > case_id: 339 > definition: lava > result: pass > start: 1 lava-test-interactive-retry (timeout 00:15:00) [common] > start: 1.1 lava-test-interactive (timeout 00:15:00) [common] > Connection closed > end: 1.1 lava-test-interactive (duration 00:00:00) [common] > case: lava-test-interactive > case_id: 340 > definition: lava > duration: 0.00 > extra: ... > level: 1.1 > namespace: common > result: fail > lava-test-interactive-retry failed: 1 of 1 attempts. 'Connection closed' > Connection closed > end: 1 lava-test-interactive-retry (duration 00:00:00) [common] > case: lava-test-interactive-retry > case_id: 341 > definition: lava > duration: 0.00 > extra: ... > level: 1 > namespace: common > result: fail > Cleaning after the job > start: 2.1 power-off (timeout 00:00:10) [common] > end: 2.1 power-off (duration 00:00:00) [common] > case: power-off > case_id: 342 > definition: lava > duration: 0.00 > extra: ... > level: 2.1 > namespace: common > result: pass > start: 2.2 read-feedback (timeout 00:15:00) [common] > end: 2.2 read-feedback (duration 00:00:00) [common] > InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins. > case: job > case_id: 343 > definition: lava > error_msg: Connection closed > error_type: Infrastructure > result: fail > " > > Regards, > Koti > > On Tue, 24 Mar 2020 at 00:13, koti koti kotisoftwaretest@gmail.com wrote: >> >> Hi, >> >> I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml". >> >> But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now) >> >> Please can some one help me for the same? >> >> 1. Basically I am facing the connection issue with out "-boot" section. >> 2. Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file) >> 3. Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section) >> >> >> " >> device_type: beaglebone-black >> job_name: begalbone 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 >> ## reset: false >> ## auto_login: >> ## login_prompt: '.* login:' >> ## username: root >> # prompts: >> # - root@dragonboard-410c:~# >> >> - test: >> interactive: >> - name: reset >> prompts: ["#"] >> script: >> - name: reset >> command: reset >> >> " >> >> Regards, >> Koti
-- Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org
-
koti koti -
Milosz Wasilewski -
Rémi Duraffort