lava-announce

lava-announce@lists.lavasoftware.org

141 discussions

LAVA 2025.10

by Remi Duraffort

Hi folks, The 2025.10 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Device-types ## New device-types * acer-cp714-1hn-rex * acer-cpe794-1n-rex * imx8mp-frdm * imx91-11x11-frdm-imx91s * imx943-15x15-lpddr4-evk * imx95-15x15-frdm * k3-am625-verdin-wifi-mallow * mt8196-rauru-navi-sku2 * rk3576-rock-4d ## Removed device-types * aml-s905d3-cc: duplicates of meson-sm1-s905d3-libretech-cc ## u-boot Support dynamic device tree update using fdt command. This feature allows dynamic modifications to the loaded DTB. For example, the device dictionary could include the following to enable the ethernet at runtime on the mt8365-genio-350-evk: ```jinja {% set uboot_fdt_extra_commands = ['fdt set /soc/ethernet status okay'] %} ``` # LAVA Server ## Database migration A new partial index on TestCase table to improve performances when creating the Job Errors page. ## gunicorn optimization Use gunicorn's `--preload` mode to optimize memory usage. The preload mode will load all the Python files before forking the workers. This allows the Python code to be shared in memory between worker processes resulting in less overall RAM being used. ## XMLRPC API Add a new `proxy.scheduler.device_types.devices` endpoint to list the devices of a given device-type. The function allows to filter by device health. # LAVA worker ## Kernel crashes When a kernel panic happens a board can reboot faster than the end of the kernel panic could be printed. This will result the job error becoming `wait for prompt timed out` which is very misleading. In this release, the error message will be `Kernel panic - not syncing` even if matching the end of kernel panic fails. ## Log queue The `lava-run` process is now using a [multiprocessing.Queue]( https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Queue) instead of a pipe to keep pending log lines in memory. `multiprocessing.Queue` uses a unlimited queue as a internal buffer and a separate thread to feed the pipe. It helps prevent job execution from being blocked when logs are not consumed from the pipe in time ## HTTP cache rules This release introduced rules and fallback when using the http caching service option. In the dispatcher configuration, you can now specify 4 different parameters to configure the http caching service, which URL to exclude and include and to fallback or not to the original URL if the caching service failed. ```jinja http_url_format_string: "https://cache.lavasoftware.org/api/v1/fetch?url=%s" http_cache_include_rules: ["https://.*example.com"] http_cache_exclude_rules: ["https://10.*"] http_cache_fallback_origin_url: True ``` ## Log parsing performances Remove the [pexpect](https://pexpect.readthedocs.io/en/stable/) delays for both reading and writing to the DUT serial console. This is improving log parsing speed when a lot of interaction are happening. ## Worker and job cancellation during restart When restarting lava-worker, the process waits for attached lava jobs to finish cleanly. Due to a bug in previous version, canceling such jobs on the LAVA server was not taken into account by the worker. Starting in the release, lava-worker will correctly cancel lava jobs. ## Worker logs Log time in lava-worker and lava-docker-worker log file into UTC. This has been broken since 2018. Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

1 month, 3 weeks

Call for LAVA maintainers

by Remi Duraffort

Hello LAVA users and developers, LAVA has been around and useful for a lot of people for a long time. For some years now, the list of LAVA maintainers as been shrinking down to 2 or even 1 developer (payed by Linaro). In order to review all the patches that the LAVA developers are pushing, we are looking for developers that want to become maintainer. The idea would be to delegate some part of the maintenance of LAVA sub-systems to some developers. If you are interested, please reach out to me in the lava-users ML, privately or in the new LAVA discord server at https://discord.gg/4dVatqyw Thanks for your attention. -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

1 month, 4 weeks

LAVA 2025.06

by Remi Duraffort

