Hello Lava users,
Do you have any example or advice to share on a way to measure boot time using Lava?
Let's say that I use u-boot, a minimal boot for a device running Linux, and I want to measure the time spent between Power On (pdu-reboot e.g) and Linux prompt.
Best regards,
Denis
Hi Team,
Do you know how to fix below issue when I trigger one LAVA job on LAVA V2 server?
Traceback (most recent call last):
File "trigger.py", line 184, in <module>
main(sys.argv[1:])
File "trigger.py", line 174, in main
lava_bn = lava_server.submit_job(lava_jd)
* File "trigger.py", line 52, in submit_job*
return self._server.scheduler.submit_job(job_data)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1092, in _call_
return self._send(self._name, args)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1432, in __request
verbose=self.__verbose
File "/usr/lib/python3.5/xmlrpc/client.py", line 1134, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1150, in single_request
return self.parse_response(resp)
File "/usr/lib/python3.5/xmlrpc/client.py", line 1322, in parse_response
return u.close()
File "/usr/lib/python3.5/xmlrpc/client.py", line 655, in close
raise Fault(**self._stack[0])
xmlrpc.client.Fault: <Fault -32603: 'Internal Server Error (contact server administrator for details): relation "lava_scheduler_app_build" does not exist\nLINE 1: ...number", "lava_scheduler_app_build"."branch" FROM "lava_sche...\n
Best Regards
Zhanghui Yuan
OTC Production Kernel Integration Test
Refer to https://validation.linaro.org/scheduler/job/1890179,I had run a test case in real board successfully
The nfsrootfs image is too big ,it took too many download time in every test. So I put kernel nfs and dtb image files on tftp server, then delete deploy action and add a few boot action commands to specify tftp addr... The parameters(login_prompt&usrname&prompts) of the boot action are same with success version(has deploy action):
...
- boot:
connection: telnet localhost 7000
method: u-boot
##note the fellow commands lines is new added,the success version(has deploy action)that commands line is only "commands:nfs"
commands:
- setenv serverip 192.168.1.5
- tftp 0x8...0000 zImage_arm_1
- tftp 0x4...0000 dtb_arm_1
- setenv nfsroot rootfs_1
- boot
auto_login:
login_prompt: "arm login:"
username: root
prompts:
- root@arm:~#
timeout:
minutes: 3
...
After job submited,the log display that kernel startup and rootfs mount ok, but it always failed at login error.
error log lines:
err info:lava-test-shell: Wait for prompt ['root@arm:~#', 'Login incorrect', 'Login timed out', 'lava-test: # '] (timeout 00:05:00)
Nothing to run. Maybe the 'deploy' stage is missing, otherwise this is a bug which should be reported.
In addition， does the uboot prompts(u-boot=>) no need to describe in boot action section? In other words the prompts auto_login is only described for kernel?
Lava document contains content of how to add simple qemu devices and how to write its job define. But it does not contain how to add real machine device and how to write its test job like uboot image and linex kernel specifications,etc.
Is there any document on how to step by step to build real machine testing?
I have an important question neet to clarify.
For exampe when I manunl boot kernel by uboot, once board startup and into uboot interactive environment, I manual input follow command as:
setenv image zImage_mx....
setenv nfsroot /rootfs/rootfs001....
...
if I whan to dispatcher to boot the board kernel, I need write job definition,Is it written like this?:
boot:
# list of boot methods which this device supports.
methods:
- u-boot:
parameters:
...
oe:
commands:
- setenv image zImage_mx....
- setenv nfsroot /rootfs/rootfs001....
Through web admin interface,I had added qemu device,and web devices list can display qemu device. It seems qemu device had startuped ok.
We know that if linux device startup successfully it must included uboot and kernel image. But where are the uboot image and kernel image of qemu ? In which config file is described the path of uboot and kernel image?
I am building lava test system and currently add new addvice.
According to document than step of "Adding a dictionary to the first QEMU device",follow config items neet to write to .jianja2 file.
{% extends 'qemu.jinja2' %}
{% set mac_addr = '52:54:00:12:34:59' %}
{% set memory = '1024' %}
Which file is to be writen to above config items ?does its directory path must be at path:/etc/lava-server/dispatcher-config/device-types/?
How to make these items take effect immediatly?which command to use to take effect above config items? the document is not said.
Hi,
I using LAVA version 2018.5-post1 to boot from USB thumb drive using Yocto Project's image. The LAVA job definition contain 2 deployments and booting actions. The first deployment is deploy the image to NFS server and boot using TFTP method. The second deployment is download an image to DUT and flash it on USB thumb drive. The DUT was able to download the image however it failed at flash to thumb drive. I'm use dd command as my tool to flash the image. Below is an example on lava-job definition and output message from LAVA. Due to this issue, I unable to boot from USB thumb drive. Did anyone know what is the problem?
Snipped code from lava-job definition to deploy on USB thumb drive
- deploy:
timeout:
minutes: 30
to: usb
image:
url: file:///home/user/image/yocto-image.xz
compression: xz
root_partition: 1
device: 'boot'
download:
tool: '/usr/bin/wget'
prompt: 'HTTP request sent, awaiting response...'
options: '--S {DOWNLOAD_URL}'
os: oe
The command from LAVA
wget http://lavadisptcher.com/tmp/storage/image/yocto-image.xz | dd of=/dev/disk/by-id/<myusbthumdriveid> bs=4M
This is the output message form LAVA after download flash the image
0+0 records in
0+0 records out
0 bytes copied
Regards,
Alim Hussin
