Hi, LAVA Team!
I'm trying to add my new device.
It must be flashed by fastboot.
To turn device into fastboot mode, I need to write "reboot bootloader" via
serial connection.
I have tried
set soft_reboot_command = ['reboot bootloader']
and received error message
lava-lxc protocol: FAILED executing 'lxc-attach -n lxc-hikey-test-4 -- adb
reboot bootloader'
Ilya
Hi,
we have a LAVA test setup working for some time. Automated pipelines are
running tests on different devices in parallel.
After updating to version 2018.10+stretch and changing to in-line job
definitions we started to get some sporadic errors.
The error message shows up after jobs are submitted and the return from the
submission is then used to ask for server job details:
res = lava_server.submit_job(lava_test_job_description)
for entry in res:
job_details = lavasrv.job_details(entry)
...
Resulting in the following error:
lib/python3.5/site-packages/lavac/server.py", line 272, in job_details
raise get_server_error(error, job_id)
lavac.server.NoSuchJob: No such job: 68271.0
Trying to access LAVA WebUI using the jobid (68271.0):
500 Internal Server Error
Reverse for 'lava.scheduler.job.detail' with arguments '('',)' not found. 1
pattern(s) tried: ['scheduler/job/(?P<pk>[0-9]+|[0-9]+\\.[0-9]+)$']
Can you give me a hint about this error?
Thanks!
Hi Milosz,
I am using the Raspberry Pi 3 B+ board as a real target. It has AOSP Pie 9 on it and runs.
I would be interested now, to see like you said if I could run CTS,VTS on the board and omit deploy section.
What should I put in the boot section as method:
Would be the same fastboot or another method? I ask because the board is connected to LAN (and not over USB).
Is it ok just to omit deploy section?
In other words how would Lava know to access the board on ADB over its IP. Where should I set this info?
Example section (Milosz CTS&VTS example):
https://pastebin.com/hBn0pq6U
Hi Lava Users,
I have decided to continue using a real device: a Raspberry Pi 3 B+.
Because I have an iso with Android 9 Pie, to flash the board I want to use
deploy:
to: iso-installer
The question I'm having is:
Is it possible to use this mode to flash the board with ADB via Wifi?
(The board, I connected wifi to our router and I am able to connect with adb using wifi)
(The board does not have USB/OTG interface so the only option is to use ADB on wifi.)
What I try to achieve is deploy the image I have - iso one (flash), with adb using wifi, and run as tests CTS and VTS.
george
-----Original Message-----
From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org>
Sent: Wednesday, August 21, 2019 11:27 AM
To: George Nistor <george.n(a)l4b-software.com>
Cc: lava-users(a)lists.lavasoftware.org
Subject: Re: [Lava-users] old comercial phones supported by Lava
On Wed, 21 Aug 2019 at 08:00, George Nistor <george.n(a)l4b-software.com> wrote:
>
> Hi,
>
> But I do not understand exactly for example if I can use a Nexus5x; the device is in the list of supported devices Steve McIntyre sent me.
> Milosz Wasilewski said I cannot use it with Lava due to the lack of possibility to force power cycle on them (via serial interface - USB).
>
our current use case doesn't require power cycling the device. It uses the same OS build and tests are executed in chroot environment. This is pretty specific setup for the use case (doesn't require changing kernel).
> To be able to use it requires hw modification of the device?
yes, you need to be able to forcibly power cycle the device. With battery inside the phone this isn't possible, so you have to remove battery and replace it with power supply you can turn off.
>
> What we want to have for the moment is a real device (ex, Nexus 5) on which to run Tradef with Lava.
What is your use case? Are you testing tradefed (ex CTS) changes and stick with the same Android build or do you test Android (kernel, libraries, etc) changes? If it's the former you might be lucky and use existing nexus5 support. If you want to test android using CTS, HW modification is necessary.
milosz
>
> george
>
> -----Original Message-----
> From: Steve McIntyre <steve.mcintyre(a)linaro.org>
> Sent: Tuesday, August 20, 2019 8:51 PM
> To: George Nistor <george.n(a)l4b-software.com>
> Cc: lava-users(a)lists.lavasoftware.org
> Subject: Re: [Lava-users] real devices supported by Lava by default
>
> Hi George,
>
> On Tue, Aug 20, 2019 at 12:54:21PM +0000, George Nistor wrote:
> >
> >I have a question regarding real devices supported by Linaro Lava.
> >
> >Besides these dev boards I found here :
> >https://validation.linaro.org/static/
> >docs/v2/standard-armmp-ramdisk-bbb.html#standard-known-devices
> >
> >Are any other real devices supported in Lava by default? (any
> >commercial phone for example Nexus 5)?
>
> There's a huge set of supported devices. If you don't already have
> LAVA installed, the easiest way to find the list is by looking at the
> set of device type configurations at
>
>
> https://git.lavasoftware.org/lava/lava/tree/master/etc/dispatcher-conf
> ig/device-types
>
> Cheers,
> --
> Steve McIntyre steve.mcintyre(a)linaro.org
> <http://www.linaro.org/> Linaro.org | Open source software for ARM
> SoCs
>
>
> _______________________________________________
> Lava-users mailing list
> Lava-users(a)lists.lavasoftware.org
> https://lists.lavasoftware.org/mailman/listinfo/lava-users
It appears always, right from the start of the job.
lxc is installed on my dispatcher.
Job description
https://pastebin.com/5g15YrWy
DUT description:
https://pastebin.com/bTKdaM5i
I know dut description is not full, but I want do step by step, firstly run
lxc on device.
Maybe you can give some advice about DUT desc.
I'm using fastboot flash for few partitions after that fastboot reboot
flash_cmds_order - it is order of flashing partition
fastboot_sequence - what is it?
Do you have some manual about this parameters description, cause have not
found it on your website.
And one more question, lxc deployed on dispatcher, right?
Best regards,
Ilya Fedusiv
Hi,
But I do not understand exactly for example if I can use a Nexus5x; the device is in the list of supported devices Steve McIntyre sent me.
Milosz Wasilewski said I cannot use it with Lava due to the lack of possibility to force power cycle on them (via serial interface - USB).
To be able to use it requires hw modification of the device?
What we want to have for the moment is a real device (ex, Nexus 5) on which to run Tradef with Lava.
george
-----Original Message-----
From: Steve McIntyre <steve.mcintyre(a)linaro.org>
Sent: Tuesday, August 20, 2019 8:51 PM
To: George Nistor <george.n(a)l4b-software.com>
Cc: lava-users(a)lists.lavasoftware.org
Subject: Re: [Lava-users] real devices supported by Lava by default
Hi George,
On Tue, Aug 20, 2019 at 12:54:21PM +0000, George Nistor wrote:
>
>I have a question regarding real devices supported by Linaro Lava.
>
>Besides these dev boards I found here :
>https://validation.linaro.org/static/
>docs/v2/standard-armmp-ramdisk-bbb.html#standard-known-devices
>
>Are any other real devices supported in Lava by default? (any
>commercial phone for example Nexus 5)?
There's a huge set of supported devices. If you don't already have LAVA installed, the easiest way to find the list is by looking at the set of device type configurations at
https://git.lavasoftware.org/lava/lava/tree/master/etc/dispatcher-config/de…
Cheers,
--
Steve McIntyre steve.mcintyre(a)linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
Hello Lava users,
I have a question regarding real devices supported by Linaro Lava.
Besides these dev boards I found here : https://validation.linaro.org/static/docs/v2/standard-armmp-ramdisk-bbb.htm…
Are any other real devices supported in Lava by default? (any commercial phone for example Nexus 5)?
george
Hello, LAVA Team!
I'm trying to implement own device description. Run with standard fastboot
singlenode with lxc.
And received error:
lava-dispatcher, installed at version: 2019.03+stretchstart: 0 validateStart
time: 2019-08-19 15:01:03.367020+00:00 (UTC)validate duration: 0.00result:
fail
definition: lava
case: validate
<http://localhost:10080/results/testcase/8>Cleaning after the jobRoot tmp
directory removed at /var/lib/lava/dispatcher/tmp/2InfrastructureError: The
Infrastructure is not working correctly. Please report this error to LAVA
admins.error_msg: Cannot find command 'lxc-start' in $PATH
error_type: Infrastructure
result: fail
definition: lava
case: job <http://localhost:10080/results/testcase/9>
Best regards, Ilya Fedusiv
Anyone can help to provide some suggestion about following kernelci
integration problem:
We setup one kernelci in our infrastructure and deploy LAVA master and
slave as well. kernelci can support build, LAVA can also work to run
automation test. We use the lava-boot-v2.sh (jenkins job in kernelci-core
project ) to trigger lava test, but we found that both boot report or test
report can't be synchronized to kernelci dashboard. It will report json
format error, may I know whether we need follow boot schema or test schema
defined in kernelci (https://api.kernelci.org/schema-boot.html and
https://api.kernelci.org/schema-test.html) to create one report, then
trigger LAVA callback function to post one request?
Following is callback definition in
https://github.com/kernelci/kernelci-core/blob/master/templates/base/kernel….
Do we need customize this callback if we want to post request for boot and
test result? Any suggestion will be appreciated.
{%- if callback %}
notify:
criteria:
status: finished
callback:
{%- if callback_type == 'custom' %}
url: {{ callback_url }}
{%- else %}
url: {{ callback_url }}/callback/{{ callback_name }}?lab_name={{ lab_name
}}&status={STATUS}&status_string={STATUS_STRING}
{%- endif %}
method: POST
dataset: {{ callback_dataset }}
token: {{ callback }}
content-type: json
{% endif %}
Hello LAVA Team!
Found in manual about adding new device, at begin better to write to you.
Device is: aarch64
Flashing via fastboot (have partition table list)
Device has serial debug connection.
For flashing using next commands:
fastboot flash <partition name> <path>
...
...
fastboot set_active a
fastboot reboot
To turn device into fastboot mode need to enter command in serial debug.
Best regards,
Ilya Fedusiv
