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

by Manoj Tiwary

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

6 years, 5 months

2
1
0 0

Tradefed test definition modification

by Axel Lebourhis

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

6 years, 5 months

2
8
0 0

setting u-boot bootargs

by Manoj Tiwary

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

6 years, 5 months

2
3
0 0

A question of LAVA's dead container.

by Li, Xiaoming

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

6 years, 5 months

2
1
0 0

Reboot keyword mismatch

by Manoj Tiwary

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

6 years, 5 months

2
1
0 0

Problem with login in Web UI

by Axel Lebourhis

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

6 years, 5 months

2
13
0 0

default Soft reboot command

by Manoj Tiwary

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

6 years, 6 months

2
4
0 0

lava-server won't start

by Axel Lebourhis

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

6 years, 6 months

2
2
0 0

Re: [Lava-users] Default LXC directory for LAVA

by Axel Lebourhis

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

6 years, 6 months

1
0
0 0

Default LXC directory for LAVA

by Axel Lebourhis

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

6 years, 6 months

2
1
0 0

LAVA API add health-check issue

by Patryk Mungai Ndungu

Hello, I am having an issue adding a health-check job for a device-type using the API. I have tried doing so using both lavacli and through a python script using the xml-rpc client, but both times I get the following error: With lavacli: Unable to call 'device-types.health-check': <Fault 400: 'Unable to write health-check: Permission denied'> With the python script: Traceback (most recent call last): File "./API.py", line 9, in <module> server.scheduler.device_types.set_health_check("r8a7743-iwg20d-q7-dbcm-ca","r8a7743-iwg20d-q7-dbcm-ca.yaml") 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 400: 'Unable to write health-check: Permission denied'> The user I use to authenticate the xml-rpc client has superuser privileges and I have tried using a number of different API functions (including ones which require superuser privileges like device-types add and devices add), all of which have worked with both lavacli and the python script. I have also made sure that the name of the healthcheck file matches the device-type. Has anyone else encountered this issue? Thanks, Patryk Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.

6 years, 6 months

3
5
0 0

adding devices in LAVA docker

by Manoj Tiwary

Hi all, I've installed lava-docker from https://github.com/kernelci/lava-docker but I'm little confused about adding devices and device-types to it . As described in the link above , i've edited boards.yaml file and added the board name as follows masters: - name: master1 host: local users: - name: admin token: longrandomtokenadmin password: admin superuser: yes staff: yes tokens: - username: admin token: dfjdfkfkdjfkdsjfsl description: no description slaves: - name: lab-slave-0 host: local remote_master: master1 remote_user: admin boards: - name: bcm2837-rpi-3-b-01 type: bcm2837-rpi-3-b uart: idvendor: 0x0403 idproduct: 0x6001 serial: A904MHLH after I built docker image and ran it. i'm getting following error while loading docker images Removing local_lab-slave-0_1 local_master1_1 is up-to-date Recreating 5b8d2c91c519_local_lab-slave-0_1 ... error ERROR: for 5b8d2c91c519_local_lab-slave-0_1 Cannot start service lab-slave-0: linux runtime spec devices: error gathering device information while adding custom device "/dev/bcm2837-rpi-3-b-01": lstat /dev/bcm2837-rpi-3-b-01: no such file or directory ERROR: for lab-slave-0 Cannot start service lab-slave-0: linux runtime spec devices: error gathering device information while adding custom device "/dev/bcm2837-rpi-3-b-01": lstat /dev/bcm2837-rpi-3-b-01: no such file or directory help me resolve this issue. Thanks, Manoj

6 years, 6 months

2
3
0 0

Fwd: regarding test suites

by Hemanth K V

Hello Lava-users, I am trying to run some test suites in LAVA and my test suite is organized as below -single script with multiple test cases -want to have report the results from LAVA of all test cases -don't want to depend on the return value of script which will make as test case as PASS or FAIL Developing test suites in shell script and using sh-test-lib and attached is sample test script for reference. Want to report the result of iptable_packageCheck_test and iptable_kernel_config_test separately in LAVA framework and will be having single script for both the test cases. Based on above criteria which is best method of running the test script in LAVA.Referred https://validation.linaro.org/static/docs/v2/developing-tests.html Following is the content of LAVA Test Shell Definition I am using metadata: name: applications format: "Lava-Test-Shell Test Definition 1.0" description: "Application tests." os: - debian scope: - Functional environment: - lava-test-shell run: steps: - cd /opt/applications - ./cron.sh - ./iptable.sh - . ../utils/send-to-lava.sh output/result.txt Thanks, Hemanth.

6 years, 6 months

3
2
0 0

