Thanks. Applied to toaster-next and sent bitbake-devel

On 31/10/16 10:16, Ed Bartosh wrote:
Put instructions on how to prepare event log files
and run eventreplay tests.

Signed-off-by: Ed Bartosh <[email protected]>
---
  bitbake/lib/toaster/tests/eventreplay/README | 22 ++++++++++++++++++++++
  1 file changed, 22 insertions(+)
  create mode 100644 bitbake/lib/toaster/tests/eventreplay/README

diff --git a/bitbake/lib/toaster/tests/eventreplay/README 
b/bitbake/lib/toaster/tests/eventreplay/README
new file mode 100644
index 0000000..8c5bb64
--- /dev/null
+++ b/bitbake/lib/toaster/tests/eventreplay/README
@@ -0,0 +1,22 @@
+# Running eventreplay tests
+
+These tests use event log files produced by bitbake <target> -w <event log 
file>
+You need to have event log files produced before running this tests.
+
+At the moment of writing this document tests use 2 event log files: zlib.events
+and core-image-minimal.events. They're not provided with the tests due to their
+significant size.
+
+Here is how to produce them:
+
+$ . oe-init-build-env
+$ rm -r tmp sstate-cache
+$ bitbake core-image-minimal -w core-image-minimal.events
+$ rm -rf tmp sstate-cache
+$ bitbake zlib -w zlib.events
+
+After that it should be possible to run eventreplay tests this way:
+
+$ EVENTREPLAY_DIR=./ DJANGO_SETTINGS_MODULE=toastermain.settings_test 
../bitbake/lib/toaster/manage.py test -v2 tests.eventreplay
+
+Note that environment variable EVENTREPLAY_DIR should point to the directory 
with event log files.


--
_______________________________________________
toaster mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/toaster

Reply via email to