Glossary of terms

Glossary of terms


[ bundle stream ] [ device group ] [ device owner ] [device status transition ] [ device tag ][ device type ] [ dispatcher ] [ distributed deployment] [ DUT ] [ exclusive ] [ filter ] [ health check ] [hidden device type ] [ hostname ] [ hwpack ] [ logging level ] [ messageID ] [ MultiNode ] [ job definition ] [ offline ] [ pipeline ] [ PDU ][ physical access ] [ priority ] [ refactoring ] [ remote worker] [ result bundle ] [ restricted device ] [ retired ] [ role ] [ rootfs ] [ rootfstype ] [ stream ]

bundle stream
A way of organizing the result bundle. A bundle stream could be imagined as a folder within which all related result bundles will be stored. A bundle stream could be private or anonymous. The shorthand stream is used in job definition to instruct where the results from the job should be submitted. See also Bundle Stream Overview. [1]
device group
A set of devices, defined in the JSON of an individual test job, which will run as a single group of tests within LAVA. Only devices within the group will be able to use the MultiNode API to communicate between devices.
device owner
A device owner has permission to change the status of a particular device and update the free text description of a device. Note that superusers of the LAVA instance are always able to submit jobs to and administer any devices on that instance. See also Device ownership information and Administrative controls.
device status transition
A record of when a device changed Device status, who caused the transition, when the transition took place as well as any message assigned to the transition. Individual transitions can be viewed in LAVA at <server>scheduler/transition/<ID> where the ID is a sequential integer. If the transition was caused by a job, this view will link to that job.
device tag
A tag is a device specific label which describes specific hardware capabilities of this specific device. Test jobs using tags will fail if no suitable devices exist matching the requested device tag or tags. Tags are typically used when only a proportion of the devices of the specified type have hardware support for a particular feature, possibly because those devices have peripheral hardware connected or enabled. A device tag can only be created or assigned to a particular device by a lab admin. When requesting tags, remember to include a description of what the tagged device can provide to a Test Job.
device type
The common type of a number of devices in LAVA. The device type may have a health check defined. Devices with the same device type will run the same health check at regular intervals. See Identifying device types.
A server to which multiple devices are connected. The dispatcher has lava-dispatcher installed and passes the commands to the device and other processes involved in running the LAVA test. A dispatcher does not need to be at the same location as the server which runs the scheduler. [2]
distributed deployment
A method of installing LAVA such that the load of running tests on devices is spread across multiple machines (dispatchers) which each act as a remote worker with a single machine providing the web frontend, master scheduler and database connection. The design of the worker is changing drastically in the refactoring. [2]
Device Under Test - a quick way to refer to the device in LAVA.

The refactoring and the consequent migration means that devices can have three states:

  • JSON only - current dispatcher jobs, pipeline jobs rejected.
  • JSON and Pipeline support - both models supported.
  • Pipeline only - JSON submissions would be rejected.

If the device is marked as pipeline in the admin interface and has a device dictionary, that device can support pipeline submissions. If the device dictionary marks the device as exclusive, then the device can only support pipeline submissions:

{% set exclusive = "True" %}

The state of the device is indicated in the device type and device detail pages. Accepted submissions are marked with a tick, rejected submissions marked with a cross. See also Device ownership information.

Exclusive devices are intended to allow admins and developers to make changes in the refactoring without being limited by having to retain compatibility with the current dispatcher, e.g. to update the bootloader, to support new devices not supported by the current dispatcher at all or to indicate that the devices have completed a migration to the pipeline and prevent users mistakenly submitting old jobs.

It is recommended to have pipeline support for all devices of the relevant device type before enabling exclusive pipeline support, especially if the device type has a V2 type YAML health check job definition.

Within the Dashboard, a filter identifies particular results from a stream or streams. Filters in LAVA can be used to combine test results from multiple bundle streams in a single view and provide the ability to apply attribute filtering as well include or exclude particular tests or test cases. [1]
hacking session
A test job which uses a particular type of test definition to allow users to connect to a test device and interact with the test environment directly. Normally implemented by installing and enabling an SSH daemon inside the test image. Not all devices can support hacking sessions. See LAVA Hacking Sessions (JSON).
health check
A test job for one specific device type which is automatically run at regular intervals to ensure that the physical device is capable of performing the minimum range of tasks. If the health check fails on a particular device of the specified device type, LAVA will automatically put that device Offline. See Writing Health Checks for device types. Health checks have higher priority than any other jobs.
hidden device type
A device type can be hidden by the LAVA administrators. Devices of a Hidden device type will only be visible to owners of at least once device of this type. Other users will not be able to access the job output, device status transition pages or bundle streams of devices of a hidden type. Devices of a hidden type will be shown as Unavailable in tables of test jobs and omitted from tables of devices and device types if the user viewing the table does not own any devices of the hidden type.
The unique name of this device in this LAVA instance, used to link all jobs, results and device information to a specific device configuration.
Linaro style hardware pack. Usually contains a boot loader(s), kernel, device tree blob and ramdisk. [1]
job definition
The original JSON submitted to create a job in LAVA is retained in the database and can be viewed directly from the job log. Although the JSON is the same, the YAML may well have changed since the job was submitted, so some care is required when modifying job definitions from old jobs to make a new submission. If the job was a MultiNode job, the MultiNode definition will be the unchanged JSON from the original submission; the job definition will be the parsed JSON for this particular device within the MultiNode job. [2]

