Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
The actions in the job definition looks as follows (sorry pastebin is blocked by our proxy):
actions: - boot: method: u-boot commands: msd type: uimage auto_login: login_prompt: '(none) login: ' username: root prompts: - 'myiwg20m: # ' timeout: minutes: 2 failure_retry: 5 - test: timeout: minutes: 5 failure_retry: 3 name: kernel-version-singlenode definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: kernel-version-basic description: "check kernel version" run: steps: - lava-test-case linux-INLINE-uname --shell uname -a from: inline name: kernel-version-inline path: inline/kernel-version-basic.yaml
So far LAVA has been successful at powering on the board, interrupting u-boot, sending the u-boot commands, recognizing the boot login prompt and auto-login in. In other words, the boot actions seems to be working fine.
The problem comes with the 'test' action. I have mostly copied the code from the inline example included in the help but I get the following errors: (sorry again for not pasting it on pastebin)
- {"dt": "2017-09-11T05:19:03.602576", "lvl": "target", "msg": "Debian GNU/Linux 8 (none) /dev/ttySC0"} - {"dt": "2017-09-11T05:19:03.605709", "lvl": "debug", "msg": "Matched prompt #6: \(none\) login: "} - {"dt": "2017-09-11T05:19:03.606979", "lvl": "debug", "msg": "Sending username root"} - {"dt": "2017-09-11T05:19:03.608100", "lvl": "debug", "msg": {"sending": "root\n"}} - {"dt": "2017-09-11T05:19:03.864073", "lvl": "target", "msg": "(none) login: root"} - {"dt": "2017-09-11T05:19:03.865475", "lvl": "debug", "msg": "auto-login-action: Wait for prompt ['myiwg20m: # ']. 120 seconds"} - {"dt": "2017-09-11T05:19:03.868416", "lvl": "target", "msg": "root"} - {"dt": "2017-09-11T05:19:03.898283", "lvl": "target", "msg": ""} - {"dt": "2017-09-11T05:19:03.904742", "lvl": "target", "msg": "The programs included with the Debian GNU/Linux system are free software;"} - {"dt": "2017-09-11T05:19:03.911114", "lvl": "target", "msg": "the exact distribution terms for each program are described in the"} - {"dt": "2017-09-11T05:19:03.915433", "lvl": "target", "msg": "individual files in /usr/share/doc/*/copyright."} - {"dt": "2017-09-11T05:19:03.921821", "lvl": "target", "msg": "Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent"} - {"dt": "2017-09-11T05:19:03.923941", "lvl": "target", "msg": "permitted by applicable law."} - {"dt": "2017-09-11T05:19:03.927111", "lvl": "target", "msg": "login[816]: root login on 'ttySC0'"} - {"dt": "2017-09-11T05:19:03.928112", "lvl": "target", "msg": ""} - {"dt": "2017-09-11T05:19:03.933510", "lvl": "target", "msg": "BusyBox v1.22.1 (2017-09-01 01:37:39 UTC) built-in shell (ash)"} - {"dt": "2017-09-11T05:19:03.937734", "lvl": "target", "msg": "Enter 'help' for a list of built-in commands."} - {"dt": "2017-09-11T05:19:03.938979", "lvl": "debug", "msg": "Setting shell prompt(s) to ['myiwg20m: # ', 'lava-test: # ']"} - {"dt": "2017-09-11T05:19:03.939504", "lvl": "debug", "msg": {"sending": "export PS1="lava-test: # "\n"}} - {"dt": "2017-09-11T05:19:05.310766", "lvl": "target", "msg": "myiwg20m: # [6nexport PS1=\"lava-test: # \""} - {"dt": "2017-09-11T05:19:05.311542", "lvl": "debug", "msg": "auto-login-action duration: 3.93"} - {"dt": "2017-09-11T05:19:05.312062", "lvl": "results", "msg": {"case": "auto-login-action", "definition": "lava", "duration": !!float "3.929234027862549", "extra": !!python/object/apply:collections.OrderedDict [[["success", "No kernel warnings or errors detected."]]], "level": "1.5.5", "result": "pass"}} - {"dt": "2017-09-11T05:19:05.313427", "lvl": "debug", "msg": "start: 1.5.6 expect-shell-connection (max 120s)"} - {"dt": "2017-09-11T05:19:05.313967", "lvl": "debug", "msg": "expect-shell-connection: Waiting for prompt myiwg20m: # , lava-test: # "} - {"dt": "2017-09-11T05:19:05.314522", "lvl": "debug", "msg": "expect-shell-connection: Wait for prompt ['myiwg20m: # ', 'lava-test: # ']. 300 seconds"} - {"dt": "2017-09-11T05:19:05.315249", "lvl": "target", "msg": "export PS1=\"lava-test: # \""} - {"dt": "2017-09-11T05:19:05.315963", "lvl": "debug", "msg": "expect-shell-connection duration: 0.00"} - {"dt": "2017-09-11T05:19:05.316851", "lvl": "debug", "msg": "start: 1.5.7 export-device-env (max 120s)"} - {"dt": "2017-09-11T05:19:05.317390", "lvl": "debug", "msg": "export-device-env duration: 0.00"} - {"dt": "2017-09-11T05:19:05.317890", "lvl": "debug", "msg": "Setting default test shell prompt"} - {"dt": "2017-09-11T05:19:05.318373", "lvl": "debug", "msg": ["myiwg20m: # ", "lava-test: # "]} - {"dt": "2017-09-11T05:19:05.318902", "lvl": "debug", "msg": "uboot-retry: Wait for prompt ['myiwg20m: # ', 'lava-test: # ']. 240 seconds"} - {"dt": "2017-09-11T05:19:05.339032", "lvl": "debug", "msg": "uboot-retry duration: 8.48"} - {"dt": "2017-09-11T05:19:05.339643", "lvl": "info", "msg": "uboot-action duration: 8.50"} - {"dt": "2017-09-11T05:19:05.340189", "lvl": "info", "msg": "start: 2 lava-test-retry (max 300s)"} - {"dt": "2017-09-11T05:19:05.340724", "lvl": "debug", "msg": "start: 2.1 lava-test-shell (max 300s)"} - {"dt": "2017-09-11T05:19:05.341253", "lvl": "info", "msg": "Executing test definitions using ShellSession"} - {"dt": "2017-09-11T05:19:05.341753", "lvl": "debug", "msg": {"sending": "#\n"}} - {"dt": "2017-09-11T05:19:05.442940", "lvl": "target", "msg": "lava-test: # [6n#"} - {"dt": "2017-09-11T05:19:05.443483", "lvl": "debug", "msg": "lava-test-shell: Wait for prompt ['myiwg20m: # ', 'lava-test: # ']. 300 seconds"} - {"dt": "2017-09-11T05:19:05.446189", "lvl": "target", "msg": "#"} - {"dt": "2017-09-11T05:19:05.469109", "lvl": "exception", "msg": "Traceback (most recent call last):\n File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 290, in run_actions\n new_connection = action.run(connection, args)\n File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/test/shell.py", line 243, in run\n for running in xrange(stage + 1):\nTypeError: unsupported operand type(s) for +: 'NoneType' and 'int'\n"} - {"dt": "2017-09-11T05:19:05.470260", "lvl": "debug", "msg": "start: 3.1 power_off (max 5s)"} - {"dt": "2017-09-11T05:19:05.470796", "lvl": "info", "msg": "nice curl http://admin:<omitted>@192.168.11.68/set.cmd?cmd=setpower+p61=0"} - {"dt": "2017-09-11T05:19:05.534407", "lvl": "debug", "msg": !!python/unicode "command output % Total % Received % Xferd Average Speed Time Time Time Current\n Dload Upload Total Spent Left Speed\n\r 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0\r100 20 0 20 0 0 371 0 --:--:-- --:--:-- --:--:-- 377\n<html>p61=0</html>\r\n"} - {"dt": "2017-09-11T05:19:05.535945", "lvl": "debug", "msg": "power_off duration: 0.07"} - {"dt": "2017-09-11T05:19:05.536462", "lvl": "results", "msg": {"case": "power_off", "definition": "lava", "duration": !!float "0.06516695022583008", "extra": !!python/object/apply:collections.OrderedDict [[["status", "success"]]], "level": "3.1", "result": "pass"}} - {"dt": "2017-09-11T05:19:05.644487", "lvl": "error", "msg": "Status: Incomplete\nErrors ['Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 290, in run_actions new_connection = action.run(connection, args) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/test/shell.py", line 243, in run for running in xrange(stage + 1):TypeError: unsupported operand type(s) for +: \'NoneType\' and \'int\'', 'Incomplete']"} - {"dt": "2017-09-11T05:19:05.646006", "lvl": "exception", "msg": "Traceback (most recent call last):\n File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 290, in run_actions\n new_connection = action.run(connection, args)\n File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/logical.py", line 57, in run\n new_connection = self.internal_pipeline.run_actions(connection)\n File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 302, in run_actions\n raise RuntimeError(action.errors)\nRuntimeError: ['Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 290, in run_actions new_connection = action.run(connection, args) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/test/shell.py", line 243, in run for running in xrange(stage + 1):TypeError: unsupported operand type(s) for +: \'NoneType\' and \'int\'']\n"} - {"dt": "2017-09-11T05:19:05.647870", "lvl": "debug", "msg": "start: 3.1 power_off (max 5s)"} - {"dt": "2017-09-11T05:19:05.648393", "lvl": "debug", "msg": "power_off duration: 0.00"} - {"dt": "2017-09-11T05:19:05.648864", "lvl": "results", "msg": {"case": "power_off", "definition": "lava", "duration": !!float "3.0994415283203125e-05", "extra": !!python/object/apply:collections.OrderedDict [[["status", "success"], ["duration", !!float "0.06516695022583008"], ["connection-timeout", !!float "300.0"], ["timeout", !!float "5.0"], ["level", "3.1"]]], "level": "3.1", "result": "pass"}} - {"dt": "2017-09-11T05:19:05.650619", "lvl": "error", "msg": "status: ['Incomplete']"}
Any hint of what's going on? # One thing I don't understand is that even though I have set the "prompts" variable on the job, LAVA seems to force it to become "lava-test: #".
Thanks, Daniel
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
The actions in the job definition looks as follows (sorry pastebin is blocked by our proxy)
Please use attachments instead of putting the content inline. Extracting the test definition to reproduce elsewhere is prone to errors once it has been mangled as inline text. Besides, pastebins are best used with IRC, not email as the bin itself usually has an expiry and then the link goes dead when someone searches for your question in the mailing list archive. Attachments will be preserved in the archive.
You can find most of what you need by following the documentation and standard test job examples:
https://staging.validation.linaro.org/scheduler/job/179047
Always go back to a known working test job to see what might be going on.
This job uses a similar inline test definition: https://staging.validation.linaro.org/scheduler/job/188480
actions:
- boot: method: u-boot commands: msd type: uimage auto_login: login_prompt: '(none) login: ' username: root prompts: - 'myiwg20m: # ' timeout: minutes: 2 failure_retry: 5
- test: timeout: minutes: 5 failure_retry: 3 name: kernel-version-singlenode definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: kernel-version-basic description: "check kernel version" run: steps: - lava-test-case linux-INLINE-uname --shell uname -a from: inline name: kernel-version-inline path: inline/kernel-version-basic.yaml
So far LAVA has been successful at powering on the board, interrupting u-boot, sending the u-boot commands, recognizing the boot login prompt and auto-login in. In other words, the boot actions seems to be working fine.
The problem comes with the 'test' action. I have mostly copied the code from the inline example included in the help but I get the following errors: (sorry again for not pasting it on pastebin)
Any hint of what's going on? # One thing I don't understand is that even though I have set the "prompts" variable on the job, LAVA seems to force it to become "lava-test: #".
You have specified a prompt to be matched at the end of the boot phase. LAVA specifies what prompt is used from then on.
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
The actions in the job definition looks as follows (sorry pastebin is blocked by our proxy)
Please use attachments instead of putting the content inline. Extracting the test definition to reproduce elsewhere is prone to errors once it has been mangled as inline text. Besides, pastebins are best used with IRC, not email as the bin itself usually has an expiry and then the link goes dead when someone searches for your question in the mailing list archive. Attachments will be preserved in the archive.
Oh OK, that will be easier for me. Thanks.
You can find most of what you need by following the documentation and standard test job examples:
https://staging.validation.linaro.org/scheduler/job/179047
Always go back to a known working test job to see what might be going on.
This job uses a similar inline test definition: https://staging.validation.linaro.org/scheduler/job/188480
actions:
- boot: method: u-boot commands: msd type: uimage auto_login: login_prompt: '(none) login: ' username: root prompts: - 'myiwg20m: # ' timeout: minutes: 2 failure_retry: 5
- test: timeout: minutes: 5 failure_retry: 3 name: kernel-version-singlenode definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: kernel-version-basic description: "check kernel version" run: steps: - lava-test-case linux-INLINE-uname --shell uname -a from: inline name: kernel-version-inline path: inline/kernel-version-basic.yaml
So far LAVA has been successful at powering on the board, interrupting u-boot, sending the u-boot commands, recognizing the boot login prompt and auto-login in. In other words, the boot actions seems to be working fine.
The problem comes with the 'test' action. I have mostly copied the code from the inline example included in the help but I get the following errors: (sorry again for not pasting it on pastebin)
Any hint of what's going on? # One thing I don't understand is that even though I have set the "prompts" variable on the job, LAVA seems to force it to become
"lava-test: #".
You have specified a prompt to be matched at the end of the boot phase. LAVA specifies what prompt is used from then on.
OK, thanks for the explanation.
Regards, Daniel
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Robert
[1] https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
Thanks, Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
Thanks, Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi,
I have spent a few days learning LAVA with QEMU and the Beagle Bone black. Now, I'm trying to setup a Renesas iwg20m board but I have some strange problem. # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Thanks, Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Monday, September 11, 2017 3:23 PM
On 11 September 2017 at 07:06, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote: > Hi, > > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. > Now, I'm trying to setup a Renesas iwg20m board but I have some strange > problem. > # I'm using LAVA v2016.12.
Updates are available - you should follow the LAVA documentation for the LAVA repositories and upgrade.
https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On 12 September 2017 at 08:50, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Such a system can only be booted, it cannot operate a Lava Test Shell because there is no way to get the test shell onto the device without a deploy.
There is support for primary connections using SSH https://validation.linaro.org/static/docs/v2/dispatcher-design.html#primary-...
See: Problems with simplistic testing in the documentation. https://validation.linaro.org/static/docs/v2/simple-admin.html#problems-with...
Thanks, Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
Hi Neil,
Thanks for your quick reply.
> -----Original Message----- > From: Neil Williams [mailto:neil.williams@linaro.org] > Sent: Monday, September 11, 2017 3:23 PM > > On 11 September 2017 at 07:06, Daniel Sangorrin > daniel.sangorrin@toshiba.co.jp wrote: > > Hi, > > > > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. > > Now, I'm trying to setup a Renesas iwg20m board but I have some strange > > problem. > > # I'm using LAVA v2016.12. > > Updates are available - you should follow the LAVA documentation for > the LAVA repositories and upgrade. > > https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht...
Thanks, I will try with the 2017.9 version then.
Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:58 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:50, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Such a system can only be booted, it cannot operate a Lava Test Shell because there is no way to get the test shell onto the device without a deploy.
There is support for primary connections using SSH https://validation.linaro.org/static/docs/v2/dispatcher-design.html#primary-...
See: Problems with simplistic testing in the documentation. https://validation.linaro.org/static/docs/v2/simple-admin.html#problems-with...
Thanks a lot Neil. # I'm not against deployment, I just wanted to prepare the environment step by step.
The primary connection could be a good solution but it looks like I wouldn't be able to use the PDU, or the autologin features from the u-boot action through the serial port. I will implement the deploy action instead.
By the way, when you talk about "test shell" I am assuming that you mean a shell script or binary that is copied into the target filesystem and executed. Is that correct? My filesystem is very minimal: basically busybox using the ash shell.
I am checking the requirements here, do you think there will be a problem with that? https://validation.linaro.org/static/docs/v2/pipeline-admin.html https://validation.linaro.org/static/docs/v2/development-intro.html
Thanks Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall Sent: Monday, September 11, 2017 4:47 PM To: 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
"Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes:
> Hi Neil, > > Thanks for your quick reply. > >> -----Original Message----- >> From: Neil Williams [mailto:neil.williams@linaro.org] >> Sent: Monday, September 11, 2017 3:23 PM >> >> On 11 September 2017 at 07:06, Daniel Sangorrin >> daniel.sangorrin@toshiba.co.jp wrote: >> > Hi, >> > >> > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. >> > Now, I'm trying to setup a Renesas iwg20m board but I have some strange >> > problem. >> > # I'm using LAVA v2016.12. >> >> Updates are available - you should follow the LAVA documentation for >> the LAVA repositories and upgrade. >> >> https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht... > > Thanks, I will try with the 2017.9 version then. > Daniel
If you're doing the test within b@d [1] you should look at my https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes branch which has various fixes for our use of lava 2017-7, once that branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
On 12 September 2017 at 09:25, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:58 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:50, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Such a system can only be booted, it cannot operate a Lava Test Shell because there is no way to get the test shell onto the device without a deploy.
There is support for primary connections using SSH https://validation.linaro.org/static/docs/v2/dispatcher-design.html#primary-...
See: Problems with simplistic testing in the documentation. https://validation.linaro.org/static/docs/v2/simple-admin.html#problems-with...
Thanks a lot Neil. # I'm not against deployment, I just wanted to prepare the environment step by step.
The primary connection could be a good solution but it looks like I wouldn't be able to use the PDU, or the autologin features from the u-boot action through the serial port. I will implement the deploy action instead.
By the way, when you talk about "test shell" I am assuming that you mean a shell script or binary that is copied into the target filesystem and executed. Is that correct? My filesystem is very minimal: basically busybox using the ash shell.
"test shell" == Lava Test Shell as defined by the test action block. This relies on POSIX behaviour where the automation drives scripts installed onto the system to execute the test operations themselves.
To handle busybox ash compatibility, just set the Operating System as Open Embedded.
actions: - deploy: # ... rest of the deploy os: oe
https://validation.linaro.org/static/docs/v2/actions-deploy.html#index-18
I am checking the requirements here, do you think there will be a problem with that? https://validation.linaro.org/static/docs/v2/pipeline-admin.html https://validation.linaro.org/static/docs/v2/development-intro.html
Thanks Daniel
-----Original Message----- From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin Sent: Monday, September 11, 2017 5:16 PM To: 'Robert Marshall'; 'Lava Users Mailman list' Subject: Re: [Lava-users] Help running an inline test
> -----Original Message----- > From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall > Sent: Monday, September 11, 2017 4:47 PM > To: 'Lava Users Mailman list' > Subject: Re: [Lava-users] Help running an inline test > > "Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes: > > > Hi Neil, > > > > Thanks for your quick reply. > > > >> -----Original Message----- > >> From: Neil Williams [mailto:neil.williams@linaro.org] > >> Sent: Monday, September 11, 2017 3:23 PM > >> > >> On 11 September 2017 at 07:06, Daniel Sangorrin > >> daniel.sangorrin@toshiba.co.jp wrote: > >> > Hi, > >> > > >> > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. > >> > Now, I'm trying to setup a Renesas iwg20m board but I have some strange > >> > problem. > >> > # I'm using LAVA v2016.12. > >> > >> Updates are available - you should follow the LAVA documentation for > >> the LAVA repositories and upgrade. > >> > >> https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht... > > > > Thanks, I will try with the 2017.9 version then. > > > Daniel > > If you're doing the test within b@d [1] you should look at my > https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes > branch which has various fixes for our use of lava 2017-7, once that > branch is merged - soon now! - it should 'just work'
Wow Robert, just in time! Thanks.
Daniel
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
Hi Neil,
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 5:49 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 09:25, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:58 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:50, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Hi Neil,
Thanks for your reply.
-----Original Message----- From: Neil Williams [mailto:neil.williams@linaro.org] Sent: Tuesday, September 12, 2017 4:16 PM To: Daniel Sangorrin Cc: Robert Marshall; Lava Users Mailman list Subject: Re: [Lava-users] Help running an inline test
On 12 September 2017 at 08:10, Daniel Sangorrin daniel.sangorrin@toshiba.co.jp wrote:
Robert, Neil:
I managed to prepare a 2017.7 environment. The boot action still works fine. The test action still fails, but in a more 'sane' way I would say. There are strange things like 'None', no lava-test-runner, etc.. Please check the log attached.
You haven't specified a deploy step, so there is no test shell created. Boot just does the boot - to deploy the test environment there must be a deploy action.
As far as I understand, the deployment action occurs before the boot action and consists of preparing a kernel/filesystem in some media (e.g.: as a network filesystem). Ref: https://validation.linaro.org/static/docs/v2/actions-deploy.html
For now, I wanted to run my tests with the kernel and filesystem that is already installed on the Flash memory. Is this impossible with LAVA?
Such a system can only be booted, it cannot operate a Lava Test Shell because there is no way to get the test shell onto the device without a deploy.
There is support for primary connections using SSH https://validation.linaro.org/static/docs/v2/dispatcher-design.html#primary-...
See: Problems with simplistic testing in the documentation. https://validation.linaro.org/static/docs/v2/simple-admin.html#problems-with...
Thanks a lot Neil. # I'm not against deployment, I just wanted to prepare the environment step by step.
The primary connection could be a good solution but it looks like I wouldn't be able to use the PDU, or the autologin features from the u-boot action through the serial port. I will implement the deploy action instead.
By the way, when you talk about "test shell" I am assuming that you mean a shell script or binary that is copied into the target filesystem and executed. Is that correct? My filesystem is very minimal: basically busybox using the ash shell.
"test shell" == Lava Test Shell as defined by the test action block. This relies on POSIX behaviour where the automation drives scripts installed onto the system to execute the test operations themselves.
To handle busybox ash compatibility, just set the Operating System as Open Embedded.
actions:
- deploy: # ... rest of the deploy os: oe
https://validation.linaro.org/static/docs/v2/actions-deploy.html#index-18
Sorry, it took me a while but I finally got it working.
I met several problems. Some of them were a matter of overriding variables. For example, I cannot use dhcp for the board so I had to change uboot_ipaddr_cmd and base_ip_args.
There was one variable (SERVER_IP) I couldn't override, so I had to modify base-uboot.jinja2 for it.
my jinja2: {% set uboot_serverip = '192.168.1.66' %}
base-uboot.jinja2 # vi /etc/lava-server/dispatcher-config/device-types/base-uboot.jinja2 {% set base_uboot_tftp_bootcmd = uboot_tftp_bootcmd|default( " - setenv bootcmd '" + uboot_ipaddr_cmd|default('dhcp') + "; setenv serverip " + uboot_serverip|default('{SERVER_IP}') + "; run loadkernel; run loadinitrd; " + run_load_fdt + uboot_bootx_cmd|default('{BOOTX}') + "' - run bootcmd") -%}
Note: I tried modifying LAVA_SERVER_IP and LAVA_NETWORK_IFACE in /etc/lava-dispatcher/lava-dispatcher.conf as well but it didn't work.
If you consider it useful, please consider including it in the mainstream code.
Thanks for your help, Daniel
> -----Original Message----- > From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Daniel Sangorrin > Sent: Monday, September 11, 2017 5:16 PM > To: 'Robert Marshall'; 'Lava Users Mailman list' > Subject: Re: [Lava-users] Help running an inline test > > > -----Original Message----- > > From: Lava-users [mailto:lava-users-bounces@lists.linaro.org] On Behalf Of Robert Marshall > > Sent: Monday, September 11, 2017 4:47 PM > > To: 'Lava Users Mailman list' > > Subject: Re: [Lava-users] Help running an inline test > > > > "Daniel Sangorrin" daniel.sangorrin@toshiba.co.jp writes: > > > > > Hi Neil, > > > > > > Thanks for your quick reply. > > > > > >> -----Original Message----- > > >> From: Neil Williams [mailto:neil.williams@linaro.org] > > >> Sent: Monday, September 11, 2017 3:23 PM > > >> > > >> On 11 September 2017 at 07:06, Daniel Sangorrin > > >> daniel.sangorrin@toshiba.co.jp wrote: > > >> > Hi, > > >> > > > >> > I have spent a few days learning LAVA with QEMU and the Beagle Bone black. > > >> > Now, I'm trying to setup a Renesas iwg20m board but I have some strange > > >> > problem. > > >> > # I'm using LAVA v2016.12. > > >> > > >> Updates are available - you should follow the LAVA documentation for > > >> the LAVA repositories and upgrade. > > >> > > >> https://staging.validation.linaro.org/static/docs/v2/installing_on_debian.ht... > > > > > > Thanks, I will try with the 2017.9 version then. > > > > > Daniel > > > > If you're doing the test within b@d [1] you should look at my > > https://gitlab.com/rajm/board-at-desk-single-dev/tree/lava2017-fixes > > branch which has various fixes for our use of lava 2017-7, once that > > branch is merged - soon now! - it should 'just work' > > Wow Robert, just in time! Thanks. > > Daniel > > > _______________________________________________ > Lava-users mailing list > Lava-users@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/lava-users
Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
-
Daniel Sangorrin -
Neil Williams -
Robert Marshall