- lava-users - op-lists.linaro.org

bootloader-commands not waiting for prompt

by Jeremy Stashluk

The bootloader-commands step breaks into u-boot and begins to issue commands, but some commands are issued prior to receiving the prompt. I've attempted changing the boot_char_delay, but it doesn't solve the issue. I'm getting symptoms much like the ones in this thread, except I'm sending space rather than a newline, so the fix is not relevant to me. https://lists.linaro.org/pipermail/lava-users/2018-May/001069.html Jeremy Stashluk Embedded Software Engineer [cid:image002.jpg@01D45B04.B75D2A40] Geophysical Survey Systems, Inc. 40 Simon Street * Nashua, NH 03060-3075 603. 893.1109 main * 603.681.2045 direct * 603.889.3984 fax stashlukj(a)geophysical.com<mailto:stashlukj@geophysical.com> * www.geophysical.com<http://www.geophysical.com/>

7 years, 6 months

2
5
0 0

Detect u-boot watchdog in Lava

by Denis HUMEAU

Dear users, I'm looking for a way to detect a possible watchdog in u-boot during a test session. It happened that on one our test platforms a watchdog was triggered, u-boot restarted, and eventually the test session started. Unless we take a look at every trace of every job, there is a big chance to leave this type of errors undetected. Do you have any idea on a possible way to handle this in Lava, maybe via device dictionary? Thanks in advance, Denis

7 years, 6 months

2
1
0 0

CSRF verification failed even after changing settings.conf

by Jorgen Peddersen

Hi, We're using LAVA 2018.5.post1 and we have not been able to log into the web interface since upgrading to this version. The system is running within a docker container. Trying to log in results in a CSRF warning. The same version of LAVA running on a dedicated debian machine does start working when adding the mentioned lines from this page: https://validation.linaro.org/static/docs/v2/installing_on_debian.html#djan… Making the same changes to /etc/lava-server/settings.conf within the docker container has no effect on the way the web interface works. It still provides the same errors. Is there anything else we should do to try to get the web interface to allow logins? I'm not even sure the settings.conf file is being read when restarting the LAVA services, would it appear in one of the logs so that I could search for it? Thanks for any help you can provide regarding this matter. Regards, Jorgen Peddersen Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen(a)seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COM<http://seeingmachines.com> [SEEINGMACHINES] This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-i…] <https://twitter.com/seeingmachines> [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-…] <https://www.linkedin.com/company/258949/>

7 years, 6 months

2
3
0 0

Second serial port control

by Oana Ercus

Hi everyone, I'm a newbie to LAVA, so this may be a stupid question, but I have no idea how to fix this issue. I am using a device for which I enabled the usage of the second serial port as described in the example beaglebone-black job with a second serial port - it seems that the configuration works fine, I was able to enable the secondary connection. The problem is the following: the second serial port connects to a different shell, which at this moment is used for freeRTOS application, and its prompt ("SHELL>>") is different of the primary connection prompt which is used for Linux("root@imx8mqevk"). When trying to actually run some commands on freeRTOS, I get timeout error and I have no idea how to fix it. I attached to this e-mail my test job definition, together with the log and the snip from my web. Thanks in advance for your support, Oana [image: image.png] [image: image.png]

7 years, 6 months

2
3
0 0

Changing SERVER_IP in device-types/bae-uboot.jinja2

by Thomas Klaehn

Hi, As far as I could figure out - the uboot environment server ip is set in the base_uboot_dhcp_command in base-ubooy.jinja2. The value of SERVER_IP seems to be set somehow within lava. And it looks if it's not possible to overide it in the device dictionary, isn't it? Is there a way to change the value of SERVER_IP? Thanks in advance. Best regards, Thomas Klaehn Senior Software Engineer u-blox Berlin GmbH Rudower Chaussee 9 DE-12489 Berlin Phone +49 30 55573 1032 Mobile +49 151 23990904 www.u-blox.com<http://www.u-blox.com/> locate.communicate.accelerate follow us on twitter<https://twitter.com/ublox> | subscribe to our youtube channel<https://www.youtube.com/c/ublox1> | follow us on linkedin<https://www.linkedin.com/company/u-blox> | connect with us on facebook<https://www.facebook.com/ublox1> | follow us on google+<https://plus.google.com/+ublox1> u-blox Berlin GmbH CEO (Geschäftsführer): Daniel Ammann Registered: Berlin HRB 164301 B This message contains confidential information intended only for the use of the addressee(s) and may be legally privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return email and destroy all copies of the original message. All suggestions, recommendations, or other comments contained in this email are provided as a courtesy only. We do not assume any responsibility or liability for the correctness of the information contained in the email.