This module is designed to test USB and OTG. It is useful for

  • USB Host hot-plug and functionality confirm
  • USB Host voltage monitoring
  • USB Device hot-plug
  • USB OTG mode sensing by SENSE pin
  • USB OTG role switching

This module is designed to test GPIO, audio hot-plug and SPI bus. It is useful for

  • Boot source selection
  • Switch actuation simulation
  • LED state confirmation
  • Scanned keypress simulation

It provides 2 x 8 level-converted buses configurable as either 3-state outputs suitable for controlling pulled-up or pulled-down wired boot control signals, or level-converted inputs suitable for checking the state of signals. The two 8-bit buses can be independently selected to be input, output or tristate. It also provides a single 4-pin 3.5mm jack connect / disconnect action. This is also compatible with 3-ring 3.5mm jack plugs. All four rings are disconnected, including the 0V one. No connection is made to any of the jack plug signals except the relay switching. So there is no practical limit on the level of analogue or digital signals present or additional load introduced.


This module is designed to test 10/100 Ethernet and SATA. It is useful for

  • 10/100 Ethernet physical connect and disconnect testing
  • SATA logical interface physical connect and disconnect testing

This module is designed to test full-size HDMI. It is useful for

  • HDMI hot-plug test
  • EDID : monitor emulation and activity recording
  • Confirming 5V supply from video source
  • Testing with a programmable hpd delay

This module is designed to do SD-related testing. It is useful for

  • bootloader testing
  • SD card hot-plug testing

This module allows the host and Cortex-M0 chip to control which of two Micro SD cards, A and B, are seen by the DUT at boot time or optionally the host at any time. That should include having one SD card in use by the DUT and the other in use by the host at the same time.

logging level
Various commands within the LAVA test shell operations can be more verbose. The default logging level is INFO and the amount of logging can be increased by setting DEBUG. [1]
Each message sent using the MultiNode API uses a messageID which is a string, unique within the group. It is recommended to make these strings descriptive using underscores instead of spaces. The messageID will be included the the log files of the test.
A single test job which runs across multiple devices. See MultiNode API and MultiNode Use Cases.
A status of a device which allows jobs to be submitted and reserved for the device but where the jobs will not start to run until the device is online. Devices enter the offline state when a health check fails on that device or the administrator puts the device offline.
Power Distribution Unit - a network-controlled set of relays which allow the power to the devices to be turned off and on remotely. Certain PDUs are supported by lavapdu-daemon to be able to hard reset devices in LAVA.
physical access
The user or group with physical access to the device, for example to fix a broken SD card or check for possible problems with physical connections. The user or group with physical access is recommended to be one of the superusers.
Within LAVA, the pipeline is the new model for the dispatcher code as part of the refactoring where submitted jobs are converted to a pipeline of discrete actions - each pipeline is specific to the structure of that submission and the entire pipeline is validated before the job starts. The model integrates concepts like fail-early, error identification, avoid defaults, fail and diagnose later, as well as giving test writers more rope to make LAVA more transparent.
A job has a default priority of Medium. This means that the job will be scheduled according to the submit time of the job, in a list of jobs of the same priority. Every health check has a higher priority than any submitted job and if a health check is required, it will always run before any other jobs. Priority only has any effect whilst the job is queued as Submitted.
remote worker
A dispatcher with devices attached which does not have a web frontend but which uses a connection to a remote lava-server to retrieve the list of jobs for supported boards. [2]
Within LAVA, the process of developing the pipeline code in parallel with the existing code, resulting in new elements alongside old code - possibly disabled on some instances.
restricted device
A restricted device can only accept job submissions from the device owner. If the device owner is a group, all users in that group can submit jobs to the device.
result bundle
A set of results submitted after a testing session. It contains multiple test runs, as well as other information about the system where the testing was performed. [1]
A device is retired when it can no longer be used by LAVA. A retired device allows historical data to be retained in the database, including log files, result bundles and state transitions. Devices can also be retired when the device is moved from one instance to another.
An arbitrary label used in MultiNode tests to determine which tests are run on the devices and inside the YAML to determine how the devices communicate.
A tarball for the root file system.
Filesystem type for the root filesystem, e.g. ext2, ext3, ext4.
Shorthand for a bundle stream used in the submit_results action in the JSON. [1]
test run
The result from a single test definition execution. The individual id and result of a single test within a test run is called the Test Case. [2]
Trivial File Transfer Protocol (TFTP) is a file transfer protocol, mainly to serve boot images over the network to other machines (PXE). The protocol is managed by the tftpd-hpa package and not by LAVA directly. See TFTP support requirement.
[1](1, 2, 3, 4, 5, 6) These terms reflect objects and methods which will be removed after the migration to the new V2 design.
[2](1, 2, 3, 4, 5) These items will be replaced in meaning or detail after the migration to the new V2 design.