Fwd: Issue in adding Device type

by Manoj Tiwary

---------- Forwarded message --------- From: Manoj Tiwary <manojtiwary22(a)gmail.com> Date: Thu 25 Oct, 2018, 6:46 PM Subject: Issue in adding Device type To: <lava-users(a)lists.linaro.org> Hi all, I've installed lava on Ubuntu 14.04 by following below steps : *deb [arch=amd64] http://images.validation.linaro.org/trusty-repo <http://images.validation.linaro.org/trusty-repo> trusty main$ wget http://images.validation.linaro.org/trusty-repo/trusty-repo.key.asc <http://images.validation.linaro.org/trusty-repo/trusty-repo.key.asc>$ sudo apt-key add trusty-repo.key.asc$ sudo apt-get update$ sudo apt-get install lava-server$ sudo a2dissite 000-default$ sudo a2ensite lava-server.conf$ sudo service apache2 restart* Now when i'm trying to add device-type using following command *$ sudo lava-server manage add-device-type qemu* I'm getting command not found error. so , I checked subcommands available using *$ sudo lava-server manage help * I got following output Available subcommands: [auth] changepassword createsuperuser [dashboard_app] addldapuser authorize_superuser linaro_ldapuserlist mergeldapuser [django] check cleanup compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages runfcgi shell sql sqlall sqlclear sqlcustom sqldropindexes sqlflush sqlindexes sqlinitialdata sqlsequencereset startapp startproject validate [django_extensions] clean_pyc compile_pyc create_app create_command create_jobs describe_form dumpscript export_emails find_template generate_secret_key graph_models mail_debug notes passwd pipchecker print_settings print_user_for_session reset_db runjob runjobs runprofileserver runscript runserver_plus set_fake_emails set_fake_passwords shell_plus show_templatetags show_urls sqlcreate sqldiff sync_media_s3 sync_s3 syncdata unreferenced_files update_permissions validate_templates [django_openid_auth] openid_cleanup [lava_scheduler_app] crowd device-dictionary dispatcher-master migrate-users-to-crowd scheduler schedulermonitor testjobmigrate [sessions] clearsessions [south] convert_to_south datamigration graphmigrations migrate migrationcheck schemamigration startmigration syncdb test testserver [staticfiles] collectstatic findstatic runserver add-device-type subcommand is not there. Help me resolve this issue. Thanks & Regards, Manoj

6 years, 6 months

2
1
0 0

Re: [Lava-users] Overwriting SERVER_IP

by Patryk Mungai Ndungu

Hello, Is there a way to overwrite the SERVER_IP variable either in the LAVA environment or in the device-types template/device dictionary? https://lava.ciplatform.org/static/docs/v2/migrating-admin-example.html?hig… No matter what I do, it remains in the rendered yaml file for a device. Unfortunately, the IP it picks up for the environment I'm working is wrong, as I'm running LAVA within a docker-container and it picks up the IP of the container, but the tftp server (within docker) is proxified to the host, meaning that the IP address it needs to pick up is the host's IP. Hence my question, is there a way to overwrite it so that the desired IP appears in the rendered job submission yaml? Thanks, Patryk Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.

6 years, 6 months

2
2
0 0

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

6 years, 6 months

4
8
0 0

job stuck after disconnection

by Corentin Labbe

