From 99992959999ce9f6ad5fdae5a96262a5e0e59b5e Mon Sep 17 00:00:00 2001 From: Patrick Vacek Date: Fri, 17 May 2019 10:32:21 +0200 Subject: Mention oe-selftest usage of ptest. Despite that it is not fully supported in rocko/sumo because of valgrind/openssl and timeout issues. Signed-off-by: Patrick Vacek --- README.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.adoc b/README.adoc index 1aab7dc..01f1c85 100644 --- a/README.adoc +++ b/README.adoc @@ -242,6 +242,8 @@ Be aware that it will add several hundreds of MB to the generated file system. The aktualizr tests will now be part of the deployed ptest suite, which can be run by calling `ptest-runner`. Alternatively, the required files and run script can be found in `/usr/lib/aktualizr/ptest`. +The aktualizr ptests can be run via oe-selftest with `oe-selftest -r updater_qemux86_64_ptest`, but in the rocko and sumo branches, this is not fully supported due to valgrind issues with openssl 1.0.2 and issues with ptest timing out. + == Manual provisoning As described in <> section you can set `SOTA_DEPLOY_CREDENTIALS` to `0` to prevent deploying credentials to the built `wic` image. In this case you get a generic image that you can use e.g. on a production line to flash a series of devices. The cost of this approach is that this image is half-baked and should be provisioned before it can connect to the backend. -- cgit v1.2.3-54-g00ecf