7 years, 6 months

2
1
0 0

Re: [Lava-users] Reset LAVA database

by Tim Jaacks

Hi Neil, thanks for your quick and direct feedback and please excuse my incautiousness. Being a software developer, I am still new to admin stuff and don't have much experience in hosting servers. The "flush" command is documented in the help text of "lava-server manage". From the information there it seemed as if "lava-server manage dumpdata" would create a dump of the database (which it did) and that I might be able to restore it with "lava-server manage loaddata" (which I couldn't) if the flush would not do what I expected. However, the database in that installation was not important at all, I spent some time experimenting with LAVA on this machine and just wanted to have a clean database for starting production use. I assumed there should be an easy way to achieve this. With your help, I was able to reset my LAVA database using the following commands: sudo apt-get purge lava-server sudo rm -rf /etc/lava-server/ sudo rm -rf /var/lib/lava-server/ sudo pg_dropcluster 9.6 main --stop sudo pg_createcluster 9.6 main --start sudo apt-get install lava-server Thanks for pointing me to the backup topic, I will address that in my next step. Cheers, Tim Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

7 years, 6 months

2
1
0 0

Reset LAVA database

by Tim Jaacks

Hello everyone, is there a way to reset the LAVA database to the state of a fresh installation? From the docs I thought that "lava-server manage flush" command would do that. However, there are some things missing afterwards, e.g. the lava-health user and the master worker. Any hints on how to repair this? Re-installing lava-server did not help. Mit freundlichen Grüßen / Best regards i.A. Tim Jaacks Software Engineering Garz & Fricke GmbH Tempowerkring 2, 21079 Hamburg - Germany Amtsgericht Hamburg HRB 60514 Geschäftsführer: Manfred Garz, Matthias Fricke Phone: +49 40 791899 - 55 Fax: +49 40 791899 – 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com

7 years, 6 months

2
1
0 0

Building Embedded Debian-based system images

by Zoran S

Hello to Linaro developers, Recently I have learned that Linaro has developed its own tool to build Embedded Debian-based system images. I am very interested in this work/this tool. So I have some questions regarding this domain. [1] Do you have published this tool on the Open Source? [2] If YES, what are the web pointers to it, and the docs I can read and get familiar with the process? [3] Does it include scripts to enhance initramfs (the technology Linaro uses to do that), and where are the locations to read about it? [4] You name it (if I miss something, please, feel free to fill the gaps)! I use (almost always) YOCTO based build tool to create initramfses to test upon them (you know this already if you read my recent emails to this list). But I would like to have alternative method, and Linaro tool seems excellent one as alternative, for many reasons. Thank you in advance, Zoran Stojsavljevic _______

7 years, 6 months

2
1
0 0

Why the lava is not designed a machnism that notify user when only a test case is complete(err..)

by john zhang

Lava xml-rpc notification machnism, criteria.status indicates which event can be notified to user (by hook callback). But the criteria.status only has such as "Complete Incomplete,Canceled,finished" events. Why the lava is not designed a machnism that notify user when only a test case is complete(err..),if so that user has more rights to control test process execution.

7 years, 6 months

2
2
0 0

new added worker is offline？

by ramboly

hi all i add a worker to master from the slave container by lavacli.., But the worker is offline in the localhost:10080 web . Master and slave can ping each other sucessfully. any guy konw why? THX

7 years, 6 months

1
0
0 0

Is the use of multinode that a single test job's all test cases are parallel executed simultaneously on multiple devices?

by chao yang

