Dear CIP friends,

please check below. This is a use case we will meet in a few weeks/months. It is important to see others walking the same route.


-------- Forwarded Message --------
Subject: [Lava-users] OE/Yocto testcase
Date: Mon, 3 Jul 2017 20:19:31 +0300
From: Robert Berger <lava.users.mailinglist@...>
To: Lava-users@...

Hi,

I succeeded in running the example Lava tests[1][2] on a Beagle Bone
Black in my lab.

Now I would like to test a core-image-minimal I built with Yocto and
cooked up something like this[3][4].

The result is unfortunately this[5].

I guess one of the problems I have is this:

lava-test: # ls -l /lava-38/
export SHELL=/bin/sh
/lava-38/bin/lava-test-runner /lava-38/0ls: cannot access '/lava-38/':
No such file or directory
lava-test: # export SHELL=/bin/sh
lava-test: # /lava-38/bin/lava-test-runner /lava-38/0
-sh: /lava-38/bin/lava-test-runner: No such file or directory

Regards,

Robert


[1]
https://validation.linaro.org/static/docs/v2/examples/test-jobs/standard-armmp-ramdisk-bbb.yaml
[2]
https://validation.linaro.org/static/docs/v2/examples/test-jobs/standard-armmp-nfs-bbb.yaml

[3]
https://github.com/RobertBerger/git.linaro.org-lava-team-refactoring/blob/master/bbb-core-image-minimal-1.yaml
[4]
https://github.com/RobertBerger/git.linaro.org-qa-test-definitions/blob/master/openembedded/smoke-tests-basic-core-image-minimal.yaml

[5] https://pastebin.com/14pjxhiN
_______________________________________________
Lava-users mailing list
Lava-users@...
https://lists.linaro.org/mailman/listinfo/lava-users

--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito@...

Hi,

On 2017-07-04 15:18, Agustin Benito Bethencourt wrote:

Dear CIP friends,
please check below. This is a use case we will meet in a few weeks/months. It is important to see others walking the same route.

My simple tests are running now thanks to the help of the nice people from the #linaro-lava chat.

1) Crazy me decided to use upstream u-boot 2017.05 instead of running some ancient version from 2014;)

1.1) which happens to have a different AUTOBOOT_PROMPT than the one Lava expects "Press SPACE to abort autoboot in %d seconds\n" instead of "Hit any key to stop autoboot" so (since) I would like to be able to stay as close as possible to upstream LAVA 2017.06 I patched u-boot[1]. Note that this could be fixed with LAVA as well - interrupt_prompt: {{ interrupt_prompt|default('Hit any key to stop autoboot') }}

1.2) also the SYS_PROMPT of upstream u-boot is different than the one expected by LAVA and again I made a u-boot patch[2]. Note that this could be fixed with LAVA as well - {% set bootloader_prompt = bootloader_prompt|default('U-Boot') %}

2) After some searching it turned out that LAVA set some funny variables in u-boot which made my kernel crash. (Crazy me decided to use a 4.9.x uImage without baked in address).

Adding this:
{% set base_high_limits = false %}
to my bbb03.jinja2 file fixed it.

... obviously ;)

Regards,

Robert

[1] https://github.com/RobertBerger/meta-mainline/blob/pyro-training-v4.9.x/u-boot-wic-bsp/recipes-bsp/u-boot/2017.05/beagle-bone-black/0002-default-AUTOBOOT_PROMPT-for-LAVA.patch
[2] https://github.com/RobertBerger/meta-mainline/blob/pyro-training-v4.9.x/u-boot-wic-bsp/recipes-bsp/u-boot/2017.05/beagle-bone-black/0003-SYS_PROMPT-LAVA-compatible.patch