Hello We got a job (number 332) stuck in running state. After 23h of inaction, the only way to stop it was to cancel+fail it. According to the logs, a small disconnection happen between the slave and master. The slave seems to try to update the final status of the job but the master "ignore" it. Regards This is the slave logs: 2018-09-21 21:45:57,197 INFO [332] Starting job2018-09-21 21:45:57,226 DEBUG [332] device : actions: 2018-09-21 21:45:57,227 DEBUG [332] env-dut : 2018-09-21 21:45:57,241 DEBUG START_OK(332) => master 2018-09-21 21:46:17,260 DEBUG PING => master (last message 20s ago) 2018-09-21 21:46:17,453 DEBUG master => PONG(20) 2018-09-21 21:46:37,475 DEBUG PING => master (last message 20s ago) 2018-09-21 21:46:37,684 DEBUG master => PONG(20) 2018-09-21 21:46:57,708 DEBUG PING => master (last message 20s ago) 2018-09-21 21:47:03,603 DEBUG master => PONG(20) 2018-09-21 21:47:23,625 DEBUG PING => master (last message 20s ago) 2018-09-21 21:47:41,199 DEBUG master => PONG(20) 2018-09-21 21:48:01,222 DEBUG PING => master (last message 20s ago) 2018-09-21 21:48:19,372 DEBUG master => PONG(20) ## 2018-09-21 21:48:39,395 DEBUG PING => master (last message 20s ago) ## 2018-09-21 21:48:59,418 DEBUG PING => master (last message 40s ago) ## 2018-09-21 21:49:19,441 DEBUG PING => master (last message 60s ago) 2018-09-21 21:49:34,458 INFO [332] Job END ## 2018-09-21 21:49:34,487 DEBUG END(332) => master 2018-09-21 21:49:39,496 WARNING Master goes OFFLINE 2018-09-21 21:49:39,496 DEBUG PING => master (last message 80s ago) 2018-09-21 21:49:39,501 INFO [332] Job END (resend) 2018-09-21 21:49:39,515 DEBUG END(332) => master 2018-09-21 21:49:44,521 INFO [332] Job END (resend) 2018-09-21 21:49:44,538 DEBUG END(332) => master 2018-09-21 21:49:49,544 INFO [332] Job END (resend) 2018-09-21 21:49:49,559 DEBUG END(332) => master 2018-09-21 21:49:54,565 INFO [332] Job END (resend) 2018-09-21 21:49:54,588 DEBUG END(332) => master 2018-09-21 21:49:59,594 DEBUG PING => master (last message 100s ago) 2018-09-21 21:49:59,594 INFO [332] Job END (resend) 2018-09-21 21:49:59,612 DEBUG END(332) => master 2018-09-21 21:50:04,618 INFO [332] Job END (resend) 2018-09-21 21:50:04,639 DEBUG END(332) => master 2018-09-21 21:50:09,645 INFO [332] Job END (resend) 2018-09-21 21:50:09,659 DEBUG END(332) => master 2018-09-21 21:50:14,665 INFO [332] Job END (resend) 2018-09-21 21:50:14,685 DEBUG END(332) => master 2018-09-21 21:50:19,690 DEBUG PING => master (last message 120s ago) 2018-09-21 21:50:19,691 INFO [332] Job END (resend) 2018-09-21 21:50:19,708 DEBUG END(332) => master 2018-09-21 21:50:24,714 INFO [332] Job END (resend) 2018-09-21 21:50:24,735 DEBUG END(332) => master 2018-09-21 21:50:29,741 INFO [332] Job END (resend) 2018-09-21 21:50:29,755 DEBUG END(332) => master 2018-09-21 21:50:34,761 INFO [332] Job END (resend) 2018-09-21 21:50:34,776 DEBUG END(332) => master 2018-09-21 21:50:39,781 DEBUG PING => master (last message 140s ago) 2018-09-21 21:50:39,782 INFO [332] Job END (resend) 2018-09-21 21:50:39,800 DEBUG END(332) => master 2018-09-21 21:50:44,806 INFO [332] Job END (resend) 2018-09-21 21:50:44,823 DEBUG END(332) => master 2018-09-21 21:50:49,829 INFO [332] Job END (resend) 2018-09-21 21:50:49,850 DEBUG END(332) => master 2018-09-21 21:50:54,856 INFO [332] Job END (resend) 2018-09-21 21:50:54,876 DEBUG END(332) => master 2018-09-21 21:50:59,882 DEBUG PING => master (last message 160s ago) 2018-09-21 21:50:59,883 INFO [332] Job END (resend) 2018-09-21 21:50:59,901 DEBUG END(332) => master 2018-09-21 21:51:04,907 INFO [332] Job END (resend) 2018-09-21 21:51:04,920 DEBUG END(332) => master 2018-09-21 21:51:09,926 INFO [332] Job END (resend) 2018-09-21 21:51:09,939 DEBUG END(332) => master 2018-09-21 21:51:14,945 INFO [332] Job END (resend) 2018-09-21 21:51:14,967 DEBUG END(332) => master 2018-09-21 21:51:19,973 DEBUG PING => master (last message 180s ago) 2018-09-21 21:51:19,974 INFO [332] Job END (resend) 2018-09-21 21:51:19,994 DEBUG END(332) => master 2018-09-21 21:51:25,000 INFO [332] Job END (resend) 2018-09-21 21:51:25,020 DEBUG END(332) => master 2018-09-21 21:51:30,026 INFO [332] Job END (resend) 2018-09-21 21:51:30,047 DEBUG END(332) => master 2018-09-21 21:51:35,053 INFO [332] Job END (resend) 2018-09-21 21:51:35,071 DEBUG END(332) => master 2018-09-21 21:51:40,077 DEBUG PING => master (last message 200s ago) 2018-09-21 21:51:40,077 INFO [332] Job END (resend) 2018-09-21 21:51:40,095 DEBUG END(332) => master 2018-09-21 21:51:45,101 INFO [332] Job END (resend) 2018-09-21 21:51:45,123 DEBUG END(332) => master 2018-09-21 21:51:50,129 INFO [332] Job END (resend) 2018-09-21 21:51:50,149 DEBUG END(332) => master 2018-09-21 21:51:55,154 INFO [332] Job END (resend) 2018-09-21 21:51:55,175 DEBUG END(332) => master 2018-09-21 21:51:58,639 DEBUG master => PONG(20) 2018-09-21 21:51:58,640 INFO Master is ONLINE 2018-09-21 21:51:58,831 DEBUG master => PONG(20) 2018-09-21 21:51:58,833 DEBUG master => PONG(20) 2018-09-21 21:52:00,053 INFO master => END_OK(332) 2018-09-21 21:52:00,054 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,062 DEBUG master => PONG(20) 2018-09-21 21:52:00,062 INFO master => END_OK(332) 2018-09-21 21:52:00,063 DEBUG [332] Unknown job 2018-09-21 21:52:00,063 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,242 INFO master => END_OK(332) 2018-09-21 21:52:00,242 DEBUG [332] Unknown job 2018-09-21 21:52:00,243 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,243 INFO master => END_OK(332) 2018-09-21 21:52:00,244 DEBUG [332] Unknown job 2018-09-21 21:52:00,244 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,244 INFO master => END_OK(332) 2018-09-21 21:52:00,245 DEBUG [332] Unknown job 2018-09-21 21:52:00,245 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,246 DEBUG master => PONG(20) 2018-09-21 21:52:00,246 INFO master => END_OK(332) 2018-09-21 21:52:00,246 DEBUG [332] Unknown job 2018-09-21 21:52:00,246 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,381 INFO master => END_OK(332) 2018-09-21 21:52:00,382 DEBUG [332] Unknown job 2018-09-21 21:52:00,382 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,436 INFO master => END_OK(332) 2018-09-21 21:52:00,436 DEBUG [332] Unknown job 2018-09-21 21:52:00,436 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,592 INFO master => END_OK(332) 2018-09-21 21:52:00,593 DEBUG [332] Unknown job 2018-09-21 21:52:00,593 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,610 DEBUG master => PONG(20) 2018-09-21 21:52:00,770 INFO master => END_OK(332) 2018-09-21 21:52:00,771 DEBUG [332] Unknown job 2018-09-21 21:52:00,771 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,892 INFO master => END_OK(332) 2018-09-21 21:52:00,892 DEBUG [332] Unknown job 2018-09-21 21:52:00,892 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:00,976 INFO master => END_OK(332) 2018-09-21 21:52:00,977 DEBUG [332] Unknown job 2018-09-21 21:52:00,977 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,156 INFO master => END_OK(332) 2018-09-21 21:52:01,157 DEBUG [332] Unknown job 2018-09-21 21:52:01,157 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,164 DEBUG master => PONG(20) 2018-09-21 21:52:01,170 INFO master => END_OK(332) 2018-09-21 21:52:01,171 DEBUG [332] Unknown job 2018-09-21 21:52:01,171 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,353 INFO master => END_OK(332) 2018-09-21 21:52:01,353 DEBUG [332] Unknown job 2018-09-21 21:52:01,353 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,493 INFO master => END_OK(332) 2018-09-21 21:52:01,493 DEBUG [332] Unknown job 2018-09-21 21:52:01,493 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,550 INFO master => END_OK(332) 2018-09-21 21:52:01,551 DEBUG [332] Unknown job 2018-09-21 21:52:01,551 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,552 DEBUG master => PONG(20) 2018-09-21 21:52:01,700 INFO master => END_OK(332) 2018-09-21 21:52:01,700 DEBUG [332] Unknown job 2018-09-21 21:52:01,700 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,745 INFO master => END_OK(332) 2018-09-21 21:52:01,745 DEBUG [332] Unknown job 2018-09-21 21:52:01,745 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,819 INFO master => END_OK(332) 2018-09-21 21:52:01,819 DEBUG [332] Unknown job 2018-09-21 21:52:01,820 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,936 INFO master => END_OK(332) 2018-09-21 21:52:01,936 DEBUG [332] Unknown job 2018-09-21 21:52:01,936 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:01,938 DEBUG master => PONG(20) 2018-09-21 21:52:02,048 INFO master => END_OK(332) 2018-09-21 21:52:02,048 DEBUG [332] Unknown job 2018-09-21 21:52:02,049 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:02,138 INFO master => END_OK(332) 2018-09-21 21:52:02,138 DEBUG [332] Unknown job 2018-09-21 21:52:02,138 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:22,160 DEBUG PING => master (last message 20s ago) 2018-09-21 21:52:37,178 INFO master => END_OK(332) 2018-09-21 21:52:37,179 DEBUG [332] Unknown job 2018-09-21 21:52:37,179 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,180 INFO master => END_OK(332) 2018-09-21 21:52:37,180 DEBUG [332] Unknown job 2018-09-21 21:52:37,180 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,181 DEBUG master => PONG(20) 2018-09-21 21:52:37,181 INFO master => END_OK(332) 2018-09-21 21:52:37,181 DEBUG [332] Unknown job 2018-09-21 21:52:37,182 DEBUG [332] Removing /var/lib/lava/dispatcher/slave/tmp/332 2018-09-21 21:52:37,374 DEBUG master => PONG(20) 2018-09-21 21:52:57,396 DEBUG PING => master (last message 20s ago) 2018-09-21 21:53:17,418 DEBUG PING => master (last message 40s ago) 2018-09-21 21:53:21,421 DEBUG master => PONG(20) 2018-09-21 21:53:21,610 DEBUG master => PONG(20) 2018-09-21 21:53:41,632 DEBUG PING => master (last message 20s ago) 2018-09-21 21:54:01,653 DEBUG PING => master (last message 40s ago) 2018-09-21 21:54:05,695 DEBUG master => PONG(20) 2018-09-21 21:54:05,893 DEBUG master => PONG(20) 2018-09-21 21:54:25,911 DEBUG PING => master (last message 20s ago) 2018-09-21 21:54:45,933 DEBUG PING => master (last message 40s ago) 2018-09-21 21:54:51,497 DEBUG master => PONG(20) 2018-09-21 21:54:51,692 DEBUG master => PONG(20) 2018-09-21 21:55:11,713 DEBUG PING => master (last message 20s ago) 2018-09-21 21:55:31,733 DEBUG PING => master (last message 40s ago) 2018-09-21 21:55:38,958 DEBUG master => PONG(20) 2018-09-21 21:55:39,147 DEBUG master => PONG(20) 2018-09-21 21:55:59,169 DEBUG PING => master (last message 20s ago) 2018-09-21 21:56:19,191 DEBUG PING => master (last message 40s ago) 2018-09-21 21:56:23,724 DEBUG master => PONG(20) 2018-09-21 21:56:23,927 DEBUG master => PONG(20) 2018-09-21 21:56:43,950 DEBUG PING => master (last message 20s ago) 2018-09-21 21:56:44,137 DEBUG master => PONG(20) 2018-09-21 21:57:04,159 DEBUG PING => master (last message 20s ago) 2018-09-21 21:57:04,351 DEBUG master => PONG(20) And this is the master logs: 2018-09-21 21:45:56,427 INFO scheduling jobs: 2018-09-21 21:45:56,428 DEBUG - bcm2837-rpi-3-b-32 2018-09-21 21:45:56,453 DEBUG -> rpi3-corelab-01 (Idle, Good) 2018-09-21 21:45:56,453 DEBUG |--> [332] scheduling 2018-09-21 21:45:56,459 DEBUG - dra7-evm 2018-09-21 21:45:56,464 DEBUG - qemu 2018-09-21 21:45:56,660 INFO [332] START => agl-core-lab-1 (rpi3-corelab-01) 2018-09-21 21:45:57,341 INFO [332] agl-core-lab-1 => START_OK 2018-09-21 21:45:57,773 DEBUG lava-logs => PING(20) 2018-09-21 21:46:16,711 INFO scheduling health checks: 2018-09-21 21:46:16,724 INFO scheduling jobs: 2018-09-21 21:46:16,725 DEBUG - dra7-evm 2018-09-21 21:46:16,729 DEBUG - qemu 2018-09-21 21:46:17,351 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:46:18,980 DEBUG lava-logs => PING(20) 2018-09-21 21:46:36,744 INFO scheduling health checks: 2018-09-21 21:46:36,757 INFO scheduling jobs: 2018-09-21 21:46:36,758 DEBUG - dra7-evm 2018-09-21 21:46:36,762 DEBUG - qemu 2018-09-21 21:46:37,566 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:46:48,466 DEBUG lava-logs => PING(20) 2018-09-21 21:46:56,776 INFO scheduling health checks: 2018-09-21 21:46:56,790 INFO scheduling jobs: 2018-09-21 21:46:56,791 DEBUG - dra7-evm 2018-09-21 21:46:56,795 DEBUG - qemu 2018-09-21 21:46:57,797 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:47:08,482 DEBUG lava-logs => PING(20) 2018-09-21 21:47:16,809 INFO scheduling health checks: 2018-09-21 21:47:16,822 INFO scheduling jobs: 2018-09-21 21:47:16,823 DEBUG - dra7-evm 2018-09-21 21:47:16,827 DEBUG - qemu 2018-09-21 21:47:23,718 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:47:31,521 DEBUG lava-logs => PING(20) 2018-09-21 21:47:36,841 INFO scheduling health checks: 2018-09-21 21:47:36,854 INFO scheduling jobs: 2018-09-21 21:47:36,855 DEBUG - dra7-evm 2018-09-21 21:47:36,859 DEBUG - qemu 2018-09-21 21:47:54,275 DEBUG lava-logs => PING(20) 2018-09-21 21:47:56,872 INFO scheduling health checks: 2018-09-21 21:47:56,885 INFO scheduling jobs: 2018-09-21 21:47:56,886 DEBUG - dra7-evm 2018-09-21 21:47:56,891 DEBUG - qemu 2018-09-21 21:48:01,321 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:48:14,292 DEBUG lava-logs => PING(20) 2018-09-21 21:48:16,903 INFO scheduling health checks: 2018-09-21 21:48:16,917 INFO scheduling jobs: 2018-09-21 21:48:16,918 DEBUG - dra7-evm 2018-09-21 21:48:16,922 DEBUG - qemu 2018-09-21 21:48:35,995 DEBUG lava-logs => PING(20) 2018-09-21 21:48:36,933 INFO scheduling health checks: 2018-09-21 21:48:36,946 INFO scheduling jobs: 2018-09-21 21:48:36,947 DEBUG - dra7-evm 2018-09-21 21:48:36,951 DEBUG - qemu 2018-09-21 21:48:39,486 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:48:56,011 DEBUG lava-logs => PING(20) 2018-09-21 21:48:56,962 INFO scheduling health checks: 2018-09-21 21:48:56,975 INFO scheduling jobs: 2018-09-21 21:48:56,976 DEBUG - dra7-evm 2018-09-21 21:48:56,981 DEBUG - qemu 2018-09-21 21:49:16,995 INFO scheduling health checks: 2018-09-21 21:49:17,009 INFO scheduling jobs: 2018-09-21 21:49:17,010 DEBUG - dra7-evm 2018-09-21 21:49:17,014 DEBUG - qemu 2018-09-21 21:49:21,406 DEBUG lava-logs => PING(20) 2018-09-21 21:49:37,026 INFO scheduling health checks: 2018-09-21 21:49:37,040 INFO scheduling jobs: 2018-09-21 21:49:37,041 DEBUG - dra7-evm 2018-09-21 21:49:37,046 DEBUG - qemu 2018-09-21 21:49:41,419 DEBUG lava-logs => PING(20) 2018-09-21 21:49:52,363 ERROR [STATE] Dispatcher <agl-core-lab-1> goes OFFLINE 2018-09-21 21:49:57,059 INFO scheduling health checks: 2018-09-21 21:49:57,067 INFO scheduling jobs: 2018-09-21 21:50:01,440 DEBUG lava-logs => PING(20) 2018-09-21 21:50:17,078 INFO scheduling health checks: 2018-09-21 21:50:17,086 INFO scheduling jobs: 2018-09-21 21:50:21,462 DEBUG lava-logs => PING(20) 2018-09-21 21:50:37,097 INFO scheduling health checks: 2018-09-21 21:50:37,105 INFO scheduling jobs: 2018-09-21 21:50:41,484 DEBUG lava-logs => PING(20) 2018-09-21 21:50:57,117 INFO scheduling health checks: 2018-09-21 21:50:57,125 INFO scheduling jobs: 2018-09-21 21:51:01,502 DEBUG lava-logs => PING(20) 2018-09-21 21:51:17,135 INFO scheduling health checks: 2018-09-21 21:51:17,144 INFO scheduling jobs: 2018-09-21 21:51:21,524 DEBUG lava-logs => PING(20) 2018-09-21 21:51:37,154 INFO scheduling health checks: 2018-09-21 21:51:37,162 INFO scheduling jobs: 2018-09-21 21:51:41,546 DEBUG lava-logs => PING(20) 2018-09-21 21:51:57,170 INFO scheduling health checks: 2018-09-21 21:51:57,178 INFO scheduling jobs: 2018-09-21 21:51:58,734 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:58,737 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:59,125 INFO [332] agl-core-lab-1 => END 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,954 DEBUG get_type_name: skipping finalize 2018-09-21 21:51:59,954 DEBUG type_name failed for finalize metatype finalize 2018-09-21 21:51:59,960 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:51:59,964 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,968 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,971 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,974 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:51:59,977 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:00,093 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,287 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,341 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,493 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,496 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:00,674 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,795 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:00,881 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,061 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,063 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,075 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,256 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,397 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,453 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,456 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,568 DEBUG lava-logs => PING(20) 2018-09-21 21:52:01,603 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,646 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,722 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,840 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,842 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:01,884 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:01,985 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,040 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,106 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:02,109 DEBUG agl-core-lab-1 => PING(20) 2018-09-21 21:52:02,220 INFO [332] agl-core-lab-1 => END (duplicated), skipping 2018-09-21 21:52:17,187 INFO scheduling health checks: 2018-09-21 21:52:17,201 INFO scheduling jobs: 2018-09-21 21:52:17,202 DEBUG - dra7-evm 2018-09-21 21:52:17,207 DEBUG - qemu 2018-09-21 21:52:21,585 DEBUG lava-logs => PING(20)

6 years, 6 months

4
4
0 0

REST API

by Milosz Wasilewski

Hi, I made a first attempt to add REST API for some LAVA objects (jobs, devices and device types). The API is very rudimentary but already solves some basic job filtering issues. However I'm not sure how to add dependencies. There are 2 packages required for this code to work properly. Pip packages are named 'djangorestframework' and 'djangorestframework-filters'. Former has a corresponding debian package 'python3-djangorestframework' but the later does not. Any hints how to add proper dependencies to LAVA? The code can be found here: https://git.lavasoftware.org/mwasilew/lava/tree/rest_api milosz

6 years, 6 months

2
12
0 0

Integrate auxiliary device in LAVA test job definition

by Oana Ercus

Hello, I am looking for a suitable method for the following use-case: during test, I need to access the connection to the workstation that runs my LAVA worker and use it as a second namespace in order to be able to issue some commands on the the workstation (like playing an audio file). In other words I need to integrate the workstation as an auxiliary device needed for testing in the test job definition (like ssh <user>@<ws_ip_addr> and send some commands). Using LXC is not an option at this moment. At a first sight, the Multinode support would have the most of the needed features, but I did not find an example of such an usage, if there is any example you can point me to, I will be grateful. Thank you in advance, Oana Ercus

6 years, 6 months

