openembedded-core.git/meta/lib/oeqa/runexported.py, branch uninative-1.0

oeqa/runexported.py: Fix exported test

2016-04-12T21:45:33+00:00

With the changes introduced to test the eSDK
the runexported test failed during the execution.

This change fix runexported test in the least invasive
way, because of the release cycle.

Signed-off-by: Mariano Lopez 
Signed-off-by: Richard Purdie

scripts, lib: Don't limit traceback lengths to arbitrary values

2016-03-31T12:18:12+00:00

There appears to have been a lot of copy and pasting of the code
which prints tracebacks upon failure and limits the stack trace to
5 entries. This obscures the real error and is very confusing to the user
it look me an age to work out why some tracebacks weren't useful.

This patch removes the limit, making tracebacks much more useful for
debugging.

[YOCTO #9230]

Signed-off-by: Richard Purdie

oeqa/runexported: Replaced optionparser with argparse.

2015-10-01T16:54:45+00:00

Also added the default json file name as default for
the first positional argument.

Signed-off-by: Lucian Musat 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

oeqa/runexported: Fix a problem with ssh_target_log existing in folder.

2015-09-29T14:15:48+00:00

When copying the exported tests to a remote machine ssh_target_log can
be transformed from softlink to file which will throw an error when
trying to run again.

Signed-off-by: Lucian Musat 
Signed-off-by: Richard Purdie

oeqa/runexported: Removed DEPLOY_DIR as mandatory.

2015-09-23T21:08:13+00:00

We don't need DEPLOY_DIR for every runtime test so there is no
need for it to be mandatory.

Signed-off-by: Lucian Musat 
Signed-off-by: Richard Purdie

runexported: Make it compatible with host dump

2015-09-01T20:47:12+00:00

Currently it is not possible to run a exported test,
but this patch will allow to use the HosDumper class
when running a exported test, otherwise the HostDumper
class will break runexpored test.

[YOCTO #8118]

Signed-off-by: Mariano Lopez 
Signed-off-by: Richard Purdie

lib/oeqa: add module for running tests outside of the build system

2014-02-08T21:00:31+00:00

This script will run the exported tests outside of the build system.

Simplest way to test this is with a qemu image that you manually start.
For an already build image use this in local.conf:
TEST_EXPORT_ONLY = "1"
TEST_TARGET = "simpleremote"
TEST_TARGET_IP = "192.168.7.2"
TEST_SERVER_IP = "192.168.7.1"
Export the tests: bitbake core-image-sato -c testimage
Then: runqemu core-image-sato
And: cd build/tmp/testimage/core-image-sato
     ./runexported.py testdata.json

The contents of build/tmp/testimage/core-image-sato can be moved on another machine
as long as some paths are updated in the json.
The exported data contains paths to the build dir. We only care about DEPLOY_DIR/rpm (
if the rpm and smart tests are enabled), so running the tests on other machine
means that the user has to move the contents and call runexported with --deploy-dir PATH:
 ./runexported.py --deploy-dir /path/on/another/machine testdata.json
runexported.py accepts other arguments as well, see --help.

[YOCTO #5613]

Signed-off-by: Stefan Stanacar 
Signed-off-by: Saul Wold