https://validation.linaro.org/static/docs/v2/glossary.html#term-multinode https://validation.linaro.org/static/docs/v2/multinode.html it said "A single test job which runs across multiple devices". I still don't quite understandt the purpose of MultiNode. Is that mean that a single test job's all test cases are parallel executed simultaneously on multiple devices? For example it have 10 test cases and 5 devices, when job is running, firstly the former 5 cases is distributed to 5 devices and parallel run (case 1 is run on device 1,case 2 is run on device 2,... device 5 is run on device 5). When a case is end(suppose case 2) ,then case 6 is scheduled to run on device 2... and so on.Is my understanding correct?

7 years, 6 months

2
1
0 0

what is the "metadata" tag practical use ?

by chao yang

https://validation.linaro.org/static/docs/v2/standard-test-jobs.html#job-me… The above link destripes how to define metadata in job. But how to use these metadata defines?

7 years, 6 months

2
1
0 0

xmlrpc mechanism to monitor job error

by john zhang

I want to implement a function: When a test case in job is crush or return err(no zero), the job can be rescheduled(or resubmit). Does it need to write own event notification? Need monitor "job Incomplete" action? In addition, according to lava xmlrpc doc, I input command in lava server console: python zmq_client.py -j 121 --hostname tcp://127.0.0.1:5500 -t 1200 .The was error : .... File "/usr/lib/python2.7/httplib.py", line 821, in connect self.timeout, self.source_address) File "/usr/lib/python2.7/socket.py", line 557, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM):

7 years, 7 months

1
0
0 0

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?

7 years, 7 months

2
1
0 0

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?

7 years, 7 months

3
9
0 0

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

7 years, 7 months

4
6
0 0

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

7 years, 7 months

2
1
0 0

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?

7 years, 7 months

2
1
0 0

Login incorrect , (auto_login and prompts settings should be correct)

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?

7 years, 7 months

2
1
0 0

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?

7 years, 7 months

2
1
0 0

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?

7 years, 7 months

3
2
0 0

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

7 years, 7 months

3
2
0 0

In which config file is described the path of uboot and kernel image or qemu?

by ljh_dev

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?

7 years, 7 months

2
1
0 0

about qemu device dictionary config

by ljh_dev

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.

7 years, 7 months

3
3
0 0

booting from USB thumb drive

by Hussin, Mohamad Noor Alim

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

7 years, 7 months

2
1
0 0

when add a new real device, do the uboot and kernel program need to be modified according to the lava specifications?

by ljh_dev

Hi, I think the lava web document is relatively simple.I still have some basic questions that didn’t understand. I want to add new real board(for example the arm development board,includes serial,ethernet interface etc)into lava environment. The board had ordinary uboot program, and uboot can download linux kernel image by ethernet interface. If treat it as DUT to run test,do the uboot and kernel program need to be modified or both configuration need to be modified?

7 years, 7 months

2
1
0 0

is the uboot image location specified in the job definition file?

by ljh_dev

When used real board(not qemu),is the uboot image location specified in the job definition file? If so, what keyword is used to indicate the uboot image location? The lava document description is not enough.

7 years, 7 months

2
1
0 0

How to rename a devicetype (and deprecate the old one)

by LABBE Corentin

Hello I have a cubietruck in LAVA, but its devicetype does not follow the rule "devicetype should be the same as devicetree name". Diverting from this rule, make difficult to find if the device is already handled by LAVA. I have lots of other boards which suffer the same problem (odroid-xu3 for example) Do you already have a process for renaming devicetype ? If not, why about duplicating to the correct name (sun7i-a20-cubietruck) and adding some tags (comment like "{# set deprecated = true}") to the old one. The deprectation warning could be printed by the LAVA web interface like the warning about not having health checks. After some release, the deprecated devicetype could be removed. Regards

7 years, 7 months

2
1
0 0

Does board test system must include PDU device?

by john zhang

Does board test system must include PDU device? If test system has no PDU and in job definition the boot action method is u-boot. When board had startup to enter linux interactive environment and submit job at this time. Then how does dispatcher restart the board?

7 years, 8 months

2
1
0 0

How to restart LAVA server master service after LAVA server host restart

by Yuan, ZhanghuiX

Hi LAVA team, I meet one critical error. We restart our LAVA server host machine. We can’t know how to restart our LAVA server service. Could you tell me how to restart LAVA server master service with detail steps? Thanks! The LAVA server is not installed by us. So we are not clear about this. BR/Zhanghui

