Lava-users August 2018

lava-users@lists.linaro.org

22 participants
32 discussions

lavacli: adding remote worker requires superuser

by Kevin Hilman

Hello, When trying to use lavacli to add a remote worker, it works fine if the user is a superuser. However, if I drop the superuser privileges and add just the privileges for adding workers, it fails with: Unable to call 'workers.add': <Fault 403: "User 'testuser' is not superuser." we even tried enabling all the permissions for that user, but leaving the superuser flag off, and it still fails. Why does this require superuser and the specific permissions related to workers don't work? Kevin

5 years, 9 months

What are the general design principles about how to plan to deploy remote workers

by john zhang

In lava website,it is lack the documents on how to build multiple remote slave test system.For example,if our system has a lot of test devices. What are the general design principles about how to plan to deploy remote workers, how many dut connect to one worker,etc. Is there any background knowledges about multiple slave and multiNode?

5 years, 9 months

How to configure usb serial in device .jinja2 file

by ljh_dev

The board has usb serial, it connected to computer running dispatcher. On dispatcher computer that usb serial device name is /dev/ttyUSB0 . How to configure usb serial in device .jinja2 file?

5 years, 9 months

Boot time measurement with Lava

by Denis HUMEAU

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

5 years, 9 months

xmlrpc.client.Fault: <Fault -32603: 'Internal Server Error (contact server administrator for details): relation "lava_scheduler_app_build" does not exist

by Yuan, ZhanghuiX

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

5 years, 9 months

Once job case make device cpu crash, is there any mechanism by choose to restart next round test or end test?

by john zhang

Once job test case make device cpu crash, is there any mechanism by choose to restart next round test or end test?

5 years, 9 months

by ljh_dev

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?

5 years, 9 months

how does lava choose job action parallel parameter blocks?

by john zhang

in https://git.linaro.org/lava/lava.git/tree/lava_dispatcher/devices/bbb-01.ya… The boot action includes some marked blocks: oe ,master,nfs... It can be seen that there are multiple command blocks,but lava how tochoose the one of these mark blocks at runtime?Is it passed in by which parameter?

5 years, 9 months

how to step by step to build real machine testing

by ljh_dev

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?

5 years, 9 months

correspondence between uboot manual commands and job definition script commands.

by ljh_dev

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....

5 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Lava-users August 2018