Hi all,
When I try to run a test in lava , hacking session is not starting .
it is exiting by showing:
Using /lava-18
export SHELL=/bin/sh
# export SHELL=/bin/sh
/lava-18/bin/lava-test-runner /lava-18/0
/lava-18/bin/lava-test-runner /lava-18/0
Test shell timeout: 10s (minimum of the action and connection timeout)
export SHELL=/bin/sh
# /lava-18/bin/lava-test-runner /lava-18/0
Illegal instruction
<LAVA_TEST_RUNNER EXIT>
ok: lava_test_shell seems to have completed
end: 3.1 lava-test-shell (duration 00:00:01) [common]
end: 3 lava-test-retry (duration 00:00:01) [common]
start: 4 finalize (timeout 00:10:00) [common]
start: 4.1 power-off (timeout 00:00:05) [common]
end: 4.1 power-off (duration 00:00:00) [common]
my board linux has busybox init system
Please help me resolve the issue.
I've attached the job log below.
Thanks & Regards,
Manoj
Hi everyone,
I'm currently running CTS tests on imx8mq on Android 9.
My test job is based on Linaro's test definition located here :
https://git.linaro.org/qa/test-definitions.git/tree/automated/android/trade…
I had issue concerning the Java heap size, causing the test to abort and
skip a lot of tests.
So, I cloned this git tree and made modifications in "tradefed.sh" :
export _JAVA_OPTIONS="-Xmx350M"
replaced by :
export _JAVA_OPTIONS="-Xmx700M"
Since this modification, I'm able to run the full CTS 9.
So, I think you should consider modify this script, so other users
can benefit from it.
Best regards,
Axel
Hi all,
In Tftp deploy , How to give new set of u-boot bootargs by modifying device
configuration file?
I've tried by giving:
{% set base_kernel_args = "setenv bootargs console=serial1,115200
console=tty1 root=/dev/ram0 ip=dhcp rootwait" %}
But it is not taking these args.
Please suggest the modifications I have to make.
Thanks and regards,
Manoj
Hi Neil,
When LAVA start container from image for the first time(usually docker run ), if failed, it will bring a zoobie container.
And I found that LAVA did not check whether LAVA run is OK, and has no dead container cleanup method.(maybe I was wrong).
Does LAVA have some method to prevent it or do you think it is necessary?
Best Regards
Li Xiaoming
Hi all,
During send-reboot-commands phase in Health check on my raspberry pi 3
board,
LAVA is trying to match the keyword "The system is going down for reboot
NOW" after sending the reset command "reboot -n" to the DUT.
But the problem is when my board starts Reboot it shows "Started Show
Plymouth Reboot Screen .." , not the same as what LAVA want.
So is there any way to specify the keywords to what it should be("Started
Show Plymouth Reboot Screen" or something) in the corresponding DUTs jinja2
file?
I've attached the reslult log of my test below.
Regards,
Manoj
Hi everyone,
I have some troubles to log in my Web UI. I type the good password and
username and then the website sends me back to the home page. If I type a
wrong password, I get an error message. It does the same thing for all user
accounts. Tried to restart lava services, apache2 but it's still doing the
same thing. No error messages returned in logs.
Best regards,
Axel Le Bourhis
Hi all,
When health check is running on my raspberry pi 3 board , in boot phase it
is
taking default soft reboot commands like reboot , reboot -n , reboot -nf.
which is not working with
U-boot boot type. It is showing unknown command ' reboot' .
How to set soft reboot command manually in test job definition?
Thanks & regards,
Manoj
Hi everyone,
I got an issue using LAVA today. After trying to load a job page, LAVA
crashed returning PROXY ERROR. I tried to restart lava-master, lava-slave
and lava-server-gunicorn services without success. The django.log returns
an error about django tables2, saying it can't find the module. I'm running
LAVA 2018.10.
See attached log for more precision.
Best regards,
Axel Le Bourhis
Ok i'll keep that in mind.
To mailing list : I confirm this solution fixed the issue.
Kind regards,
Axel
On Tue, 6 Nov 2018 at 16:55, Neil Williams <neil.williams(a)linaro.org> wrote:
> Yes, please always include the mailing list in replies. When people do
> search for help in the list archives, it is frustrating to find the
> question without the solution - or even just a confirmation that the
> reply worked.
> On Tue, 6 Nov 2018 at 15:47, Axel Lebourhis <axel.lebourhis(a)linaro.org>
> wrote:
> >
> > Thank you for the clarification. I've been able to fix the problem
> thanks to your help.
> >
> > Just a quick question : should I reply including the mailing list ?
> >
> > Regards,
> > Axel
> >
> > On Tue, 6 Nov 2018 at 16:08, Neil Williams <neil.williams(a)linaro.org>
> wrote:
> >>
> >> On Tue, 6 Nov 2018 at 14:59, Axel Lebourhis <axel.lebourhis(a)linaro.org>
> wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > I just upgraded NXP's installation for DRM team from 2018.4 to
> 2018.10.
> >> > I changed my default LXC folder for storage purpose and when I was at
> 2018.4, there was a constant.py file in
> /usr/lib/python3/dist-packages/lava_dispatcher/utils in order to make LAVA
> know where are located LXC containers.
> >>
> >> Avoid making code changes for these kinds of settings. Constants and
> >> settings can be modified in configuration files. There is no need to
> >> alter anything in /usr/lib/python3/dist-packages/lava* - any change
> >> there will always be undone at the next package upgrade.
> >>
> >>
> https://git.lavasoftware.org/lava/lava/blob/master/etc/dispatcher.yaml#L13
> >>
> >> So on a per-worker basis, you can set the LXC_PATH
> >>
> >> This support is covered under simple administration in the LAVA help:
> >>
> https://master.lavasoftware.org/static/docs/v2/simple-admin.html#lava-server
> >>
> >> In 2018.10 release, this file doesn't exist anymore, so I'd like to
> >> know how I can specify to LAVA the correct path to LXC containers.
> >> >
> >> > Best regards,
> >> > Axel Le Bourhis
> >> >
> >> > _______________________________________________
> >> > Lava-users mailing list
> >> > Lava-users(a)lists.lavasoftware.org
> >> > https://lists.lavasoftware.org/mailman/listinfo/lava-users
> >>
> >>
> >>
> >> --
> >>
> >> Neil Williams
> >> =============
> >> neil.williams(a)linaro.org
> >> http://www.linux.codehelp.co.uk/
>
>
>
> --
>
> Neil Williams
> =============
> neil.williams(a)linaro.org
> http://www.linux.codehelp.co.uk/
>
Hi everyone,
I just upgraded NXP's installation for DRM team from 2018.4 to 2018.10.
I changed my default LXC folder for storage purpose and when I was at
2018.4, there was a constant.py file in
/usr/lib/python3/dist-packages/lava_dispatcher/utils in order to make LAVA
know where are located LXC containers. In 2018.10 release, this file
doesn't exist anymore, so I'd like to know how I can specify to LAVA the
correct path to LXC containers.
Best regards,
Axel Le Bourhis