The 2018.10 release has been uploaded to Debian:
https://tracker.debian.org/news/998932/accepted-lava-201810-1-source-all-am…
In due course, that is expected to migrate into buster. 2018.10 might
be the last release to be uploaded to stretch-backports in the Debian
archive because the Debian release process for Buster will be starting
in January.
We have been making a lot of changes to extend and enhance the CI
within the LAVA software upstream processes as part of the move to the
Community Project. This now allows us to support 2018.10 and
subsequent releases to make it easier for labs who don't want to
migrate immediately to the new releases.
2018.10 is also available from the LAVA repositories.
New LAVA repositories
=================
https://master.lavasoftware.org/static/docs/v2/installing_on_debian.html#la…
deb https://apt.lavasoftware.org/release stretch-backports main
deb https://apt.lavasoftware.org/release buster main
The production-repo within Linaro has also been updated at
images.validation.linaro.org - this is the same location as previous
releases.
Snapshots
========
>From 2018.10 onwards, LAVA software will be retaining snapshots of
daily builds of LAVA at https://apt.lavasoftware.org/snapshot/
organised by suite, year, month and date.
Official Docker images
=================
For the first time, LAVA is also releasing official Docker images for
amd64. These are available from lavasoftware.org and from the
lavasoftware organisation on hub.docker.comhttps://master.lavasoftware.org/static/docs/v2/docker-admin.html#administer…
lavasoftware
=========
hub.lavasoftware.org/lava/lava/lava-server:2018.10 2c9b2e36f 155.64 MiB
hub.lavasoftware.org/lava/lava/lava-dispatcher:2018.10 fab86e936 236.85 MiB
hub.docker.com
============
docker pull lavasoftware/lava-dispatcher:2018.10
https://hub.docker.com/r/lavasoftware/lava-dispatcher/tags/
docker pull lavasoftware/lava-server:2018.10
https://hub.docker.com/r/lavasoftware/lava-server/tags/
Changes in this release
==================
I've skipped changes to do with the CI process on lavasoftware.org.
24f6bc296 Support gdb/openocd for disco_l475_iot1
1d1cf4380 Fix resource cleanup when using prefix
7f9796ee1 Append the defined prefix to the udev rule files
1e60552f1 Allow a user-specified kernel failure message
8445444bb device-types: minnowboard: add initrd command to nfs_commands
7c006f458 Ensure build dir exists
0e598e63f Update package version support
0c75c37b9 Distinguish between builds on different suites
135269b50 XMLRPC: use django permissions to manage accesses
dcf5e1358 Fix inconsistent header in docker admin
21f2ddf12 Do not depend on network access for test suites
e74e35b93 docs: Improve wording in various places for new users
579b86bb3 Add docs for IoT boot methods and monitor test action
fab08cc2e docker: allow to use local images
0e0f4d352 Comment out people.l.o and snapshots.l.o urls
f429369bd Support for skipping test shell timeout
32e02b925 Add device-type for qcom QDF2400
368f13217 Help for admins using docker.
829658237 Drop sections on V1 removal
05fcc7f9a docker: allow to use local images
d24c2e756 Fix build errors in docs
d4cfad706 Import the packaging support into upstream
caf3df11e Fix pyocd requirement listing
ae66959a1 Callback add a default timeout to 5 seconds
8e556cbab Compute coverage only on master or for tags
8d928d483 Update documentation for changes in share/requires.py
536b3bab9 Advise use of allow_none in XMLRPC clients
2dc976d28 Update Debian installation instructions for new repo
ddc980704 Allow switching to a binary=any build
59ba58b9c download: Raise an Infrastructure Error on timeout
2e3338ebc Limit excessive exception messages
1f10f2996 Fix undefined variables found by prospector
93529bc64 LAVA-1231 Support multiple boots in QEMU
23f25ee7a Ensure Device.is_valid is checked in submissions
6ca13ea7a Update jobs.list for two bugs found in Linaro
5f36ec668 XMLRPC: allow_none should always be True
f077b620d base-uboot: nbd: handle uboot_set_mac
1d2f38615 Fix arch build instructions in build script.
a6e61d0f9 Update pipeline-admin section on device dicts
5d045edec Isolate dependencies for unit tests
97e55bcf4 Advise against using patterns if POSIX is available
cbdc3ca47 Migrate support links to lists.lavasoftware.org
b34022569 Do not dump python object in description.yaml
42bfd72d3 Update the shebang to python3
ede13f753 Add index entry for persistence
b037a8660 Callbacks replace urllib.request with requests
a5bfdd71e Disable sorting Jobs tables by state
59add5e70 Drop release-queue.py
ecfc5c405 Set InfrastructureError for fastboot-flash-action
8d5679606 Fix imports of JobError from the wrong file
38dc6cace Ensure base-uboot quotes fastboot and adb serial
22f64cb62 Use raw string for regexp
dd5532ee3 Apply black formatting to linaro_django_xmlrpc
819986bd9 Apply black to remaining files in share
9556abc5c Add NBD support for iPXE based DUTs
563b88a00 Keep tags with uppercase letters
74b1d8ca2 Make version string lexicographically sortable
485bca7a6 Improve 359f8278 to support all -misc variants
13fe9a5ec Fix crash when calling lava-server without args
c96946ee9 Fix BootloaderSecondaryMedia.validate() with arbitrary boot commands
9debcf425 Fix warnings during package build
6a9ad82b8 add pytest support to lava-dev
1e0de18dc Fix missing change in the doc after 9595d66e
ee97069da Update Authentication Token page to use lavacli
b52d52b5e Add lava-server manage device-tags
9ae06152c Initial blackening support.
8051f1ddf Silence SAST warnings about mark_safe for internal data.
146e143d4 Apply yaml.safe_load to unit tests
01a3b0c0b Silence SAST noise from unit test
9ac2edac8 Silence security noise from unit test use of assert
c4ad0130a Explicitly set autoescape to False for YAML.
3c359acf3 Point README at new site
b9169d75e Fix typo in the variable names for since
53e21ef20 Update jobs.py
386b9efb7 Add more output to scheduler.jobs.list
a7b7939dd Updates for the contribution guide
fdd55ba63 Improve indexing and linking for device dicts
a956159da Support building for specific suites
9a5aa7e9b Minor doc updates
33f3abf62 Update copyright of docs.
8c6761baa Add gitlab ci configuration
eefc21edc Fix build errors in manpages
5b9ef16d7 Port zmq-client example script to Python3
8cd8cee2a Fix copy/paste error in 65ba876cb5
ce3f6120d Use generator expressions when available
e6f4ef1de Use isinstance() instead of type()
4440cd746 doc: fix most broken links
60928847d Support LXC with IoT
0cc3653f9 Allow LXC for FRDM-K64F IoT device
3bb0819fb Allow the suite to be specified for requirements
dff387150 Fix call to requires.py
7ad9790a8 Move requirements away from pypi tooling
75c928fe1 Remove python2 leftover
359f82786 Add support for qemu-system-misc
65ba876cb Let LXC protocol calls use lists as in base
79312ea8a Upgrade doc examples to Stretch
6a2638fb6 Handle cancelled test jobs in get_recent_jobs
c56ab4c66 Fix logic in pending_jobs_by_device_type
af211db77 LAVA-1398 fix group handling for logrotate support.
cdf4aaec3 Support branch for requires.py
6ff5b43b4 Clarify some of the lavacli doc items
f4948855e Check for download files ending with /
0b25c71bc Port URLs to lavasoftware.org
9871e777c Fix link to api/help location.
571ff39e9 Support ZMQ dependency on lava-common
a7acfc0ae Document architecture restrictions.
393e52fda Fix vland interface code so it works with python3 too
6fc476481 Certificate directory needs to be available in common
e159a369b sample_jobs: fix bbb-initrd-nbd NBD usage
98dfbb377 Add unit test for minnowboard-turbot-E3826 GRUB template
7c01f67a7 device-types: add x86 Minnowboard Max and Turbot using GRUB
2d373d36a documentation: add note about no kernel type attribute for Depthcharge
cc432d33b device-types: define block commands in base-grub.jinja2
5e101d817 run_command: print the output when failing
f019af70d device-types: sunxi-common: support booti
8961645f0 LAVA-1014 add a prefix to tmp directories
b022cde9d Fix indent error
b885dd112 Improve documentation about dispatcher configuration
d9196acd2 LAVA-1397 - fix crash in callback data
55c52bb6d LAVA-1156 When running under pytest, fake requests
c6d61c0e4 Clarify about Debian point releases of Stretch
b051ff1b5 Add missing show_fail after e3cdf814
c4f578e46 Use syslog for lava_lxc_device_add
5f7a22074 Portablility support without using 'os'
e3cdf8140 LAVA-1384 - Add cancel button to definition pages
5693b68b1 Fix sphinx syntax in git describe example
f2f1af5d8 Update filtering of TestJob fields in export
927a28820 Fix error in imx8m change
d484031f7 Use git describe to get the version
b76fe5a1d LAVA-1295 iMX8M evk device integration.
5f3d1769e Allow user to specify the build directory
09d6a90dd LAVA-1380 Drop 'os' from functional test jobs
3af493d42 Update requirement for django-tables
8df4482f0 LAVA-1383 - allow overrides of posix constants
ba035ca72 docker: allow to bind devices
2c507744f Allow for '@' in device name
407db2b45 Revert "Raise a JobError when a cmd output is empty"
f2d4490fd admin: improve listing and update/add page
953df9325 Raise a JobError when a cmd output is empty
baf61b465 Check downloaded file size against expected
ca74a1939 Use OSError when applicable
fc083df5c Use contextlib.suppress when applicable
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
Another step in the LAVA Software Community Project - the lava-users
and lava-announce mailing lists have moved from lists.linaro.org to
lists.lavasoftware.org so that these can be more easily managed within
the LAVA Software Community, outside Linaro.
The configuration is the same but subscribers may need to change their
local filtering rules.
In addition, a new mailing list has been created,
lava-devel(a)lists.lavasoftware.org which is intended for discussions on
design and development issues within LAVA. If you are working on a
merge request for LAVA, this mailing list can be used for a wider
discussion of any issues which don't fit neatly into comments on the
merge request. If you are working on your own device but have not
prepared or created a merge request, please use
lava-users(a)lists.lavasoftware.org as before.
Message headers like List-Id, List-Unsubscribe, List-Archive,
List-Post, List-Help and List-Subscribe simply switch domain from
lists.linaro.org to lists.lavasoftware.org
>From this point onwards, please only send list emails to lists.lavasoftware.orghttps://lists.lavasoftware.org/pipermail/lava-announce/https://lists.lavasoftware.org/pipermail/lava-devel/https://lists.lavasoftware.org/pipermail/lava-users/
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
(There will be a few more messages than usual on announce this month.
Apologies, but I think it's easier to avoid putting everything into one
enormous message.)
As part of the LAVA Software Community Project, there is a new IRC channel
on Freenode aimed at any discussions around LAVA which do not relate to the
use of LAVA within Linaro. The #linaro-lava channel remains open and will
remain focused on discussions of problems and issues relating to LAVA
instances operated by Linaro and other Linaro-centric topics.
Community members are invited to use the new channel to discuss anyting
related to LAVA but not involving Linaro. Questions about your own
instances, problems with new devices and general LAVA development
questions. The new channel should make it is easier to respond to questions
and discuss issues. The existing IRC guidelines apply, as does the LAVA
Software Community Project Code of Conduct.
In addition, when asking questions on #lavasoftware, please include
information on your LAVA setup - include information on the version of LAVA
you are running and, if the instance is publicly-accessible, include the
URL.
As always, complex questions about device integrations will typically
require information like the device-type template, device dictionary and
test job submission definition - you are much better to ask those questions
by subscribing to and posting to the lava-users mailing list.
https://master.lavasoftware.org/static/docs/v2/support.html#irchttps://master.lavasoftware.org/static/docs/v2/code-of-conduct.html#code-of…
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
As part of the move to the LAVA Software Community Project, we will be
moving the hosting of the lava-users and lava-announce mailing lists to the
new server in two weeks - the 16th October.
This will involve changing the URLs of the lists to:
lava-users(a)lists.lavasoftware.org
lava-announce(a)lists.lavasoftware.org
A new list will also appear: lava-devel(a)lists.linaro.org which will support
development of LAVA within the Community Project. Development discussions
relating specifically to Linaro LAVA infrastructure and devices can remain
on linaro-dev(a)lists.linaro.org
If, for any reason, you do not wish to be on the new list, feel free to
unsubscribe between now and the 16th October 2018. All subscribers and
configuration will be migrated to the new location using the configuration
of the lists at lists.linaro.org on that date.
If you decide to stay on the list(s), any filters will need to be updated
on or after the 16th October.
On the day of the migration, there may be a short time when it will not be
possible to post to the current lists. There will be an email from
lava-announce(a)lists.lavasoftware.org when the migration is complete.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
Opening up LAVA development
============================
The LAVA software project has been developed in the open from its very
beginning: Free Software licensing, public discussion spread across IRC and
email, and open access to the software development repositories. The
roadmap and planning behind LAVA development has also become increasingly
open over time, with the use of publicly archived mailing lists and
anonymous access to LAVA issue tracking.
A community of users and contributors has steadily grown up around LAVA.
With the completion of the migration to the V2 codebase, the Linaro LAVA
software team is now moving to a more open development model. We invite new
and existing contributors to be directly involved in planning future
development of the LAVA software project. To this end, Linaro has created
the new LAVA Software Community Project (LSCP) to host and foster LAVA
development with more input and control available to the community. This
removes the need for contributors to register with Linaro, and provides
much more flexibility for LAVA Software development.
The existing Linaro lab in Harston, UK, will remain entirely within Linaro,
providing test infrastructure for Linaro and its members. The sole focus of
the new community project will be LAVA software itself. This will allow the
project to focus on priorities beyond just what Linaro needs, for example
easier integration of devices and new/different use cases. The Linaro
engineers working directly on LAVA software have migrated into a
newly-formed Linaro LAVA Software Team and will act as the founding
maintainers and contributors for the upstream LAVA Software Community
Project. The Linaro LAVA Software Team will still retain access to the
Linaro lab staging instance (https://staging.validation.linaro.org/) for
functional testing using devices available within the Linaro lab.
A new home - https://www.lavasoftware.org
The LAVA Software Community Project (LSCP) has a new home at
https://www.lavasoftware.org.
We have set up initial services there including:
https://www.lavasoftware.org/ - the main website
https://git.lavasoftware.org/ - a GitLab instance to which we have moved
upstream LAVA development
https://master.lavasoftware.org/ - a LAVA master service, available for
development use
Existing LAVA contributors will need to reconfigure their git checkouts
accordingly. The new GitLab instance does not share credentials with the
existing git.linaro.org service; new accounts will be needed - see the
introductory contribution guide
https://master.lavasoftware.org/static/docs/v2/contribution-intro.html and
the full https://master.lavasoftware.org/static/docs/v2/contribution.html
for more details. The former location on git.linaro.org will be archived in
due course.
New repositories exist for the nightly LAVA builds at
https://apt.lavasoftware.org/debian/ (using our existing apt signing key)
and the documentation is being updated to match. The primary location for
test images used in LAVA software functional testing will now be
https://files.lavasoftware.org/; a process to add more files to extend the
functional tests will follow soon. URLs using
http://images.validation.linaro.org/ will continue to be available for a
transitional period.
New mailing lists will also be available soon on the lavasoftware.org site.
There will be a separate announcement about this shortly; subscriptions are
not yet open on the new site.
Contributing to the LSCP
========================
The LAVA Software Community Project has published a Contribution Guide
https://master.lavasoftware.org/static/docs/v2/contribution.html; all
contributors will be expected to adhere to this when submitting issues or
merge requests. These guidelines are designed to clarify the requirements
for contributions, to make contributing more efficient for all involved.
The contribution guide also includes details of how to switch from the old
development process to the new.
We have also adopted a Code of Conduct for the LSCP (
https://www.lavasoftware.org/code-of-conduct.html). All participants in the
LAVA Software Community Project will be expected to communicate and behave
appropriately when working with us.
We request that contributors with currently unmerged Gerrit reviews on
https://review.linaro.org/#/q/status:open+lava/lava should move these
across into merge requests in the new system at
https://git.lavasoftware.org/lava/lava. We will offer help here on request,
but will not automatically migrate them ourselves.
All the outstanding LAVA JIRA stories have been converted into GitLab
issues at https://git.lavasoftware.org/lava/lava/boards. We intend to use
the GitLab workflow for easy integration between CI, issues and merge
requests. At some point in the near future, Linaro will disable the LAVA
projects on Gerrit (https://review.linaro.org/) and JIRA (
https://projects.linaro.org/).
A new way of contributing to LAVA is also under development. A federated
functional testing system for LAVA will allow multiple labs to contribute
to distributed functional testing of LAVA Software, by running specially
designed test jobs on a much wider range of hardware. More details of this
will be announced in due course.
Please ensure that you abide by the Code of Conduct and please read the
contribution guide
https://master.lavasoftware.org/static/docs/v2/contribution.html alongside
this announcement. Discussion of our new project structure is very welcome:
please post to the existing lava-users mailing list at
lava-users(a)lists.linaro.org. Please note that some details of the LSCP are
not yet finalised, so not every question may be answered at this time.
LSCP governance
================
Options for the future governance of the LAVA Software Community Project
are being prepared - more details will follow.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
To improve the functional test framework, we're looking at a mechanism
based on docker and this has had a knock-on effect on how we use git tags.
Previously, tags were made against the release branch. To get this new
support working, we've moved the 2018.7 tag from the release branch to the
master branch.
This does have one effect when using the developer build scripts:
dch: fatal error at line 1092:
New version specified (2018.4.post1-382-gf2f1af5d8-1) is less than
the current version number (2018.5.post1-2)! Use -b to force.
This is due to the tag issue. To fix, use git pull --tag:
neil@sylvester:lava (master)$ git pull --tag
remote: Enumerating objects: 1, done.
remote: Counting objects: 100% (1/1), done.
remote: Total 1 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (1/1), done.
>From gitlinaro:lava/lava
t [tag update] 2018.7 -> 2018.7
Already up to date.
Developer builds will then proceed.
Note that we've changed the version syntax slightly too.
lava_2018.7-17-gf2f1af5d8-1
See
https://staging.validation.linaro.org/static/docs/v2/debian.html#local-vers…
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
This release has not been uploaded to Debian due to an ongoing transition
relating to Python3.7 - see https://tracker.debian.org/pkg/lava and
https://release.debian.org/transitions/html/python3.7.html
The release is available via the LAVA repositories.
A docker container for lava-dispatcher (only) is also available:
https://hub.docker.com/r/linaro/lava-dispatcher-production-stretch-amd64/ta…
LAVA changes
============
6978ad899 Revert "Make primary key non-editable"
a6c34e83f Output a validation error for missing commands:
839a14d07 Create but not edit objects in admin interface
d54b73918 Simplify and rationalise log permissions
0892c0929 Skip deployment_data test if simg2img not installed
34cac8588 worker: add a link to the admin page
f4c85dd27 Cosmetics
baf22688e lava-slave: cosmetics
1d660d9bd Add further fixes for table searching
5903343d4 Rationalise deployment_data for Python3
e298f5acd api: log when updating device/worker health
5572ad267 Exclude Retired devices from warning messages
d874e845c LAVA-1381 CLI to copy an existing device
0736d9d13 Add rk3328-rock64 device type
35594371c Device: set default health to HEALTH_MAINTENANCE
7974b5398 slave: allow to kill the process cleanly
664977da8 Fix notification token after 1a13b85e
2b7e5768c Prevent admins for creating some objects
6383230a6 Make primary key non-editable
f770b0455 Add docs on adding devices in offline state
faa650080 Remove lxc_cmd_prefix from Action class
c0356957b Extend .gitignore for .pytest_cache/
2e124e609 Fix crash when loader yaml description
f037069b3 Make handle_testcase local
138f35d75 Fix bzr tests
425fcaefc Address the Meta data directly
bad4d83c8 device-types: add meson-gxm-khadas-vim2
5ca3ec4f4 Fix crash after 210140b0
d5c05e3c5 dt: improve the warning when hc are disabled
0216c20cc Do not crash when description.yaml is not readable
01faa5d41 Port 41747ab2 to android lava-test-runner
7099b83a1 Add a section on metalava
779a3c826 Add coverage default configuration
ec8c147bd device-types: convert tegra124-nyan-big to Depthcharge
60c137be0 Remove unused sources
7ce3b9d1b device-types: Remove no-op block
f4c557554 Add a few more notes on best practices
9bb6ee3ce Fix crash introduced by 792b63ad
ee379d343 Validate timeout format inside test definition
fa46c7d72 Use reverse relations to break some cyclic-imports
07889e548 LAVA-419 remove google analytics
b89a51557 Allow for 'os' to be optional in deploy actions
5b539c6e2 LAVA-952 per dispatcher configuration
3244fd57f master: remove unused options
1a13b85e7 Move notifications to a specific file
ed44797dc Move django signal handlers to the right module
35ff9e2aa test: remove dependency on instance.conf
30e59f1eb Fix log reading when end < start
ede84bb8f Loosen the check on health check visibility
f38471b6e Raise JobError if commands do not exist
3a6e4895a Some pylint fixes
296ba75cc Outline how to relate a test result to source
8d7afd663 LAVA-960 - remove device-type from device config
8d7de532c Update development notes for new unit tests
8865e27cf Drop functions expecting a JSON job definition
ced34d7dd Fix Python3 support for csv in XMLRPC
3adc5434d Allow to download only some part of the logs
a0312f682 Fix visibility in pending_jobs_by_device_type
210140b0f Remove support for the old v2 format (output.txt)
09288494c Fix lava-logs crashes with invalid test cases
a76b3c14c LAVA-1370 Fix device state when removing TestJob
0e5d01ee7 Update the lava-run example in the docs
792b63ad3 LAVA-1368 provide access to the callback data
59d345080 LAVA-1350 document qemu support in buster
b667d371c LAVA-1367 - drop pretty printing of device dictionary
bbca0922f Remove post_only and use require_POST
c7ede8881 LAVA-1365 - drop call to remote JS
8ca4aae3b Fix undefined variables
92d592816 scheduler.get_pipeline_device_config: fix crash
e005377e3 adb: add missing parameter to super().run
7f00e7de7 logs: write log lines before calling TestJob.save
ef9664aad Link device hostname and device type on devicedict page.
35f251612 Fix misplaced continue, where a return was intended.
4f6ae7e78 Add sdm845-mtp fastboot template support
77fab7605 Add partition:0 to db820c device-type flash order.
eaee79db9 Dont send an os.linesep when interrupting grub
d23ee01f8 Log if udev passes a path outside /dev
f53cd7e9c Update the warning about over-simplifying integration
a5bf77f17 Remove references to python2 and use python3
e9367c747 By default, dict.get() default value is None
5704e19a3 Remove support for django before 1.10
305f019d4 Add a warning to over-simplifying the integration
b528871ca Extend test_recovery to check the -bl template
bae4d6cad Remove duplicated or unused imports
28049de48 Move debian_package_(version|arch) to lava_common
40fcc1d18 Silence known pytest warnings
804bf8715 Make return statement consistent
37a137c32 Fix exception formating
c0f800991 reduce is part of functools in python3
d3531269d Add missing super().run call
2be843f25 Remove python2 code
abb90c380 Fix pytest for lava_scheduler_app
6cae769ac remove unused function
a87ad6d51 Test lava_common.Timeout class
fd8d4a2e9 Remove export PS1 from ssh connections support
e824fd392 Add notes on dependencies needed for unit tests
b6d2bd601 Set the shell prompt in all cases after 5d7c2090
9bd270263 Allow for existing LAVA_DB_NAME containing hyphens
ca7179686 dateutil is missing from server requirements
0679aa426 LAVA-1338 Handle STARTTC, ENDTC and TESTCASE
5d7c20906 LAVA-1120 - drop export PS1 lava-test
9b7ec7120 Use yaml.safe_dump whenever possible
a475c825f Fix crash with old job definitions
087d8ad73 LAVA-1359 Fix lava-publisher shutdown
00747fbe8 Add missing requirement for guestfs in lava-dispatcher
7db4042df Update cirun to avoid sudo
ecafe79b5 LAVA-1361 Fix timeout computation for some actions
e11c8c9f9 Fix job timeout name
9b64f68fd Add example jinja2 files to released tarball.
80703dd4b LAVA-1360 - Investigate Charts Add Query autocompletion
bee1d82d3 Fix order of the log lines when validate fails
b1af0e771 LAVA-1357 - drop include: functionality
5cb96b87c Finalize: ignore exception but log the error
f8a2b520c Fix typo in lava-slave Jobs SQLITE
1cf21c2ed Remove unnecessary Python 2 imports
a1278b6df Remove "args" from Action.run()
306e25d83 Add a glossary entry for BMC
d623748e3 Move import at the begining of the module
cce095f89 Check user rights when returning dt template
d4df5f3d6 Separate the server and dispatcher requirements
15519d598 Add missing import
f5d60ba5c timing: fix parsing with some timeouts
24a1293e2 make device and heathcheck_job pages similar
69c13d3c1 Fix crash when canceling on device without worker
141aeb176 Show an error if a device does not have a worker
4e289f0e3 device-types: add sun50i-h5-libretech-all-h3-cc
9bde1032e device-types: add sun8i-h3-libretech-all-h3-cc
3872951be device-types: add sun8i-h2-plus-libretech-all-h3-cc
934de4f20 No need to test that a dir exists with os.makedirs
1411a019d Use random.SystemRandom() when applicable
c43ac7034 Use CLoader when applicable
4039281ea LAVA-1260 - using Jinja2 templating
48874353a Improve indexing of lava-target-storage
b21810690 Set out plan for functional testing
325309ba9 Fix outdated comments relating to V1 support.
e0a3aaefe Use contextlib.suppress when applicable
0bbe4d381 Check tag support for multiple devices per role
c4ebcfc97 Remove bare except
9aaa115e3 Fix build errors in docs due to removed sections.
661cda0b5 Allow ci-run just for server
0c9cacae3 Remove unicode from yaml definition
2c1b3481d Allow server unit tests to run without nfs-kernel-server
eed71633a LAVA-1354 specify the tests directories for pytest
12fa843aa Improve invalid_template check
218eb19e9 Allow for lava-server without lava-dispatcher
a2fbd0c5b Add lava-lxc-mocker version to log output.
4d02ab538 Skip wait if no kernel_start_message
a2a6715f6 Apply DRY to X15 jinja2 template
306bf6bb5 Fix lxc-create command of lava-lxc-mocker to parse options
correctly.
2965e7427 Use '-q' option whenever apt-get is called.
69a96a268 lava/lxc-mocker: lxc-attach support -v (set var)
371790242 Remove django python2 compatibility code
047912932 Remove __future__ import
f6813e535 Remove python2 specific code
ec2e64b57 Use apt-get instead of apt.
bd4d0b736 context_help is a string not a tuple
63bb7c5cc Remove dummy constructor
316268eca Only use "is" when comparing against None
75300f938 Raise an infra error when guestfs fails to start
8a9f75db2 LAVA-1305 - catch errors in vexpress mcc
a53748c34 Revert "NFS defaults: vers=3"
6ea49f7fb LAVA-1349 fix state machine when canceling and hc
830df97a0 skip some tests if rpcinfo is not available
95036757e Fix crash when env-dut.yaml is defined
50e347aca Change spawnwindowsize to spawn_maxread
74e000108 LAVA-1351 fix addldapuser user_search encoding
3cd50f3ab LAVA-1349 Cancelled health check should not repeat
a72ecbf3e LAVA-1347 allow instances to disable admin Delete
3b88c861c Drop unused setup files.
4110a04a9 Add support for just running the clean task
acd3ccf05 Fix idempotency of decompress_file
93dc46bc5 Allow adding static_devices with no children
93bb55ad8 device-type: khadas-vim: use default uboot prompt
26cd076ab device-types: meson-gx-common: interrupt w/ctrl-c
70db0802c Expand the documentation on setup commands
91d99739d NFS defaults: vers=3
ff1af7f6d Fix: Duplicated Wait for USB
7473b94bc LAVA-1342 - improve docs on character delays
60039c38c LAVA-973 - Create a packaging script for permissions and user
934fdb6b9 Fix map_scanned_results() when test status string is invalid
c0382aeab device-types: meson8b-odroidc1: interrupt with ctrl-c
731e8df49 device-types: base: allow interrupt_ctrl_list for uboot
e737ced93 Split the scheduler API Help by sections
d5ef2f9a6 LAVA-909 convert JSON submissions to YAML
7f3ce8960 LAVA-1262 - document script side effects
a37a30f7b Don't utf8 encode the log data twice
ac6245249 LAVA-1333 fix visibility check for health checks
6ec3ba863 LAVA-1305 - catch errors in vexpress mcc
94c0991d8 Only setup a database once when using pytest
8801f8d26 LAVA-1320 - Add unit test for new minus-lxc jobs
332a40862 Allow limiting the pexpect spawn_window_size
e71ed3760 LAVA-1277 Document lavacli
e504d0666 LAVA-1299 - clarify Bad and Maintenance health
41747ab2f Use /dev/kmsg for LAVA test signals, if requested
7c9d1a0f4 LAVA-836 publish events from a test shell
576aeb896 LAVA-939 Integrate cc3220SF board
b7dbb12d9 device-types: Introduce sunxi-common
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
Advance notice of some changes coming in 2018.7
{% set device_type = 'foo' %} is going away
===========================================
The purpose of any item in the device dictionary or device-type template is
to provide information to lava-run to operate the test job. As far as
lava-run is concerned, the device_type is completely meaningless. Device
type is a database object, a component of scheduling and administration.
So in 2018.7, all device-type Jinja2 templates have been updated to move
this to a comment and the schema has been updated to remove the device_type
field.
If you have local Jinja2 templates which use {% set device_type = 'foo' %},
this needs to be changed to:
{# device_type = 'foo' #}
or if your template uses:
device_type: foo
This needs to be removed or commented out:
# device_type: foo
Any mention of device-type in a device dictionary will be ignored.
This also means that deploying 2018.7 will involve changes to most upstream
device-type templates. If you use an admin tool like salt, ansible, puppet
etc. then it is worth making this change ahead of time. In the Harston lab,
we create a code review against the git repo containing the device-type
templates. When the admin is ready to upgrade a particular instance, the
changes from the review are applied before the package upgrade is started.
This prevents dpkg interrrupting the upgrade with prompts about changed
configuration files whilst keeping the device-type templates under version
control.
Database configuration is now upstream
======================================
Previous releases have relied on the Debian packaging to do the work of
setting up the PostgresQL database and managing database migrations during
installation when a database already exists.
We took this upstream so that we could manage the process in Python instead
of shell, partly because the psql commands require some complex quoting
which is very difficult to read and understand in shell. The other
advantage is to have more eyes on the database setup code and to have
formal code review of changes. In due course, it may also be helpful with
the use of LAVA with docker.
Availability
============
2018.7 is likely to be available on or after 24th July 2018. At that point,
Debian will still be handling the migration to Python3.7 which has caused
issues in a range of Python packages with new keywords.
https://tracker.debian.org/pkg/lava
On request, we will not be uploading 2018.7 directly to Debian unstable
until this transition is complete. As far as we can tell at the moment,
there are no changes required within the LAVA codebase but there are a lot
of Python dependencies which are yet to be fixed. This will also delay the
arrival of 2018.7 into buster and stretch-backports in Debian.
2018.7 will be available from the LAVA repositories on
images.validation.linaro.org once the release is ready. I'll make a
separate announcement with the full list of changes at that time.
--
Neil Williams
=============
neil.williams(a)linaro.org
http://www.linux.codehelp.co.uk/