2
1
0 0

Setting tags for existing devices via command line

by Tim Jaacks

Hello everyone, is there a way of setting tags for existing devices via the command line? The "lava-server manage devices update" command does not have a "--tags" parameter, as the "lava-server manage devices add" has. 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

6 years, 7 months

2
3
0 0

Does deploy action have such as "deploy-namespace" to indicate to use previous deploy images?

by john zhang

In lava job definition, boot action can use "connection-namespace" to indicate use previous namespace's connection.Does deploy action have such as "deploy-namespace" to indicate to use previous deploy image? For example in an application scenario, it need to sequential execution two phases pipeline(deploy,boot,test), it can be solved by define two namespace in job definiton. When run it executed in serial as : phase1(namespace1) deploy->boot->test -> phase2(namespace2) deploy->boot->test. If phase2 deploy images(kernel,dtb,rootfs) are exactly same as phase2 deploy images,how to speed up phase2 deploy execution? I guess if deploy action have such as "deploy-namespace" to indicate previous deploy,then phase2 deploy process can be pass.

6 years, 7 months

2
7
0 0

In job defintion file the description of the related device is only the "device_type", why is not "device"?

by john zhang

Before test job,we need to add a "device_type" .jinja2 file to directory /etc/lava-server/dispatcher-config/device-types/,and add a "device" .jinja2 file to /etc/lava-server/dispatcher-config/devices/. The "device_type" .jinja2 file defines device type(for example different hardware) ,and "device" .jinja2 file(at: /etc/lava-server/dispatcher-config/devices/) defines a concrete device. When the dispatcher submits job, a job should be submited to a concrete device.But In job defintion file,the description of the related device is only the "device_type" but no "device", why is not "device"? for example: # Your first LAVA JOB definition for arm device_type: arm job_name: arm pipeline, first job ## why not as: # Your first LAVA JOB definition for arm device: arm01 job_name: arm pipeline, first job