Hi folks, The 2025.06 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Device-types ## New device-types * eic7700-hifive-premier-p550 * gs101-oriole (Pixel 6) * s32g399a-rdb3 * spacemit-k1-bananapi-f3 * sun55i-a527-cubie-a5e # lava-worker lava-worker is now waiting for a job to finalize before sending a second signal to a canceling job. This will leave more time for a job to finalize cleanly. # lava-dispatcher actions ## Logs Always save logs to a local file in yaml format. The `logs.yaml` can be used for debugging or post-parsing in the same job with a docker test shell. The log file is saved to dispatcher download directory so that it can be retrieved via the http server using the url `http:// ${LAVA_DISPATCHER_IP}/tmp/${LAVA_DISPATCHER_PREFIX}${LAVA_JOB_ID}/logs.yaml`. Test example: ```yaml - test: docker: image: lavasoftware/lava-dispatcher:latest definitions: - from: inline repository: metadata: format: Lava-Test Test Definition 1.0 name: Job log parsing run: steps: - wget http:// ${LAVA_DISPATCHER_IP}/tmp/${LAVA_DISPATCHER_PREFIX}${LAVA_JOB_ID}/logs.yaml # Steps for additional job log parsing - tail logs.yaml name: job-log-parsing path: inline/job-log-parsing.yaml ``` ## Deploy ### Downloads Add `LAVA_DISPATCHER_PREFIX` to the deploy to downloads shell environment. ### Flasher Allow flasher deploy method to pass `uniquify` parameter for downloading images to a flat directory. ```yaml - deploy: to: flasher images: image1: url: https://example.com/image1 image2: url: https://example.com/image2 uniquify: false ``` ## Boot ### Bootloader custom commands Allow to replace `LAVA_JOB_ID` and `LAVA_DISPATCHER_IP` for custom boot commands. ### Depthcharge Allow to override bot commands in the job definition: ```yaml - boot: method: depthcharge commands: - "exit" ``` ## u-boot Allow chain loading grub. As U-Boot nowadays has full UEFI support it is very common that we chain load grub from U-Boot as UEFI application. Enable to boot from u-boot into grub without resetting the board. # lava-server ## Remote artifact tokens API Add api to manage Remote artifact tokens via XML-RPC or REST. ## Required login Require login in order to access to `/scheduler/reports` and `/scheduler/joberrors` than can be long to generate. With the current bots crawling for data, this can kill a LAVA instance. ## `lava-server manage device-types prune` This command will delete all unused device types from the database. To be considered unused the device type has to have no devices and no jobs that requested it. The extra unused device types slow down certain iterations like health check scheduling. You can call this command from the command line with: ```bash lava-server manage device-types prune --dry-run ``` Rgds. -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

5 months, 1 week

LAVA 2025.04

by Remi Duraffort

Hi folks, The 205.04 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Device-types ## New device-types * aml-s905d3-cc * bcm2837-rpi-3-b-plus * bcm2712-rpi-5-b * mt8188-geralt-ciri-sku0 * qcs6490-rb3gen2 * rk3588-rock-5-itx * supermicro-as-2015hr-tnr ## U-boot device-types Allow adding extra boot methods On system ready devices we usually boot from u-boot into grub. To be able to interact with such a chainloaded bootloader, a device can now use the extra_boot_methods variable. Add the following to a device dict entry: ```jinja {% set extra_boot_methods %} grub: parameters: bootloader_prompt: {{ bootloader_prompt|default('grub>') }} needs_interrupt: {{ grub_needs_interrupt|default(true) }} grub-efi: parameters: bootloader_prompt: {{ bootloader_prompt|default('grub>') }} needs_interrupt: {{ grub_needs_interrupt|default(true) }} {% endset %} ``` # LAVA dispatcher ## Kernel message parsing Look for u-boot start message to detect DUT reset and fail the job. ## Deploy to downloads Save "downloads://*" file to unique path by default. This change unifies the default behavior across the `http(s)://`, `file://` and `downloads://` schemas and it provides the `uniquify` parameter for overwriting. ## Postprocess action Export `HTTP_CACHE`, `LAVA_JOB_ID` and `LAVA_DISPATCHER_IP` as environment variables in the docker container runner post-processing code. `HTTP_CACHE` is also exported to docker test actions. ## Slow serial For device-types with slow or unreliable serial connections, a parameter has been present in LAVA for a long time: `test_character_delays`. This is forcing LAVA to sleep some milliseconds between each characters sent to the serial console. With this release, the lava-test-runner script will now sleep for the same amount of time before sending each test signal. This should help mitigating the impact of these serial connections. ## lava-test-shell Add a new option to pass the output for a given test result, the result will be the same as calling the command with the `--shell` argument. The passed quoted arguments are now properly preserved by lava-test-shell. Previously the arguments had to be quoted multiple times to prevent them being split. Now the argument will be preserved quoted. For example, before `lava-test-shell "some arg"` the `some arg` would be split to to two so the `"'some arg'"` quoting was required. Now `"some arg"` will always be a single argument. This was undocumented change in last LAVA 2024.02 release. # LAVA worker Fix frequent worker offline events. After 2024.09, frequent online -> offline -> online records are observed on most workers. It is a regression introduced by the commit be0f40cbf7c7e95fb03bd83507a84ccaf43d9baf. Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