7 years, 8 months

2
4
0 0

How the parameter {KERNEL} of boot action be passed ?

by ljh_dev

https://validation.linaro.org/static/docs/v2/actions-boot.html#index-9 - setenv loadkernel 'tftp {KERNEL_ADDR} {KERNEL}' It say the {KERNEL} will be substituted. Where is {KERNEL} variable defined? When I submit job definition by web interface,I did't find where to define {KERNEL} variable

7 years, 8 months

2
1
0 0

transfer_overlay file in the same location regardless of test

by Jorgen Peddersen

Hi, I'm trying to use a situation where a large bulk of similar jobs are being sent to several devices of the same device type. These devices require the 'transfer_overlay' option in order for the tests to work due to their setup. We currently are using a single master and worker on the same server. It seems that the same transfer overlay file location (i.e., /var/lib/lava/dispatcher/tmp/overlay-1.3.2.5.tar.gz) is used regardless of the job id and that some of our jobs are experiencing a collision trying to use different copies of that file at the same time. Thus, one of our jobs is deleting the transfer overlay file before another job tries to delete it and the second gets errors. This is the error LAVA produces when viewing the job in the GUI: File "/usr/bin/lava", line 11, in <module> load_entry_point('lava-tool==0.25', 'console_scripts', 'lava')() File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 150, in run raise SystemExit(cls().dispatch(args)) File "/usr/lib/python2.7/dist-packages/lava/tool/dispatcher.py", line 140, in dispatch return command.invoke() File "/usr/lib/python2.7/dist-packages/lava/dispatcher/commands.py", line 247, in invoke self.args.validate) File "/usr/lib/python2.7/dist-packages/lava/dispatcher/commands.py", line 91, in run_pipeline_job exitcode = job.run() File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/job.py", line 340, in run self.cleanup(self.connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/job.py", line 375, in cleanup self.pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 649, in cleanup self.internal_pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 649, in cleanup self.internal_pipeline.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 251, in cleanup child.cleanup(connection) File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/actions/boot/__init__.py", line 458, in cleanup os.unlink(self.url) OSError: [Errno 2] No such file or directory: '/var/lib/lava/dispatcher/tmp/overlay-1.3.2.5.tar.gz' We are working on the 2017.7 build of LAVA, so if this has been changed in a later build, please let me know. If this has not been updated, is there another way to change things so that each job uses a different name and/or location for the overlay file? Thanks, Jorgen Peddersen Jorgen Peddersen Researcher t +61 2 6103 4700 m e jorgen.peddersen(a)seeingmachines.com a 80 Mildura Street, Fyshwick ACT 2609, Australia SEEINGMACHINES.COM<http://seeingmachines.com> [SEEINGMACHINES] This email may contain confidential information. If you are not the intended recipient, destroy all copies and do not disclose or use the information within. Any content that is not concerned with the business of the Seeing Machines Group reflects the views of the sender only, not those of Seeing Machines. No warranties are given that this email does not contain viruses or harmful code. [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-twitter-i…] <https://twitter.com/seeingmachines> [http://www.seeingmachines.com/wp-content/uploads/2018/04/sm-email-linkedin-…] <https://www.linkedin.com/company/258949/>

7 years, 8 months

2
2
0 0

[BUG] Cannot cancel a job

by LABBE Corentin

Hello I have queued jobs that I want to cancel but I get instead: 500 Internal Server Error [Errno 2] No such file or directory: '/var/lib/lava-server/default/media/job-output/2018/07/10/7181/job_data.gz' when I click on cancel. Note that thoses queued jobs are only queued and not assigned to any device. Regards

7 years, 8 months

2
4
0 0

Questions of Test Cases

by 刘彩丽

7 years, 8 months

2
1
0 0

Question about "emulator-5554 connecting"

by kong.jia.yan

Hi, I'm sending this email to confirm if anyone has encountered the same problem as me when using LAVA...I have installed a lava single node instance in a docker container and are trying to add an Android device for testing. But when I ran the adb devices command, in addition to the Android device I connected, an "emulator-5554 connecting" appeared. I have tried many ways to remove this device but I failed. I am sure that the emulator appeared after the docker container containing LAVA instance started, so I wonder if this issue is related to LAVA. Thanks Jiayan Kong