6 years, 7 months

3
6
0 0

does LXC devices mean LXC can emulate various arm devices peripheral interfaces?

by chao yang

https://validation.linaro.org/static/docs/v2/admin-lxc-deploy.html#lxc-depl… , It say that LXC devices can run lava tests within a container without disturbing the dispatcher host. Does LXC support the arm device? Although LXC may supports to run the arm virtual machine in PC server,but how does it support the completed arm device(Including various peripheral interfaces eg ethernet,usb.. ) ? Because the test job often test various peripheral interfaces,Is LXC emulating these interfaces?

6 years, 7 months

2
4
0 0

Getting tests on DUT: other solutions?

by Diego Russo

Hello, Currently I'm testing a board type which deploys OE via u-boot-ums. Before flashing the image into the device, LAVA slave modifies the image copying tests definition onto it. Once the image is modified with all the tests, this is dd'ed into the device, booted and tests will be running. This is OK so far but as soon as we enable signed images (roofs will be R/O but we will be having other R/W partitions) this won't work anymore as we are changing the image and it needs to be resigned. Moreover, this is very board specific. I'm here to investigate alternative solutions which have a more "generic" approach which also a developer (without LAVA) can run. The only assumption is that *the DUT has always wired network connectivity with the SLAVE*. The workflow I have in mind is something like: 1) I have a signed image which I deploy onto the DUT 2) Boot the DUT 3) Instruct the device to get tests from somewhere (either from the SLAVE or internet) 4) Run those tests The step I'd like to solve is 3). I was thinking something like that: * download/compile all I need on the SLAVE (it is not possible to do it on the DUT due to limited resources/libraries/tooling) * setup some sort of server http on the SLAVE in order to serve those files * wget those files onto the DUT * setup and execute the tests. The above approach should work WITHOUT LAVA as well. Basically, replace SLAVE with "developer computer" Is it something I can architect with LAVA? Does LAVA give me this flexibility? Thanks for your help Regards -- 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.