7 months, 2 weeks

LAVA 2025.02

by Remi Duraffort

Hi folks, The 205.02 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Device-types ## New device-types * imx8dxl-evk-dl2 * imx8dxl-orangebox * imx8mp-ipi-lec * imx8mp-tqma8mpql-mba8mpxl * imx91-11x11-frdm * imx943-19x19-lpddr4-evk * imx943-19x19-lpddr5-evk * mimxrt1170-evk * mimxrt1180-evk * mt8365-genio-350-evk * mt8370-genio-510-evk * mt8395-genio-1200-evk * mt8390-genio-700-evk * mt8395-radxa-nio-12l * mt8188-geralt-ciri-sku1 * mt8188-geralt-ciri-sku2 ## AVH Add support for firmware package. In the job definition, add: ```yaml fw_package: url: https://example.com/kronos-baremetal-psa-secure-storage-1.0.zip storage_file: virtio_0 root_partition: 1 ``` ## fastboot Add support for auto fastboot device detection. If only one fastboot device is attached to a dispatcher, LAVA can now automatically discover the adb and fastboot serial number. In the device dictionary, add: ```jinja {% set fastboot_auto_detection = true %} ``` ## FVP Allow to pass custom environment variables to the FVP binary. In the job definition add `environment: ["HELLO=WORLD"]` ## JLink ### Custom erase and reset commands Allow to customize erase and reset commands. In the device-type template add: ```jinja {% set erase_command = "erase" %} {% set reset_command = "r" %} ``` ## K3 Use common templates for K3 platforms. This template provides `booti` addresses and also set `uboot_ramdisk_format` to `raw` by default. ### Multi-core boards Allow JLink to connect to multi-core boards (e.g. M33 or M7). In the device-type template, a new parameter lists the supported core types. By default, LAVA will connect to the first in the list. ```jinja {% set supported_core_types = ['M33', 'M7'] %} ``` To select another core, specify it in the job definition: ```yaml - boot: method: jlink coretype : "M7" [...] ``` ### QEMU Add `mips64el`, `ppc64le` and `riscv32` to the list of supported architectures. ## u-boot devices Add support for raw initramfs images. For device-type with recent u-boot, use raw ramdisk format by updating the device-type template: ```jinja {% set uboot_ramdisk_format = uboot_ramdisk_format|default('raw') %} ``` # LAVA dispatcher ## Timeout and retries When only deploy/boot/test block timeout is defined, the same timeout is used for all the actions inside the block. When a RetryAction's child action fails on timeout, it leaves no time for the next retry to run as the parent timeout is respected too. This change propagates timeout by levels and retries for retry actions. It uses `parent_timeout // parent_retries` for child action timeout. The logic is similar to setting a smaller named/child action timeout manually. This change might require some adaptations to the timeout. For instance downloads are automatically retried 3 times, so the download timeout will be divided by 3 with this change, allowing for some retries. ## lava-dispatcher-host Make `lava-dispatcher-host` cli startup 3 times faster. This is import as this is used in udev rules. # LAVA server ## Database configuration Allow to set database `CONN_MAX_AGE` and `CONN_HEALTH_CHECKS` from environment variables: ```yaml LAVA_SETTINGS_DB_CONN_MAX_AGE=60 LAVA_SETTINGS_DB_CONN_HEALTH_CHECKS=true ``` Or inside `LAVA_JSON_SETTINGS` with: ``` DB_CONN_MAX_AGE=60 DB_CONN_HEALTH_CHECKS=true ``` ## Notifications Allow to send notification to device owner. In the notification block, add: ```yaml to: user: "{LAVA_DEVICE_OWNER}" ``` ## Scheduler queue timeout Allow to specify a default schedule queue timeout. In the configuration add: ```yaml QUEUE_TIMEOUT_HOURS=5 # In hours ``` Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

9 months, 2 weeks

LAVA 2024.09

by Remi Duraffort