7 years, 8 months

1
0
0 0

Linaro Open Source Lava Server?!

by Zoran S

> Just configure the worker to connect to your master. > This is done in /etc/lava-dispatcher/lava-slave > An example configuration file is available at /usr/share/lava-dispatcher/ lava-slave > > For a first try, you can start without encryption and only define the following variables in the configuration file: > MASTER_URL="tcp://localhost:5556" > LOGGER_URL="tcp://localhost:5555" Hello Remi, Do you, Linaro guys, have some Open Source Lava Server on the Cloud, where I can create lava admin account, hook to it my Lava Worker and try it? I need some access to create device-type BeagleBone Black and device BBB0x as well. This will be interesting experiment, don't you agree? Thank you, Zoran Stojsavljevic _______ On Tue, Aug 7, 2018 at 1:53 PM, Remi Duraffort <remi.duraffort(a)linaro.org> wrote: > Hello, > > the worker will register itself to the master automatically. You don't > have to create the worker manually. > > Just configure the worker to connect to your master. > This is done in /etc/lava-dispatcher/lava-slave > An example configuration file is available at /usr/share/lava-dispatcher/ > lava-slave > > For a first try, you can start without encryption and only define the > following variables in the configuration file: > MASTER_URL="tcp://localhost:5556" > LOGGER_URL="tcp://localhost:5555" > > You can also specify the HOSTNAME if you want. By default the slave will > use the name of the server it's running on. > > This will instruct you local lava-slave (this is the name of the service) > to connect to the local lava-master. > Then restart the lava-slave with "service lava-slave restart" > >

7 years, 8 months

2
2
0 0

single Master Instance installation, worker must only have one?

by ljh_dev

The document about installing lava system, does "Single Master Instance installation " mean master(include lava-server) and worker(include lava-dispatcher) can be installed in the one physical computer? In this simple mode,wheather the worker(logic unit)must only have one?

7 years, 8 months

2
6
0 0

about dispatcher configure

by ljh_dev

I am ready to deploy a local lava single master demo system. The server and dispatcher had be installed in a single computer. In order to enable the server to kno the dispatcher(worker),Then how to configure something. Is doing this?: sudo lava-server manage workers add <HOSTNAME> ,that HOSTNAME is changed in /etc/lava-dispatcher/lava-slave file? And when did,How to see whether dispatcher is working already?

7 years, 8 months

2
3
0 0

lava-server login error

by ljh_dev

Hi, According to lava installation document ,I had installed lava-server to debian 9.5.0.Creating super user operation is ok(sudo lava-server manage createsuperuser --username $USERNAME --email=$EMAIL) . But when using firefox browser to login in by created name , response message: -- SRF verification failed. Request aborted. You are seeing this message because this site requires a CSRF cookie when submitting forms. This cookie is required for security reasons, to ensure that your browser is not being hijacked by third parties. If you have configured your browser to disable cookies, please re-enable them, at least for this site, or for 'same-origin' requests. -- After configured browser to disable cookies,the response is still so. Jiang Lao

7 years, 8 months

6
13
0 0

Re: [Lava-users] about DUT inner program to communicate with Worker

by ljh_dev

Hi,If there is no “dameon” program in DUT. How to add/update the program running in DUT for example application test program or linux kernel or uboot etc.?Jiang Lao -------------------------------------------- On Wed, 1 Aug 2018 at 10:18, ljh_dev <ljh_dev at 126.com> wrote: > Hi, > I have browsed the website documentation of lava overall. I think the > DUT(Device Under Test) should has "dameon" program to communicate with the > Worker Dispatcher module. But I did not find where the DUT "dameon" > program source code is,and how to build&install this DUT "dameon" program. > It does not need to be built or installed. The lava-dispatcher package does all that work for you. https://validation.linaro.org/static/docs/v2/index.html#architecturehttps:/… /var/log/lava-dispatcher/lava-slave.log

7 years, 8 months

2
1
0 0

Re: [Lava-users] about DUT inner program to communicate with Worker Dispatcher.

by Jack Lu

