LQA(1)
π LQA(1) π
the LAVA quality assurance tool β yes bestie, we're doing this, it lives in manual section 1 and it's from the LAVA crew π
β¨ NAME β¨
lqa β a command line tool for LAVA quality assurance tasks π¦
πΈ SYNOPSIS πΈ
lqa [-h] [-c CONFIG.yaml] [--log-file=LOG_FILE] COMMAND β¦
π DESCRIPTION π
okay so, lqa (aka the LAVA QA Tool) is a command line tool for LAVA quality assurance tasks. that's the whole vibe, that's the assignment, periodt π
TBE
β OPTIONS β
these ones are the common options, meaning every single command gets them, no exceptions bestie π
--log-fileLOG_FILE β write logs to LOG_FILE. yes, all of them, into that file π-c<CONFIG.yaml>,--config=<CONFIG.yaml> β use configuration from CONFIG.yaml. your settings, your rules π«Ά-h,--helpβ show a short help message and exit. the classic escape hatch π
π COMMANDS π
here's the whole roster, and bestie, there are a lot of them. we're going through every single one π
π submit β submit job files
lqa submit [-h] [-g PROFILE.yaml] [-n] [-p PROFILE]
[--all-profiles] [-t TEMPLATE_VARS] [-v] [--wait [TIMEOUT]]
[--debug-vars] [--priority {high,medium,low}] [--check-image-url]
[JOB_FILE.{yaml,json} [JOB_FILE.{yaml,json} ...]]
and here's what all of that means, one by one π
-h,--helpβ show this help message and exit-g<PROFILE.yaml>,--profile-file<PROFILE.yaml> β set profile file-n,--dry-runβ dry-run, do everything apart from submitting. it's giving rehearsal energy, no actual commitment π-pPROFILE,--profilePROFILE β specify the profiles to use (can be given multiple times). stack 'em up, the more the merrier β¨--all-profilesβ process all the available profiles. every single one, no cap π-tTEMPLATE_VARS,--template-varsTEMPLATE_VARS β set'field:value'template variables/values (can be given multiple times)-v,--verboseβ verbose mode (e.g. print the resulting json). she's chatty and we love that for her π¬--waitTIMEOUT β wait for submitted jobs to complete using a TIMEOUT value (Default timeout of 3 hours). yes, 3 hours, go grab a snack π--debug-varsβ debug undefined template variables π--priority<high,medium,low> β set the job priority--check-image-urlβ check that the image url exists before submitting job. safety first, always π‘οΈ
π cancel β cancel job id
π resubmit β resubmit job id
π§΅ mkstream β create bundle stream
β³ wait β wait for job id
π status β show job id status
π₯ output β fetch job id output log
ποΈ job β get information for job id
π§ͺ test β show test information
π diffresults β show test results differences
π report β generate report for job id's
π results β get (raw) results
π jobdef β show job definition file
π¦ queue β show the current queue of running and submitted jobs
π§Ή cleanqueue β clean jobs queue
π§ maint β put the given device in maintenance mode
π’ online β put the given device into online mode
π» devices β show status of all available devices
π liststreams β show streams the user has access to
πͺͺ whoami β show authenticated user name
π·οΈ sversion β show LAVA server version
π SEE ALSO π
...(1)
ποΈ AUTHOR ποΈ
Luis Araujo <luis.araujo@collabora.co.uk>, Andrew Shadura <andrew.shadura@collabora.co.uk> β absolute icons, both of them ππ
and that's the whole page bestie!! π«Ά this was LQA(1) from the LAVA fam, version 20161215.0, dated 2017-01-05 β go forth and QA slay π
β¨
π¦ where this page comes from
- debian bookworm: lqa 20230104~git9be8db8ab65c-1 Β· LGPL-2.1-or-later
- debian trixie: lqa 20230104~git9be8db8ab65c-2 Β· LGPL-2.1-or-later
- ubuntu jammy: lqa 20210324~git9fff6ab09969-2 Β· LGPL-2.1-or-later
- ubuntu noble: lqa 20230104~git9be8db8ab65c-1 Β· LGPL-2.1-or-later
- ubuntu questing: lqa 20230104~git9be8db8ab65c-2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms