summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPatrick Vacek <patrickvacek@gmail.com>2019-05-17 10:32:21 +0200
committerPatrick Vacek <patrickvacek@gmail.com>2019-05-17 10:34:49 +0200
commit99992959999ce9f6ad5fdae5a96262a5e0e59b5e (patch)
treef62f36ca4b7b2f26644f9d7f2fdb7e6fdee0154d
parent96c83784087f145c7cada80cbbba16681a887c31 (diff)
downloadmeta-updater-fix/rocko/backport.tar.gz
Mention oe-selftest usage of ptest.fix/rocko/backport
Despite that it is not fully supported in rocko/sumo because of valgrind/openssl and timeout issues. Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
-rw-r--r--README.adoc2
1 files changed, 2 insertions, 0 deletions
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.
242 242
243The 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`. 243The 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`.
244 244
245The 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.
246
245== Manual provisoning 247== Manual provisoning
246 248
247As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> 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. 249As described in <<sota-related-variables-in-localconf,SOTA-related variables in local.conf>> 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.