6 years, 7 months

2
4
0 0

Re: [Lava-users] Description of LAVA's user permissions

by Tim Jaacks

>On Mon, 8 Oct 2018 at 10:19, Tim Jaacks <tim.jaacks at garz-fricke.com> wrote: > >> Hello everyone, >> >> is there a detailed description for all the user permissions defined by >> LAVA? Or where do I find them in the source code? >> > >LAVA currently only has one level of permissions - superuser or not. > >There is on custom permission - cancel or resubmit test job. > >Everything else comes from Django and is ignored. > At least the "Can add test job" permission seems to be evaluated as well. The UI element "Scheduler -> Submit" is available only if this permission is set. > >> >> There are lots of permissions of which I have no idea what they mean, e.g. >> "Can [add|change|delete] action data". How is this permission used? >> >> 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 at 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 >> >> _______________________________________________ >> Lava-users mailing list >> Lava-users at lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/lava-users >> > > >-- > >Neil Williams >============= >neil.williams at linaro.org >http://www.linux.codehelp.co.uk/ >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: <http://lists.linaro.org/pipermail/lava-users/attachments/20181008/bf5abb68/…> 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

6 years, 7 months

1
0
0 0

Re: [Lava-users] Description of LAVA's user permissions

by Tim Jaacks

>On Mon, 8 Oct 2018 at 10:19, Tim Jaacks <tim.jaacks at garz-fricke.com> wrote: > >> Hello everyone, >> >> is there a detailed description for all the user permissions defined by >> LAVA? Or where do I find them in the source code? >> > >LAVA currently only has one level of permissions - superuser or not. > >There is on custom permission - cancel or resubmit test job. > >Everything else comes from Django and is ignored. > Oh thanks, I didn't know that. Is this noted anywhere in the docs? > >> >> There are lots of permissions of which I have no idea what they mean, e.g. >> "Can [add|change|delete] action data". How is this permission used? >> >> 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 at 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 >> >> _______________________________________________ >> Lava-users mailing list >> Lava-users at lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/lava-users >> > > >-- > >Neil Williams >============= >neil.williams at linaro.org >http://www.linux.codehelp.co.uk/ >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: <http://lists.linaro.org/pipermail/lava-users/attachments/20181008/bf5abb68/…> 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

6 years, 7 months

1
0
0 0

Description of LAVA's user permissions

by Tim Jaacks

Hello everyone, is there a detailed description for all the user permissions defined by LAVA? Or where do I find them in the source code? There are lots of permissions of which I have no idea what they mean, e.g. "Can [add|change|delete] action data". How is this permission used? 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

6 years, 7 months

2
1
0 0

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

6 years, 7 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

6 years, 7 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/>

6 years, 7 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]

6 years, 7 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.

6 years, 7 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

6 years, 7 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

6 years, 7 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 _______

6 years, 7 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.

6 years, 7 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

6 years, 7 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?

6 years, 7 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?

6 years, 7 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):

6 years, 8 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?

6 years, 8 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?

6 years, 8 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

6 years, 8 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

6 years, 8 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?

6 years, 8 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?

6 years, 8 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?

6 years, 8 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?

6 years, 8 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....

6 years, 8 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?

6 years, 8 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users