If there is no "dameon" program in DUT. How to add/update the program running in DUT for example application test program or linux kernel or uboot etc.? Best regards,

7 years, 8 months

1
0
0 0

about DUT inner program to communicate with Worker Dispatcher.

by ljh_dev

Hi, I have browsed the website documentation of lava overall. I think the DUT(Device Under Test) should has "dameon" program to communicate with the Worker Dispatcher module. But I did not find where the DUT "dameon" program source code is,and how to build&install this DUT "dameon" program. thanks, Jiang Lao

7 years, 8 months

2
1
0 0

is lava supported to install in debian-9.5.0 version?

by ljh_dev

Hi, Is lava supported to install in debian-9.5.0 version? thanks, Jiang Lao

7 years, 8 months

2
1
0 0

is lava supporte installation in debian-9.5.0?

by ljh_dev

Hi, is lava supporte installation in debian-9.5.0 version? thanks Jiang Lao

7 years, 8 months

1
0
0 0

Regarding Queries in LAVA

by Hemanth K V

Hello Lava Users, We are creating queries in LAVA and adding multiple conditions to query.For example in our yaml job definition we have included os field in metadata section which will have different values.For example following is the metadata section for 2 different jobs Job1: metadata: description: '"Build SiemensIPC-327E target with latest build"' os: Debian device: imx6q Build_ID: QA-BUILD-F0150 Job2: metadata: description: '"Build SiemensIPC-327E target with latest build"' os: Ubuntu device: imx6q Build_ID: QA-BUILD-F0150 Now with queries I am trying to just filter out job running with Build_ID( QA-BUILD-F0150 ) and on only os debian. Entity Field Operator Value namedtestattribute Build_ID exact QA-BUILD-F0150 namedtestattribute os exact Debian When I am creating queries with above information, as a user when I run the query the query results will just list Job1 information but at present in LAVA both the jobs are getting listed. Is this the expected behavior?The LAVA server version used is 2018.5.post1 release. Thanks, Hemanth.

7 years, 8 months

2
5
0 0

Configuration management / Salt / documentation

by Tim Jaacks

Hello everyone, is there any documentation on how Linaro uses Salt for configuring LAVA nodes? I know the infrastructure code is hosted at https://git.linaro.org/lava/lava-lab.git, but since I am new to Salt (and configuration management in general), I would love to have some kind of starting point. Where is this repository checked out? Who applies the defined Salt states and when? Are there any automatic processes happening when someone commits to the repository (e.g. changing a device type or health check job)? What is Linaro's workflow in these cases? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

7 years, 8 months

2
1
0 0

unable to login to local django account from lava webpage

by Hussin, Mohamad Noor Alim

Hi, I just install lava-server to latest release, 2018.5-post1 & created a local Django account. I unable to login using lava webpage from my local machine. Lava webpage did not prompt any error message and I have no idea how to debug this problem. Any idea? Regards, Alim Hussin

7 years, 8 months

2
2
0 0

LAVA email notification configuration

by Diego Russo

Hello, In my LAVA pipeline I have the following snippet: notify: recipients: - to: method: email mail: diego.russo(a)arm.com criteria: status: finished verbosity: verbose When the job ends though I'm not receiving any email. I've looked at the documentation, but I couldn’t find anything about mail configuration. Logs also are not very helpful to debug this issue. How/where can I configure the email client? I'm also interested in changing the "from:" field. Thanks -- Diego Russo Staff Software Engineer - diego.russo(a)arm.com Direct Tel. no: +44 1223 405920 Main Tel. no: +44 1223 400400 ARM Ltd. CPC1, Capital Park, Cambridge Road, Fulbourn, CB21 5XE, United Kingdom http://www.diegor.co.uk - http://twitter.com/diegor http://www.linkedin.com/in/diegor IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 9 months

2
2
0 0

x86 based boot

by Hemanth K V

Hello Lava-Users, I have UEFI based x86 target board which I want to connect to LAVA and execute tests. When I go through https://validation.linaro.org/static/docs/v2/integrate-uefi.html it specifies different mechanism available.I am confused here as I am not completely clear on differences between systems mentioned. If I just know UEFI implementations method of target is it enough to select which method can be used for booting. What are the things I need to know before concluding the method to be used for booting x86 based target board? Thanks, Hemanth.