Hi folks, The 2024.09 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Upgrading ## Database migrations This release includes migrations for both lava_scheduler_app and lava_results_app. The migrations add unique constraints to fix potential (and rare) race conditions when receiving and parsing job logs. In order to apply the migrations, the database should not contains TestJobs with duplicated sub_id, TestSets, TestSuites or TestCases. Otherwise the migrations will fail. An helper script as been added as part of this release to **remove test jobs with such duplicates**. The helper **should** be ran **before** running the migrations. ```shell lava-server manage check_uniqueness --yes ``` When using `--yes`, the helper script will automatically **remove** the faulty jobs. # Device-types ## New device-types * imx8mp-debix-model-a * imx91-9x9-qsb * imx93-11x11-frdm * imx95-15x15-ab2 * imx95-15x15-evk * imx95-19x19-verdin * k3-am62p5-sk * qrb4210-rb2-uboot * r8a779f4-s4sk * r9a07g044l2-smarc # Deploy actions # Downloads Make overlay tarball available in downloads. When running postprocess action in "downloads" deployment it is sometimes necessary to use LAVA overlay. Example use case is when running tests on the board without networking. This release makes it possible to, for example, append LAVA overlay to the ramdisk during postprocessing step. ```yaml actions: - deploy: images: image: url: 'https://example.com/Image' dtb: url: 'https://example.com/device.dtb' ramdisk: url: 'https://example.com/ramdisk.gz' timeout: minutes: 5 to: downloads postprocess: docker: image: mkbootimage:master steps: - mkdir lava_overlay - tar xvf overlay*.tar.gz -C lava_overlay - "(cd lava_overlay ; find * | cpio -o -H newc -R +0:+0 | gzip -9 >> ../ramdisk.gz)" - mkbootimg --header_version 2 --kernel Image --dtb device.dtb --cmdline "earlycon clk_ignore_unused pd_ignore_unused audit=0" --ramdisk ramdisk.gz --output boot.img ``` ## Fasboot Allow fastboot devices to use minimal and u-boot boot methods. Some boards like the Qualcomm robotics platforms can run U-Boot by chainloading with fastboot. Add support for using the U-Boot boot method as a second step after "fastboot boot". ## u-boot ### Device tree overlay Add support for device tree overlay when deploying to u-boot with tftp. The resource should be called `dtbo`. ```yaml actions: - deploy: to: tftp dtbo: url: https://example.com/dtb-overlay ``` The support should be added to the u-boot device-type with: ```jinja {% set enable_dtbo_support = 'true' %} ``` Also specify the right addresses with: ```jinja {% set bootm_dtbo_addr = '0x93c00000' %} {% set bootz_dtbo_addr = bootm_dtbo_addr %} {% set dtb_base_resize = dtb_base_resize | default(1048576) %} ``` ### Skip power reset Allow to skip resetting the device for u-boot. Allow user to define a fastboot boot action to load u-boot boot image, and then define a u-boot boot action to run u-boot level boot steps. ```yaml actions: - boot: method: fastboot [...] - boot: method: u-boot reset: false [...] ``` ## USB mass-storage Add a new method to deploy to USB mass storage gadget. This feature requires hardware support on the worker and is currently only available for u-boot DUTs (but can be extended to other DUTs). The device dictionary should include: ```jinja2 {% set usbg_ms_commands = { "disable": ["gadget-ms", "off"], "enable": ["gadget-ms", "on", "{IMAGE}"], } %} ``` The job definition should look like: ```yaml actions: - deploy: to: usbg-ms image: url: https://example.com/.../20231109_raspi_4_bookworm.img.xz compression: zstd format: ext4 partition: 1 overlays: lava: true ``` # LAVA server ## Rest API Add a new endpoint to cancel jobs in batch by POSTing to the endpoint the list of job ids. ## Scheduler When finishing a job, the scheduler will now schedule the next jobs way faster. The process for reporting the end of a job has been improved, reducing the time between two consecutive jobs. Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

1 year, 2 months

LAVA 2024.05

by Remi Duraffort

