- lava-devel - op-lists.linaro.org

by Moein Shafi

Hello everyone, I'm new to LAVA and I have some issue with 'iso-installer' for ubuntu 20.04 . As you know, in ubuntu 20.04 the preseed file would not use 'debian_installer' and use 'subiquity' instead, Also LAVA does not support 'subiquity' for 'iso-installer', so I don't know how can I use 'iso-installer' for testing my ubuntu 20.04.

4 years, 11 months

1
0
0 0

WG: Help with new device integration

by Marcel Trattner

Dear Lava-Team, I contacted you a few weeks ago for some help with the integration of a new device. We got a bit further thanks to you but we're faceing some new issues and we hoped that you could help us with this. We are using the official Docker-Compose<https://git.lavasoftware.org/lava/pkg/docker-compose> repository and specified a new device dictionary on the server container. As a device type we use a newly created device type that extends base-fastboot device-type, which looks like this: {% extends 'rse22.jinja2' %} {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} {% set connection_list = [uart0] %} {% set connection_commands = {uart0: telnet <ip_host_machine> 7101} %} {% set connection_tags = {uart0: [primary, 'telnet']} %} But with this we received the following error: [cid:image001.png@01D6EE7C.31C35A90] The error disappeared however when we removed the following lines: {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} With those lines we are trying to trigger the scripts, which control our power supply directly. Do we have to pay attention to the python dependencies in the scripts or could the error be in the definition itself? We thought, that we had at least configured the device dictionary sufficiently to have a connection to the device and start a very basic health check. Our device runs Linux, which is running Android on top. The Ser2Net connection has been configured according to the instructions on the repo as well (using the telnet command by itself worked fine). So we specified the health check like this: device_type: rsu job_name: Health Check for RSU timeouts: job: minutes: 30 action: minutes: 5 connection: minutes: 2 priority: medium visibility: public actions: - deploy: namespace: tlxc timeout: minutes: 5 to: lxc packages: - android-tools-adb - android-tools-fastboot - boot: method: lxc prompts: - 'root@(.*):/#' timeout: minutes: 5 - test: timeout: minutes: 4 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: hello-world description: "say hello" os: - android scope: - functional run: steps: - apt -q update - pwd - echo "echo hello" # remember to use -y to allow apt to proceed without interaction # -q simplifies the apt output for logging. from: inline name: hello-world path: inline/hello-world.yaml When executing, we got the following error: [cid:image002.png@01D6EE7E.9CED3690] Could you please give us some advice, on how to define a test job/health check for a device, which uses fast-boot and Android? Your help would be greatly appreciated. Best regards, Marcel _________________________________________________________ EMAIL LEGAL MENTION / DISCLAIMER This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.

5 years, 3 months

2
1
0 0

Integration of a new device

by Marcel Trattner

Dear LAVA-Team, We have only recently started to use LAVA in a new project and we are now at the point of integrating a new device. As I have read in the documentation that this is the hardest part I would like to ask for some advice where to start and what to especially look out for. The current state is that LAVA, as a master and one slave is running in two Docker containers by using the example of the following Github repository: https://github.com/kernelci/lava-docker After reading the documentary extensively and trying things out with qemu I'd like to try and integrate the following device: https://www.lantronix.com/products/sa8155p-automotive-development-platform/ Our plan so far would be: Since it has a Snapdragon processor, it's running Android and it is using fastboot for flashing, we figured we could use one of the dragonboard Device-Type templates and duplicate it for our device. But as it comes now to configuring the device dictionary and specifying the test jobs we are not so sure as how to proceed and we also don't want to damage the hardware, so we would be grateful for some help. Here some more information: The DUT is connected via USB and its power supply can be turned on and off by using Python scripts (When defining the power_on and power_off commands, should the scripts then be on the master or on the dispatcher? And what are all the necessary parameters for the power on/off and also the values connection_list and connection_commands?). It is running Android with the underlying Linux configured especially for the hardware, so we would like to avoid deploying for the beginning and only run some simple shell tests to see if the connection stands. A very simple health check has been set up here<https://paste.debian.net/1175549>, maybe you could give some feedback if that would be sufficient and how future test jobs should be altered. Hope to hear from you soon Best Regards, _________________________________________________________ EMAIL LEGAL MENTION / DISCLAIMER This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.

5 years, 5 months

2
1
0 0

Re: [Lava-devel] Integration of a new device

by koti koti