7 years, 9 months

2
1
0 0

Is LAVA suitable for us?

by magnus＠minimum.se

Hey, Where I work, we've been using LAVA since 2014 to test our in-house Linux distribution. Our devices are typically "low-end" devices with 128 to 256 MB RAM and up to 512 MB NAND flash. We use LAVA to test our BSPs, e.g lots of connectivity/interface/IO tests. We also use it for stability-testing and performance testing (like measuring the application context switch time or Ethernet TX rates). For a while, there has been a growing concern within our team that LAVA might not be ideal for our testing needs. Right now, the team is discussing if we should drop LAVA and use something else. There is even talks about developing our own test framework. I personally like the idea behind LAVA but also agree that it has been a bumpy road these past 4 years. Due to various bugs and missing features, we've several times been forced to upgrade to an unstable version of LAVA just to get normal operations working. Two times we've lost the entire test database because we were unable to recover from a LAVA upgrade. In those cases, it was easier for us to just "start over". Today we use LAVA 2018.02. I've compiled a list that summarize the most pressing issues we've experience with LAVA: 1. Test development is slow. Several members of my team avoids test development because the process of developing a test with LAVA is tedious / very timeconsuming. I think it mostly boils down to making a change, pushing it to a Git repo, submitting a job, running the job and then watching the LAVA job output for result. This will in our environment take several minutes, just to verify a change in a test. I'm aware of the guidelines for making portable tests and I personally think we can be a lot better at it for single-node tests which could enable us to run testscripts on local devices, but we have also quite a number of multinode jobs that we find are difficult to run in any other environment than LAVA. We've also tried using hacksessions to speed up development (e.g you edit the tests on the DUT and then synchronize it back to your host once you're happy). This works quite well, but feels a bit hacky and if the hacksession timeout hits, you lose all your work ;-) 2. Can't test bootloaders. Several of our hardware contain FPGAs and the FPGA images / "firmware" is tightly bundled with the bootloader. In addition to configuring the FPGA, the bootloader also contains in-house developed code for firmware update that we would like to autotest. We have a _lot_ of bootloader variants and we need a way of testing it along with the Linux system. Our current setup is that we manually flash bootloaders in our LAVA lab and then cross our fingers that the Linux system we test on the device is compatible with the bootloader. The ideal situation for us would be to always test the Linux system and the matching bootloader together. Granted, the better solution would be to move away the FPGA loading from the bootloader, but this is a design chosen by our SoC provider and we prefer to keep it. We also manage a "LTS" branch of our Linux distro. We support it for several years and we need to ensure our test setup can test both our "master" branch and our LTS branch. With our current setup, this is not possible because all devices in our lab runs a bootloader that was manually flashed at some arbitrary time. We've considered setting up several hardware of the same type, but with different bootloaders and then let LAVA treat them as different device types. This would work but our lab would fill up fast and the usage of each device would be low. We also tried making jobs that boot a golden Linux system, write the software under test (including bootloader), reboot and run tests. This did work, but required customization per device since the test has to know where to write the bootloader. We would rather put this information into the LAVA device type definition somehow. 3. Can't write to NAND. Our devices are NAND-based and we use UBIFS ontop of UBI. We have not found a way for LAVA to write NAND because the LAVA mechanism that embeds stuff into the rootfs before deployment doesn't support UBIFS. At the moment, we ramboot our devices but we are now at a point where our devices OOM because they don't have enough RAM to fit both the rootfs and running the tests. Our current solution is to split the job into several jobs that each run a smaller amount of tests, but this is less than ideal because it makes our test run slower (we need to reboot) and it is a bit annoying that test results are spread across several jobs. We have our own deployment tool that would be nice to integrate into LAVA as a deployment method. It accepts a kernel, rootfs, DT and bootloader and will write it using TFTP or DFU (USB) depending on target. To avoid forking all of LAVA in order to implement such deploy method, is there any plugin architecture that allows us to install additional boot methods alongside the LAVA packages? I'd love to get your views on these issues and if there is a solution when using LAVA. Best regards, Magnus.

7 years, 9 months

2
1
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users