Hi folks, The 2024.05 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Security issue A security issue as been found by Arnaud Ferraris in the callback code. Every user that can view a job can access to the callback token. We strongly advice to upgrade LAVA to 2024.05 to fix this issue and to revoke every callback token. # Device-types ## New device-types * imx8mn-ddr3l-ab2 * imx91-11x11-evk * imx93-14x14-evk * qrb4210-rb2 * sm8550-hdk * stm32mp157c-lxa-tac-gen1 ## FVP Allow to to import fvp ubl license file. `ubl_license` can be either a license file or a license code now. LAVA runs `armlm activate` for the former and `armlm import` for the latter. ## meson-g12 Add a default `boot_character_delay` of 10ms for all the device-types based on `meson-g12`. ## rk3399-rock-pi-4b Allow to override `boot(i|m)_*` variables. # lava-run When LAVA interacts with a DUT, LAVA uses pexpect to parse the DUT output. Starting from this release, LAVA will better handle logging coming from pexpect and only print the strings sent by LAVA once. # lava-scheduler Improve the `lava-scheduler` performances by lowering the number of SQL requests generated by the scheduling. Also improve performances by improving the job filtering when using tags. # lava-server manage Allow to automatically update a user password from the `lava-server manage` command line. Admins should call ```shell sudo lava-server manage users update --passwd <PASSWD> <USERNAME> ``` # lava-worker lava-worker is now running job cleanups (removing failed job temporary directory) in a specific thread to avoid blocking the main thread for too long. This was causing the lava-worker to be marked offline for some minutes with cleaning large job directories. Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

1 year, 5 months

LAVA 2024.03

by Remi Duraffort

Hi folks, The 2024.03 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Device-types ## New device-types * mt8195-cherry-tomato-r3 ## aaeon-UPN-EHLX4RE-A10-0864 Allow to set `kernel_start_message` variable. ## bcm2837-rpi-3-b Fix the DT load addresses that was potentially overwriting u-boot ATAGs. See [rpi-3-32b fix]( https://gitlab.com/lava/lava/-/commit/afa28d5ae128a591414517edd72652800a72b… ) ## FVP Automatically retry failures when activating the ARMLM license. # APIs ## Rest API The REST API v1 has been removed. The API has been superseded by v2 for a long time now. At the same time, a new version of the API (v3) has been started. This is still an on going work to improve the API performances and reliability. ## XMLRPC ### Devices Allow to update a device `physical_owner` field from the API. Calling `lavacli devices update --user <username>` will update the field. ### Workers Validate yaml syntax before updating the worker configuration. # docker ## lava-dispatcher Use QEMU from bookworm-backports, upgrading from 2.7 to 8.2.1. # Services ## lava-dispatcher-host Improve stability by handling more potential exceptions. ## lava-publisher Improve lava-publisher stability by handling multiple potential connection errors. ## lava-run When sending logs over https fails because the payload is too large, lava-run will automatically reduce the size of the payload before retrying. Before this version, lava-run would retry with the exact same payload (or sometime even larger one) and will be unlikely to ever succeed. When failing to send logs to the server, lava-run will also record the error to stderr. lava-worker will then forward these messages to the server. This will be recorded as failure_comment. ## lava-server-gunicorn Switch gunicorn default worker from eventlet to gthread. With eventlet, the event notification system (based on ZMQ socket) will need to create a new socket for each connection. If the publisher service is unreachable, the server will consume all the file descriptors and crash after some time. gthread worker allows to reuse the same zmq socket for multiple requests while still allowing requests to live longer than the worker timeout. Regarding the performances, the apache bench test results shown that gthread is able to handle more concurrent connection than eventlet in most use cases. ## lava-server cli A new argument has been added to the `lava-server jobs rm` command: `--logs-only`. When this parameter is set, the command will only remove the logs from the filesystem while keeping the TestJob objects in the database. Rgds -- Rémi Duraffort Principal Tech Lead LAVA Tech Lead Automation Software Team Linaro

1 year, 8 months

LAVA 2024.01

by Chase Qi

Hi folks, The 2024.01 tag has been pushed to master on gitlab.com/lava/lava. .deb packages have been built in GitLab CI and are published at https://apt.lavasoftware.org/release Docker images for amd64 and arm64 have been built in GitLab CI and are available from https://registry.gitlab.com/ and https://hub.docker.com/u/lavasoftware Changes in this release ================== # Upgrading ## Database migrations This release includes one migration in lava_scheduler_app. Remote artifact token max length is increased from 100 to 200 for super-long API tokens. # Device-types ## New device-types New supported devices: * stm32mp157a-dhcor-avenger96 * meson-g12b-a311d-libretech-cc * meson-sm1-s905d3-libretech-cc * imx93-11x11-evk-pmic-pf0900 * avh(Arm Virtual Hardware) * imx95-19x19-evk * dell-latitude-3445-7520c-skyrim * mt8186-corsola-steelix-sku131072 ## NXP Download addresses for i.MX8 are updated to match those shipped in the firmware for i.MX8MP-EVK which has been continuing to work happily. The old addresses no longer give enough room to avoid them overwriting each other. # LAVA publisher IPV6 is supported in ZMQ events now. Adding the following line in server settings enables IPV6 support. ```yaml EVENT_IPV6: true ``` # LAVA scheduler * Improve device's Jinja template performance by using a shared Jinja environment. The template cache will be shared between HTTP requests and no longer spend time to compile templates for every request. For example, when a dispatcher downloads job from the server the template has to be rendered with a job's context. * Record worker health transitions. Worker online and offline state changes are logged and displayed now. # REST API The `/device/validate` endpoint now requires "add_device" permission. # Deploy and boot methods ## avh New AVH deploy and boot methods are added for integrating Arm Virtual Hardware in LAVA. Example: ```yaml device_type: avh job_name: avh-rpi4b-deploy-boot-example timeouts: job: minutes: 60 priority: medium visibility: public secrets: # The value should be the name of user's remote artifact token avh_api_token: remote_artifact_token_name actions: - deploy: to: avh options: model: rpi4b api_endpoint: https://app.avh.arm.com/api project_name: "Default Project" timeout: minutes: 30 images: rootfs: # Disk image. url: https://example.com/rpi4b/nand format: ext4 # root partition for LAVA test overlay. root_partition: 1 # Partition for custom overlays. partition: 1 overlays: modules: compression: xz format: tar path: / url: https://example.com/rpi4b/modules.tar.xz kernel: url: https://example.com/rpi4b/kernel dtb: url: https://example.com/rpi4b/devicetree - boot: method: avh timeout: minutes: 20 prompts: - "pi@raspberrypi:" - "root@raspberrypi:" auto_login: login_prompt: "login:" username: pi password_prompt: 'Password:' password: raspberry login_commands: - sudo su ``` ## fvp Added buffering to the model stdout and stderr. Without this buffering, the model sometimes hangs when stdout or stderr buffers are full. ## fastboot DUT will be powered off when fastboot timeout. On some devices, the fastboot command will never return and is not killable. This might block lava-run forever. Powering-off the DUT will release fastboot command. ## uuu * Fixed individual action timeout not being respected in boot-corrupt-boot-media. * Disconnect device after uuu boot action to flush the output buffer. ## download Allow to turn off kisscache at job level. Example: ```yaml - deploy: timeout: minutes: 5 to: tmpfs images: rootfs: use_cache: false ``` # LAVA dispatcher ## Git clones Added 6 times retries for git clone function. It could be helpful for infrastructure level one time failure. ## DUT output In case it is needed by post-processing out of LAVA, single `\r` character in pexpect output is not stripped off anymore. ## Test definition parameters Fixed test definition parameter `0` being converted to the empty string. LAVA dispatcher converts both key values `None` and `0` to `''` before. Now only `None` is converted. Example: ```yaml - test: timeout: minutes: 5 definitions: - repository: http://git.linaro.org/lava-team/lava-functional-tests.git from: git path: lava-test-shell/smoke-tests-net.yaml name: smoke-tests parameters: USE_NC: 0 ``` `USE_NC: 0` was converted to `USE_NC=''` in the `run.sh` shell script before. It is now converted to `USE_NC='0'`. Rgds -- Chase Qi Senior Engineer Automation Software Team Linaro _______________________________________________ lava-announce mailing list -- lava-announce(a)lists.lavasoftware.org To unsubscribe send an email to lava-announce-leave(a)lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

1 year, 10 months

LAVA migration to gitlab.com/lava

by Remi Duraffort

Hello Everyone, for more than 5 years now, the LAVA gitlab server has been hosted and maintained by Linaro in the Cambridge lab. We recently decided to migrate the LAVA project source code to gitlab.com as gitlab is providing licenses for OSS projects like LAVA (and the server is getting older). The migration has been finished today. Every projects are now in the LAVA namespace at https://gitlab.com/lava/ For instance: * lava: https://gitlab.com/lava/lava/ * lavacli: https://gitlab.com/lava/lavacli/ * lavafed: https://gitlab.com/lava/lavafed/ * meta-lava: https://gitlab.com/lava/meta-lava/ * ... You need to change the git configuration to point to gitlab.com instead of git.lavasoftware.org. As the migration process does not migrate the pipeline data, if you have open MRs, please rebase and update them. If you need access, please create a username on gitlab.com and request access. Best regards -- Rémi Duraffort Principal Tech Lead Automation Software Team Linaro

2 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-announce