See merge request !1294

depends on nexedi/erp5!1695

See merge request nexedi/slapos!1290

The coverage of an individual test is after all not useful, only the
coverage of all tests combined is significant.

This replaces the broken --coverage argument from runUnitTest, coverage
needs to be started earlier and also introduces a coverage plugin to
collect coverage data for code in ZODB; python scripts and components
are supported.

To use on test nodes, set up a web dav server somewhere, configure the
instance parameters of the test suite on ERP5 to enable coverage and
upload individual results to this webdav server and then combine the
coverage data and produce a report, using the bin/coverage script from
the software release.

For the steps below, it is necessary to change working directory to the
root of the software folder.

Step 1: combine the coverage data:

    ./bin/coverage combine \
      --keep \
      /path/to/all/coverage/files/*coverage.sqlite3

( using --keep is optional, but it helps in case of mistakes )

Step 2: build an html report:

   ./bin/coverage html \
     --skip-covered \
     --omit parts/erp5/product/ERP5/Document/UnitTest.py \
     --directory /path/for/html/report/

Note that we want to omit UnitTest.py that is created during test
(see testBusinessTemplate.TestDocumentTemplateItem) and get coverage
result because it is executed in the test, but it does not exist as a
source file in the repository, so we skip it.

Of course, to produce a correct html report from a test that have been
running on test nodes, it's necessary that the software release used to
produce the html report has exactly the same version ans the one that
has been running on test nodes.

Another simpler, but slower approach is to run all the tests on the same
machine, then only running step 2 is necessary.

See merge request nexedi/slapos!1288

This reverts commit 4068fd997566035224ffdf5b3e588c767f840b3f.

component/mca: Move obs files from software/mca
software: Delete "mca".

See merge request nexedi/slapos!1230

Add support of the message API (send and receive custom messages between drones).

Manual control is used under the hood to set course to coordinates

Use an update loop to decide the instructions to give to the autopilot.

Use a script passed by the user for the flight instead of a predefined one.

security policy.

We want to sort by filename, which is on second column. The previous value
here was just wrong.

There can be a lot of files in the directories leading to Argument list
too long bash error, so switch to method not involving bash expansion.

See merge request nexedi/slapos!1284

Probably I made a mistake when getting adding this md5sum in
70070a61 . This is not a case where the
checksum changed, we did not have checksum before anyway

See merge request nexedi/slapos!1282

to support git 2.38.1