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