++ Lava-users list. Regards, Koti On Fri, 4 Dec 2020 at 17:30, <lava-devel-request(a)lists.lavasoftware.org> wrote: > Send Lava-devel mailing list submissions to > lava-devel(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-devel > or, via email, send a message with subject or body 'help' to > lava-devel-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-devel-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-devel digest..." > > > Today's Topics: > > 1. Integration of a new device (Marcel Trattner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Dec 2020 10:50:08 +0000 > From: Marcel Trattner <marcel.trattner(a)expleogroup.com> > To: "Lava-devel(a)lists.lavasoftware.org" > <Lava-devel(a)lists.lavasoftware.org> > Cc: Alexander Wyron Wachtberger > <alexander-wyron.wachtberger(a)expleogroup.com>, Vladimir Schmidt > <vladimir.schmidt(a)expleogroup.com> > Subject: [Lava-devel] Integration of a new device > Message-ID: > < > AM9PR10MB4295B7516795BD7B514C2DF7E5F10(a)AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="us-ascii" > > Dear LAVA-Team, > > We have only recently started to use LAVA in a new project and we are now > at the point of integrating a new device. As I have read in the > documentation that this is the hardest part I would like to ask for some > advice where to start and what to especially look out for. > > The current state is that LAVA, as a master and one slave is running in > two Docker containers by using the example of the following Github > repository: > > https://github.com/kernelci/lava-docker > > After reading the documentary extensively and trying things out with qemu > I'd like to try and integrate the following device: > > https://www.lantronix.com/products/sa8155p-automotive-development-platform/ > > Our plan so far would be: > Since it has a Snapdragon processor, it's running Android and it is using > fastboot for flashing, we figured we could use one of the dragonboard > Device-Type templates and duplicate it for our device. But as it comes now > to configuring the device dictionary and specifying the test jobs we are > not so sure as how to proceed and we also don't want to damage the > hardware, so we would be grateful for some help. > > Here some more information: > The DUT is connected via USB and its power supply can be turned on and off > by using Python scripts (When defining the power_on and power_off commands, > should the scripts then be on the master or on the dispatcher? And what are > all the necessary parameters for the power on/off and also the values > connection_list and connection_commands?). > It is running Android with the underlying Linux configured especially for > the hardware, so we would like to avoid deploying for the beginning and > only run some simple shell tests to see if the connection stands. > A very simple health check has been set up here< > https://paste.debian.net/1175549>, maybe you could give some feedback if > that would be sufficient and how future test jobs should be altered. > > Hope to hear from you soon > > Best Regards, > > > _________________________________________________________ > > EMAIL LEGAL MENTION / DISCLAIMER > > This message contains information that may be privileged or confidential > and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, > located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to read, print, retain, copy, > disseminate, distribute, or use this message or any part thereof. If you > receive this message in error, please notify the sender immediately and > delete all copies of this message. > > Ce message contient des informations qui peuvent ?tre privil?gi?es ou > confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS > Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le > Bretonneux-France. Il est destin? uniquement ? la personne ? qui est > adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? > ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce > message ou toute partie de celui-ci. Si vous recevez ce message par erreur, > veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les > copies de ce message. >

5 years, 5 months

1
0
0 0

Re: [Lava-devel] [Lava-users] LAVA tests execution on already provisioned (boot) begalbone board

by Milosz Wasilewski

On Tue, 17 Mar 2020 at 12:30, koti koti <kotisoftwaretest(a)gmail.com> wrote: > > Hi, > > I have successfully booted the Beagelbone board from "https://github.com/danrue/lava.therub.org" . (corresponding ymal is https://github.com/danrue/lava.therub.org/blob/master/server-overlay/etc/la…) > > But, now I am trying to run one more scenario (may be new scenario and not sure is it supported by LAVA lab?) i.e > > 1. Run the tests on already provisioned (boot) beagelbone board. (Basically I am skipping the booting mentioned and trying to run on the already provisioned/boot board) > a) boot the target > b) Connect Board to LAVA lab > c) Just check the login prompt ("#") is available or not? > c) Run the using below test definition file (Basically this test definition file runs "ls"/"ifconfig" commands in the already provisioned(boot) board). > > " > device_type: beaglebone-black > job_name: beaglebone-black healthcheck > timeouts: > job: > minutes: 10 > action: > minutes: 5 > priority: high > visibility: public > actions: > - test: > interactive: > - name: ls test > prompts: ["#"] > echo: discard > script: > - name: ls > command: ls > successes: > - message: "ls simple test successes" > failures: > - message: "TIMEOUT" > exception: InfrastructureError > error: "ls command failed" > - name: ifconfig > command: ifconfig > - name: wait for the prompt > command: > " > > I have tried to run this. But, my test failed with the error ""Connection closed"" (Attached screenshot) Connection closed is usually not sth wrong with LAVA but with serial. Are you able to connect to the board by telneting to your ser2net port? I assume you use ser2net as in Dan's example. If not, could you explain how do you connect to the BBB's UART? milosz > > Can some one let me know solution to fix this error? > > Regards, > koti > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users

6 years, 2 months

2
1
0 0

Design meeting minutes from 2019-12-18

by Remi Duraffort

Hi folks, I forget to send the last design meeting notes that you can find on https://git.lavasoftware.org/lava/lava/wikis/design-meetings We held our regular design meeting today via Hangout. Summary of brief discussion: # Connect presentations? [Rémi] * Docker deploy/boot/test for adb? * [Antonio] will make this presentation * LAVA rest api? * Some slides in the LAVA USers forum * Remote labs setup? * [milosz] will make this presentation * LAVA users forum * [Rémi] will submit the talk # documentation layout [Rémi] * http://people.linaro.org/~remi.duraffort/site/ Comments? * [Antonio] issues with the menu on smaller screens * Some CSS to change? # read the doc [Milosz] Will ping the admins to get back the lava project # port of lava-coordinator to python3 [Antonio] * [Rémi] Already working under python3 * Antonio will update the packaging to provide the binary from src:lava and drop src:lava-coordinator # Docker support coming up soon [Antonio] * With this patch all three methods works * Bare metal * lxc * Docker * So this is safe to merge and test on staging * Won’t be able to test fastboot_via_uboot locally ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/usu-aatj-fht Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Architect Linaro

6 years, 4 months

1
0
0 0

Design meeting minutes from 2019-09-11

by Remi Duraffort

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: # 11th September 2019 # Reducing the privilege of lava-slave [Antonio] It’s more or less ok that lava-run requires being run as root. But can we run lava-slave as non-root? Lava-slave needs to cleanup after lava-run if something goes wrong, so there might be stuff owned by root left over and this needs to be handled. Otherwise it’s `go for it`. # Replacing LXC with docker [Antonio] How exactly do we want to do that: See https://git.lavasoftware.org/lava/lava/issues/305 and https://git.lavasoftware.org/lava/lava/issues/286 The goal is to: * simplify the job definition (see the job definition in https://git.lavasoftware.org/lava/lava/issues/305) * allow to use user provided docker container to run adb # Job level privileges [milosz] How does that work compared to device and device-type level privileges? See https://git.lavasoftware.org/lava/lava/merge_requests/693 for more documentation The job level permission are still applied, but the device-type and device permissions are also applied (was not the case before). # LAVA package uploads to Debian? [Steve] I don't have time to do it anymore, and we have RC bugs: * some django2 issues too? patches from Antonio * One more patch https://git.lavasoftware.org/lava/lava/merge_requests/696 * Gunicorn problem? Need to update the dependency * VLANd python3 conversion underway * lava-coordinator debian package depends on python2 # New maintainer for vland [milosz] Since Steve is moving to a new project we’ll need a new maintainer for vland. # SAN19 - all stuff up to date and slides done? [Steve] Any meetings to plan? * lavafed # Moving docker base images to buster? [Rémi] When should we use buster as the base image? Will be the base image for 2019.10 # Hangout meetings links changed [Steve] The documentation should be updated. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/usu-aatj-fht Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Team, Linaro

6 years, 8 months

1
0
0 0

LAVA 2019.07 dependencies

by Dave Pigott

Hi Remi, When I was doing the lkft upgrade this morning I noticed that there is a Buster dependency for LAVA. One of the workers had somehow been missed out on the Buster upgrade and was still on Stretch. I discovered the following: lava-dispatcher : Depends: python3-requests (>= 2.20.0) but 2.12.4-1 is to be installed Does this mean we really have to check for Debian version 10.0 or later for remote, bare metal, workers? Thanks Dave ---------------- Dave Pigott LAVA Lab Lead Linaro Ltd t: (+44) (0) 1223 400063

6 years, 9 months

2
1
0 0

Design meeting minutes from 2019-07-31

by Remi Duraffort

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: # 31st July 2019 # Using celery inside LAVA [Rémi] Could be used for: * Parsing description.yaml * Replace crontabs * Compressing logs * Removing old jobs * Sending logs to ES * Splitting scheduling * notifications # August release ? [Steve] Yes - aim for 28th The release will have database changes Tag the day before to let some time for lavafed to test the tag # LAVA sessions for Connect [Steve] Three sessions has been accepeted: * LAVA Users' Forum * Hacking and contributing to LAVA * Advanced testing in python # Support packages in Debian removed/being removed [Steve] * lava-tool removed (https://tracker.debian.org/pkg/lava-tool) * django-compat marked for removal ( https://tracker.debian.org/pkg/django-compat) * django-hijack depends on django-compat, marked for removal too ( https://tracker.debian.org/pkg/django-hijack) * Rémi will remove the dependency/mention * VLANd needs some rework to go to [python 3]( https://git.lavasoftware.org/lava/vland/issues/5) # Migrating to django 2.2 (next LTS release) [Milosz] * lava source code itself is compatible with django 2.2 * Dependencies on filters and rest framework * Still waiting for a release compatible with django 2.0 * Trying to contact the maintainer to give some help (if needed) # gitlab-runner on aarch64 [Steve] The current package in [Debian]( https://tracker.debian.org/pkg/gitlab-ci-multi-runner) was a bit too old. GitLab don't provide anything for arm64 but the Debian maintainer uploaded a new version that fixe our issues. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Team, Linaro

6 years, 9 months

1
0
0 0

Design meeting minutes from 2019-07-24

by Remi Duraffort

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: # 24th July 2019 # install.git-deps [milosz] This feature works nicely: https://lkft.validation.linaro.org/scheduler/job/834097 Proposal: keep `install` option but restrict it so it’s not trying to install system packages. [Rémi] Will submit a patch to remove the “deprecation” warning in the documentation. # Authentication refactoring [milosz] Under review by Remi. Looks good. # Connect sessions where accepted [Rémi] * LAVA users forum * Hacking and contributing to LAVA * Advanced testing in python # Playing with Sentry error reporting [Rémi] * Will create a ticket to have it installed in the linaro lab. * Will create sentry.lavasoftware.org * No debian package available for python3-sentry-sdk * Should be installed from pip (sentry-sdk) * Will send a patch to install sentry-sdk from pip in lava-server docker container. * Activate it for lavafed instances. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Team, Linaro

6 years, 9 months

1
0
0 0

Design meeting minutes from 2019-07-17

by Remi Duraffort

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: # 17th July 2019 # Large job definitions causing outages [deanb] * Issue: https://git.lavasoftware.org/lava/lava/issues/299 * Wondering if for large jobs (configurable limit) simply not making ActionData objects is a sensible approach. * Tried this: https://git.lavasoftware.org/dean-birch/lava/commit/dd220c0bd82bf092e35e643… * In my test instance this reduced outage to 30 seconds (from hours). * If not, what else can we do? * Anything extra needs to be added? * Documentation? * [deanb] will send a patch with the first improvements (CLoader) * [deanb] will look at using bulk save to save all objects in one call * [stevan] investigate ActionData: is it possible to create them later on or even maybe not creating them? # Test from inline with git [milosz] The idea is to source test-definition YAML from inline but use git repository to prepare overlay. Example: https://github.com/andersson/bootrr Bjorn doesn’t want to have YAML file in this repository [Rémi] Using install.git-repos might work * https://git.lavasoftware.org/lava/lava/blob/master/lava_dispatcher/tests/te… * https://docs.lavasoftware.org/lava/lava_test_shell.html#adding-git-bzr-repo… [milosz] will try install.git-repos If that’s working Rémi will add some tests in lavafed or meta-lava # Switching between serial connections on device with multiple UARTs [Malcolm Brooks] * Issue: We have devices which use separate serial outputs for MCC, AP and SCP UARTs. * Workaround: Use the `new_connection` boot method to switch between UART1 and UART2 in order to catch the kernel booting once MCC flash stage is complete. * Idea: Allow all connections (or possibly a subset defined in the “connection_tags” for example) to be established and followed from the beginning of the job, and allow each action/stage to select which they are actually listening/interacting with the `connection` option (example below). ```yaml - boot: namespace: target connection: uart1 method: minimal ``` [Rémi] Sounds like a good idea. * Using feedback LAVA can already use one connection and listen/print the other ones * Malcom will create an issue on gitlab. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Team, Linaro

6 years, 10 months

1
0
0 0

Large job definitions in LAVA

by Dean Birch

Hi All, We've previously had an issue on our LAVA instance where it stopped responding to workers and stopped dispatching jobs when it finished running large job definition (around 25000 lines in the definition, around 1000 deploy/boot/test actions). I've been looking into reproducing this safely in a development environment, and I've got a few observations and questions about how the situation could be improved. The lava-master process appears be stuck processing the job results, and takes a painstakingly long time to finish this and send an ACK for END_OK. During this processing, the master doesn't respond to worker pings, and doesn't schedule other jobs. Tracking a bit deeper, it seems that the vast majority of time (I've never seen it finish as I have always restarted the lava services before it finishes) in the walk_actions and build_action functions of the lava_results_app/dbutils.py file: https://git.lavasoftware.org/lava/lava/blob/2019.05.post1/lava_results_app/… https://git.lavasoftware.org/lava/lava/blob/2019.05.post1/lava_results_app/… What options is there to mitigate this issue? Some ideas below: - Could we optimize the build_action function? There are a few Django model/db queries in build_action, could some results be queried once and cached? With an obscenely large job, would this even give us enough savings to make the time invested in safely optimizing this worth it? - What are the implications of not having created ActionData objects for a job? Does this mean that no options will be available in the "Pipeline ↓" drop-down on the job page for quick navigation? Could we optionally abort after a certain amount of these (and make it configurable per LAVA instance)? - Should/could the handling of the results be forked off, so lava-master can continue to schedule more jobs and respond to worker pings, but slowly the ActionData objects can be populated? I'm unsure if you have to be on a special thread to write to Django models. Even if this could be done, would any weird behaviours occur on the slave side as it will still be waiting for the ACK for END_OK from the master? Any guidance on how to proceed with this would be appreciated! I'm happy to place this and some more details in as a LAVA issue on git.lavasoftware.org if this is easier to track and discuss. Thanks, Dean

6 years, 10 months

2
2
0 0

No design meeting for 2019-07-10

by Steve McIntyre

Hi folks, As Rémi and Stevan are both out and we don't have any items listed for discussion in advance, I'm cancelling today's design meeting. Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 10 months

1
0
0 0

Design meeting minutes from 2019-07-03

by Steve McIntyre

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: 3rd July 2019 1. [Rémi] 2019.07 release? 1. Should we do one? 2. Most people will be out for most of the month 3. Maybe worth it for the LITE group (depends on the number of patches). 4. Steve back from DebConf on the 28th, but… 5. Yes: releasing around the 18th 2. [Rémi] Debian buster is due soon 1. Basing the docker image on Buster? 2. No, wait for a little bit. Maybe 2019.08? 3. Staging is already running Buster, main v.l.o is still on Stretch but the lab team will want to upgrade soon 4. How long do we support stretch-backports? 5. Add buster-backports soon, as new uploads will hit Debian unstable (---> Bullseye). 6. Target 2019.08 at all three releases (stretch-backports, buster-backports, bullseye) 3. [Rémi] Recommendations about VACUUM ANALYZE 1. This should be run regularly (every day) on busy instances to clean up 2. Add a thing in the docs, test in the lab 3. See https://www.postgresql.org/docs/11/sql-vacuum.html for more info - does a VACUUM then ANALYZE without the old data. 4. Lets the DB self-optimise for performance 4. [Rémi] Using git submodule to include docker sources into lava sources 1. Still a separate repository 2. The exact commit hash used for the lava docker image is now known and reproducible. 1. This is the main reason 2. Using version.py on the last commit of the docker directory can also work. 3. See https://git.lavasoftware.org/lava/lava/merge_requests/637 4. Let's go with this instead of git submodule, it works fine ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 10 months

1
0
0 0

Design meeting minutes from 2019-06-26

by Steve McIntyre

Hi folks, We held our regular design meeting today via Hangout. Summary of brief discussion: 26th June 2019 1. 2019.06 release 1. https://federation.lavasoftware.org/versions/ 2019.05.0050.gf287c3449/ 1. Looks ok 2. https://git.lavasoftware.org/groups/lava/-/merge requests?milestonetitle=2019.06 2. [Dean] Fast model support 1. Was deprecated 2 years ago with V1 2. Now needed again 3. Run as a user-configured container (so test writer does stuff), or re-integrate like we had with v1? 4. Very similar to how we do qemu 5. Look at how we run openocd/gdb as inspiration 3. [Remi] Allowing test job definitions to override U-Boot config (e.g. load addresses) 1. Should be easy, waiting on a patch from Matt 4. [Kumar] Direct serial connection (#296) 1. pyserial probably the best bet? 1. Look at connection tags like in: 1. https://staging.validation.linaro.org/scheduler/ device/staging-black01/devicedict#defline77 2. ser2net works, but this might add more flexibility 3. possible timing problems with ser2net in a container? 4. we can help working out package dependencies etc. if needed 5. Linaro Connect SAN19 - what sessions should we have? 1. Talk next week, suggestions welcome ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 10 months

1
0
0 0

Design meeting minutes from 2019-06-05

by Steve McIntyre

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of brief discussion: 5th June 2019 1. [Rémi] 2019.06 planning: 1. Features and issues that should be in for 2019.06 2. Try to assign some, depending on the available time to work on LAVA 3. [stevanr] 1. VAC, plus auth refactoring fixes 4. [Steve] 1. lots of doc updates 2. debugging some Arm issues 3. vland - docs, new switch support, etc. 5. Finish reviewing/reworking/merging Tim's device-dict in test job patch 1. Anibal looking into this too 2. With expansion, helps to support the expanded fastboot image work 6. https://git.lavasoftware.org/lava/lava/issues/277 - make table lengths configurable? 2. [Anibal] Some NFS code is duplicated - will open an issue ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 11 months

1
0
0 0

Design meeting minutes from 2019-05-29

by Steve McIntyre

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of brief discussion: 29th May 2019 1. [Rémi] 2019.05 release: changelog 1. Last part of the fix for the security issue regarding job context 2. Lava-slave and socks proxy for remote labs behind proxies 3. Compressing job logs 2. [Rémi] Next releases 1. 2019.06 1. Rest api filter 2. device dictionary access from the test shell 2. 2019.08 1. auth refactoring 3. [Steve] Name for the extra udev tools package? 1. Forwarding udev events to docker containers 2. udev pass-through script 3. "docker-udev-tools" agreed and created as a new project 1. https://git.lavasoftware.org/lava/docker-udev-tools ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 11 months

1
0
0 0

Design meeting minutes from 2019-05-22

by Steve McIntyre

Hi folks, We held our regular weekly design meeting on 22nd May via Hangout. Summary of brief discussion: 22nd May 2019 1. [milosz] How to fix packaging on this branch: https:// git.lavasoftware.org/mwasilew/lava/pipelines/3220 ? 1. Fixed by Steve and Rémi 2. Problem with some debian python packages 2. [Steve] charfield to textfield changes needing work - !527 1. as Stevan points out, this is breaking other things. 2. Going to back out the future-proofing changes that extended this, and go back to just fixing the specific things that we've found to be broken 3. [stevanr] Auth refactoring submit/resubmit/cancel permissions 1. Currently: submit is a separate permission and resubmit/cancel goes in the same permission level 2. Submit permission is not tied to specific testjob while resubmit and cancel are 3. [ivoire] Keep things as is 4. [Anibal] questions about the fastboot-nfs setup - how to do things? 1. how to pass information into the lxc when creating the image? 2. Ordering of actions is important - the test action in the lxc will need information that's available from the fastboot deploy step. To pass via overlay, would need this to be available before the lxc deploy 3. Can we simply pass the device dict for the DUT into the lxc, similarly to what Tim has in https://git.lavasoftware.org/lava/ lava/merge_requests/536 ? 4. How to list the variables/information we want to have available? 1. Device dictionary 2. Some dynamic data (nfsrootfs address) 5. What about listing in the test block, the “dependencies” (find a better name) that we are expecting? ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

6 years, 11 months

1
0
0 0

Design meeting minutes from 2019-05-15

by Steve McIntyre

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of brief discussion: 15th May 2019 1. [Steve] https://git.lavasoftware.org/lava/lava/issues/273 - Using long URLs in notify block causes lava-logs to crash. 1. Clearly using the wrong type of field here (fixed-length CharField instead of an open-length TextField). That's easily fixed. 2. Where else might we be using the wrong data types in our DB models and potentially storing up future bugs? Quick scan of CharField uses in models.py: 1. ExtendedUser.irchandle 40 2. ExtendedUser.ircserver 40 3. Architecture 100 (primary key) 4. ProcessorFamily 100 (primary key) 5. Alias 200 (primary key) (also, ignoring due to other work) 6. Core 100 (primary key) 7. DeviceType.cpumodel 100 (primary key) 8. Worker.hostname 200 (primary key) 9. Device.hostname 200 (primary key) 10. Device.deviceversion 200 11. JobFailureTag.name 256 12. TestJob.subid 200 13. TestJob.targetgroup 64 14. TestJob.description 200 15. Notification.template 50 16. Notification.blacklist 100 (array) 17. Notification.queryname 1024 18. Notification.conditions 400 19. NotificationRecipient.email 100 20. NotificationRecipient.irchandle 40 21. NotificationRecipient.irc_server 40 22. NotificationCallback.url 200 23. NotificationCallback.token 200 2. [Remi] udev event forward 1. How to get udev events (kernel and udev types) inside a docker container? 2. The NETLINK socket is affected by the network namespaces 1. Run systemd-udev inside the docker container 2. Remove the network namespace (--net host) 1. Ugly and hacky 3. Run a service on the host that forward events 1. Another project on lavasoftware.org - udevforward.py 2. [Rémi] sending to all docker containers? Filtering the container names? 1. Currently broadcasting to the selected containers only. 3. [Rémi] Make udevforward a proper project under the lava group 1. [All] find a good name, let’s chat on irc 2. Will move the passthrough script in the same repo. 3. [Kumar] Race between Cortex-M USB devices and Connectdevice() 1. Some boards: 1 usb for serial + debug/flashing 2. udev event for the tty vs symlink created 3. [Kumar] create an issue in git.l.o/lava/lava 4. [Matt] lava-test-raise allow different exceptions 1. Parsing args on device vs parsing args on server 1. Parsing on the DUT is cleaner 2. [Matt] finish the patch and send a MR 5. [Dan] Support fastboot boot with ramdisk and NFS issue 271 1. Mimic uboot, command ramdisk or command nfs 2. Maybe something like https://staging.validation.linaro.org/scheduler/ job/252683/definition#defline39 6. [Dean] Job error spotted with message “Unable to create metadata store: [Errno 36] File name too long: '/var/lib/lava-server/default/media/ job-output/2019/05/15/61270/metadata/…” 1. How to safely truncate these filenames and still save them? 2. Check this isn’t multiple lines and test cases etc. 3. [Dean] to raise a bug with some more info 7. [Rémi] Cycle planning draft 1. -ENOTIME, coming back to this later ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

7 years

1
0
0 0

Re: [Lava-devel] How to handle udev events when lava dispatcher is in a container

by Kumar Gala

> On May 9, 2019, at 8:11 AM, Kumar Gala <kumar.gala(a)linaro.org> wrote: > > In trying to run lava-dispatcher inside a docker container and connect a FRDM-K64F board ran into some issues related to the fact that udev events aren’t seen inside the container since we aren’t typically running systemd/udevd there. > > I came across this project that will forward udev events from the host to a container that worked pretty well: > > https://github.com/eiz/udevfw > > I’ve re-implemented this in python for easier development (added some docker awareness): > > https://git.lavasoftware.org/galak/docker-compose/blob/lite/contrib/udev-fo… > > Right now running udev-forward.py is kinda kludgy. Wanted to get input on how people think this should work, should we make a daemon out of it? Should there be some kinda of config file? Do we think we need to filter events (and if so how)? Need to look at support for multicasting (support sending to multiple dispatchers). Where should this live, in docker-compose repo? > > Other thoughts. > > - k I’ve updated my udev-forward.py script to handle multicasting and handle the lifecycle of docker containers better (having them come up/down, already be running). Now its much closer to being able to run just as a deamon, still need to figure out how we’d specify config info for that case. - k

7 years

1
0
0 0

Design meeting minutes from 2019-05-08

by Steve McIntyre

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of brief discussion: 1. [Dan/Anibal] fastboot NFS/ramdisk support 1. LAVA can almost do it today 2. https://git.lavasoftware.org/lava/lava/issues/271 1. See also this discussion https://lists.lavasoftware.org/ pipermail/lava-devel/2019-May/000047.html 3. How best to describe things in a job? 1. new deploy method? 2. name? fastboot-nfs? fastboot-noflash? bob? 4. How does this interact with the generation of the image? 1. if the user makes/tweaks the image inside an lxc, how do we pass details in/out? 2. For creating boot images or binaries, the idea is to implement a deploy method that can either run commands directly on the dispatcher (which may happen to be inside a container) or inside a container controlled by LAVA. This will replace the current LXC setup. 5. Revisit next week with Remi! 2. [Matt] Booting a kernel… without a bootloader you can interrupt... Two options: 1. option 1: static config per-device, place the files in the right place for the device and start it. depthcharge, or PXE-alike systems. Mostly there, but needs tying together 2. option 2: kea (or similar) - modify the DHCP config (kea?) as the test starts. Really the right answer for PXE infrastructure. Better solution, but longer term 3. [stevanr] Authentication refactoring mr’s are in, Remi will start reviewing after Monday 1. https://git.lavasoftware.org/lava/lava/mergerequests/511 2. https://git.lavasoftware.org/lava/lava/mergerequests/515 3. [Steve] will send out a mail describing our plan to collect together database migrations in future releases, for sanity 4. [deanb] Large job definition causes scheduler to hang. 1. No errors given, I think it’s simply taking a long time to read the definition and create a pipeline 2. (particular example in this test is ~25k lines of job definition, massive amounts of inline test definitions) 3. not clear what's going on? is it just time to parse yaml? using lots of memory for pipeline stuff? 5. [deanb] Reboots during test 1. Team wants to run a test step which sometimes locks up if we don’t reboot occasionaly. 2. Want to run a segment of a test, then reboot, then continue. 1. [milosz] try this : https://github.com/Linaro/ test-definitions/tree/master/automated/android/ noninteractive-tradefed 3. long-time wishlist feature for LAVA, but problematic: 1. how do we make sure the device boots sanely? not all devices are safe here? 2. the test suite will need to checkpoint where it got to, so it can resume sensibly after reboot 6. [deanb] Serial corruption when executing lava test shell 1. Not sure how to handle 2. Get corruption in the string when executing /lava-... 3. Once we’re into the lava test shell, we can run command to turn off kernel logging to avoid this, but cannot if we cannot enter the test shell 4. Multiple UART may solve this. Do test shell on alternate tty or over ssh 7. [deanb] Using long URLs in notify block causes lava-logs to crash 1. Possibly increase db field length 2. Check the length earlier, fail the job, don’t crash lava logs. 3. Could we make this variable length, maybe? 4. Deanb to put an issue in on git.lavasoftware.org ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

7 years

1
0
0 0

fastboot boot to ramdisk or nfs root filesystem

by Dan Rue

Hi! Anibal and I put together a list of steps that can be used to 'fastboot boot' to a ramdisk or nfs root filesystem in LAVA issue 271[1]. The idea here is to have LAVA create a boot image at runtime based on a kernel, kernel modules, optional ramdisk, and a dtb file. Embedded in the boot image is the kernel command line necessary to boot to a ramdisk or to an nfs root filesystem. This boot image is then run with 'fastboot boot' directly - no flashing required. This is based on discussions related to dragonboard-845 implementation, and would make such boards compatible with kernelci (for example), but also simplify kernel test jobs that don't require a system image to be flashed to the board. We started to look at what would be needed on the LAVA side to implement this, but need help defining the semantics and requirements for the LAVA implementation. I'm also not sure which parts should be in an LXC/docker type context, and which parts should be directly supported in LAVA. I can imagine the rest of the semantics will be very similar or the same to the tftp deploy type. Feedback and LAVA implementation suggestions welcome. Perhaps this can be a topic at the next LAVA design meeting (can I get an invite?). Thanks, Dan [1] https://git.lavasoftware.org/lava/lava/issues/271

7 years

3
3
0 0

device type alias redesign

by Milosz Wasilewski

Hi, There is an idea of device type 'alias' in LAVA. I don't quite understand what the use case for the current implementation was [1]. I tried using it but it wasn't very useful. My use case is that I need to submit jobs to a device type with different device type name. This is used to align device type naming between different labs in a bigger project (kernelci.org in this case). So the questions I have about current implementation: - is there anyone using current implementation? - if current implementation is used, how much trouble would it cause to change the behaviour? Change in behaviour is quite intrusive and will require database migration. [1] https://master.lavasoftware.org/static/docs/v2/glossary.html#term-alias Regards, milosz

7 years

4
4
0 0

Design meeting minutes from 2019-04-24

by Steve McIntyre

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of brief discussion: ## lava-lxc-mocker + db845 booting kernel/dtb/modules [Matt] * Kevin and Matt: how to change binaries before flashing with fastboot? * Should be possible using lxc and lxc:// * See [lxc-sdm845-mtp-test](https://validation.linaro.org/scheduler/job/1912316/de… * Kevin: issue with lava-lxc-mocker inside docker container * [Milosz] Working for [lavasoftware/lava-dispatcher](https://hub.docker.com/u/lavasoftware/lava-di… docker image * Kevin to compare his docker container to lavasoftware/lava-dispatcher ## Replacing lxc protocol by docker (without protocol) [Rémi] * New feature for the near future * Allow for simple deploy.fastboot and boot.adb actions * No need for lxc protocol anymore * With the option (per job) to use a custom docker container ## u-boot commands: nfs vs ramdisk [Rémi] * After [!467](https://git.lavasoftware.org/lava/lava/merge_requests/467), u-boot jobs booting from nfs without a ramdisk are failing. See [meta-lava](https://git.lavasoftware.org/lava/meta-lava/-/jobs/38813). * [!492](https://git.lavasoftware.org/lava/lava/merge_requests/492) fixes this but breaks [cubietruck](https://federation.lavasoftware.org/lava/scheduler/job/361) * Jobs using both ramdisk and nfs will fail (every job booting debian) * Adding a new command: "ramdisk-nfs" ## lavafed and KCI [Rémi] * Presenting lavafed * [Kevin] will this be a problem with multiple dispatchers? * [Rémi] lavafed will see the lab as many sub-labs (one per dispatcher) * [Kevin] is it possible with docker dispatchers? * [Rémi] yes. Install docker-cli and bnd the docker socket in the container. LAVA will then be able to call docker run from inside the container. Rémi to send a mail with the details to kevin ## 2019.04 release [Rémi] * When do we release? * Next Monday * What can be moved to the next release? * See GitLab milestone ## REST API filtering - issue with package dependencies [Milosz] * [failing pipeline](https://git.lavasoftware.org/mwasilew/lava/pipelines/3220) * Looks like a problem when building the debian package * Steve to look at it. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

7 years

1
0
0 0

Design meeting minutes from 2019-04-17

by Remi Duraffort

Hi folks, We held our regular weekly design meeting today via Hangout. Summary of discussion: 1. JS and CSS minifications [Rémi] * Is minification really useful? * Make building more complex * Make debugging difficult * Add potential failures (bugs in the compiler) * Does minify save a lot of bandwidth? If the resources are compressed (using gzip or brotli) then the gain is not significant and not worth the effort. Sounds better to remove the minified version and ensure that the server only send compressed versions whenever possible. 2. ramdisk vs nfs boot in u-boot [Rémi] Some jobs (like [cubietruck]( https://staging.validation.linaro.org/scheduler/job/251164/definition)) provide both a ramdisk and an nfsrootfs while booting with nfs commands. * Is the ramdisk of any use? * Is it possible to remove the command that loads the ramdisk completely? Dean to look at the jobs ARM ran to see any use of this. ============================================================================ The LAVA design meeting is held weekly, every Wednesday at 13:00 to 14:00 UTC using Google Hangouts Meet: https://meet.google.com/qre-rgen-zwc Feel free to comment here or join us directly in the meeting. Minutes from this and previous meetings are also stored in the LAVA wiki: https://git.lavasoftware.org/lava/lava/wikis/design-meetings/index Cheers, -- Rémi Duraffort LAVA Team, Linaro

7 years

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

lava-devel