openembedded-core.git/meta/lib/oeqa, branch uninative-1.4 Mirror of openembedded-core oeqa/selftest/base: backup and restore local configuration files 2016-09-23T13:56:17+00:00 Jose Lamego jose.a.lamego@linux.intel.com 2016-09-21T19:54:59+00:00 0877278e07e4c2494c4c23199490dc47a5cee69d Selftests' cleanup method during test setup is not capable of restoring local configuration files that remain modified after aborting a test through a keyboard interruption. This change creates backups for local.conf and bblayers.conf at test setup, restore them when found, and deletes them at cleanup. [YOCTO #9390] Signed-off-by: Jose Lamego <jose.a.lamego@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Selftests' cleanup method during test setup is not capable of
restoring local configuration files that remain modified after
aborting a test through a keyboard interruption.
This change creates backups for local.conf and bblayers.conf at
test setup, restore them when found, and deletes them at cleanup.

[YOCTO #9390]

Signed-off-by: Jose Lamego <jose.a.lamego@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa/selftest/lic-checksum: don't report the expected failure to errors.yp 2016-09-20T14:10:37+00:00 Ross Burton ross.burton@intel.com 2016-09-20T08:13:51+00:00 b2771e17a5f301423f65be9f93c9c1b1e7f8ab93 This test has a bitbake invocation that is expected to fail, so inhibit report-error running. Signed-off-by: Ross Burton <ross.burton@intel.com> 
This test has a bitbake invocation that is expected to fail, so inhibit
report-error running.

Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa/runtime/parselogs.py: Add ignore of tsc calibration fail in x86 2016-09-20T14:10:37+00:00 Aníbal Limón anibal.limon@linux.intel.com 2016-09-19T16:50:19+00:00 2271f59a0f506f89f9fea6777701c4b40790ddd9 We are experimenting failures to calibrate CPU's using TSC in x86 VM's due to usage of nested KVM [1], this is a known issue [2][3] in virtualization environments, for detail explnation see [4]. Also we already have an ignore for 'TSC Fast calibration fail'. [1] http://errors.yoctoproject.org/Errors/Details/83684/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=814231 [3] https://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01547.html [4] https://www.kernel.org/doc/Documentation/virtual/kvm/timekeeping.txt Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
We are experimenting failures to calibrate CPU's using TSC in x86
VM's due to usage of nested KVM [1], this is a known issue [2][3]
in virtualization environments, for detail explnation see [4].

Also we already have an ignore for 'TSC Fast calibration fail'.

[1] http://errors.yoctoproject.org/Errors/Details/83684/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=814231
[3] https://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01547.html
[4] https://www.kernel.org/doc/Documentation/virtual/kvm/timekeeping.txt

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa/sdkext/devtool: use a smaller module to test node.js functionality 2016-09-16T14:15:32+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2016-09-13T02:15:14+00:00 638ee71da967f093071ba25e0ea5c467dab65339 The "forever" package, despite its innocent description, actually drags in a surprising number of dependencies and as a result the nodejs test takes up to 10 minutes as a result. Pick a different example with a much more reasonable set of dependencies. Addresses part of [YOCTO #10254]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
The "forever" package, despite its innocent description, actually drags
in a surprising number of dependencies and as a result the nodejs test
takes up to 10 minutes as a result. Pick a different example with a much
more reasonable set of dependencies.

Addresses part of [YOCTO #10254].

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
qemurunner: print out the runqemu command 2016-09-16T14:15:32+00:00 bavery brian.avery@intel.com 2016-09-09T16:38:54+00:00 34aa20c6f323bbf7ad53beb643126e4e03634708 This logs the launch command that was used for runqemu while running -c testimage. This way, if I'd like to easily launch qemu manually in order to debug a failed test, I know what commmand was run to create the qemu instance. Signed-off-by: bavery <brian.avery@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
This logs the launch command that was used for runqemu while running -c
testimage.  This way, if I'd like to easily launch qemu manually in
order to debug a failed test, I know what commmand was run to create
the qemu instance.

Signed-off-by: bavery <brian.avery@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa/oetest: show stderr when running commands 2016-09-15T21:56:37+00:00 Ross Burton ross.burton@intel.com 2016-09-14T22:14:07+00:00 4cd143e0de7f0082f60f273f442f6255f28ec3e7 To help debug failures, redirect stderr to stdout in oeSDKTest.run() and oeSDKExtTest.run(). Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
To help debug failures, redirect stderr to stdout in oeSDKTest.run() and
oeSDKExtTest.run().

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/utils/decorators: LogResults fix race condition in linkfile 2016-09-15T11:14:40+00:00 Aníbal Limón anibal.limon@linux.intel.com 2016-09-13T20:25:42+00:00 059d475b6bce1e5414170a4fe2e7989f6b0eacd6 In order to avoid race condition when test if exists the linkfile use bb.utils.lock, the best solution is to create a unique name for the link file. There is no way to create a unique linkfile name at this decorator because is needed the machine and image variables, those variables can't be passed easily in this code. To avoid broke test export functionality use a try/except because bb isn't available when use test export [YOCTO #10225] Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
In order to avoid race condition when test if exists the linkfile
use bb.utils.lock, the best solution is to create a unique name
for the link file.

There is no way to create a unique linkfile name at this decorator
because is needed the machine and image variables, those variables
can't be passed easily in this code.

To avoid broke test export functionality use a try/except because bb
isn't available when use test export

[YOCTO #10225]

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Revert "oeqa.runtime.smart: work around smart race issues" 2016-09-14T21:21:24+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2016-09-14T10:46:09+00:00 d3d2d213076b50e88ddc7d4e418ea2ab61b92e67 We have a proper fix now so we can remove the workaround. This reverts commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac. 
We have a proper fix now so we can remove the workaround.

This reverts commit 4d268abc2fc892c5d34449f78c8e9f2b1a9d6bac.
oeqa: Remove linux user utilized for rpm test. 2016-09-13T14:18:43+00:00 Edwin Plauchu edwin.plauchu.camacho@intel.com 2016-09-09T00:16:04+00:00 d1a80ac434bb798634bbb792ff7df59148ec26be When trying to re-test smart rpm tests. A fail arises due to a linux user previously created upon the image. We've added a few lines to delete such user and his home dir when finishing test. [YOCTO #9204] Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
When trying to re-test smart rpm tests. A fail arises
due to a linux user previously created upon the image.
We've added a few lines to delete such user and his home dir
when finishing test.

[YOCTO #9204]

Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
oeqa.buildperf: another fix for splitting 'nevr' string 2016-09-13T14:18:42+00:00 Markus Lehtonen markus.lehtonen@linux.intel.com 2016-09-08T16:47:46+00:00 936eb9aac055f1d4f41bb351477a0f5bebf76a0e When processing buildstats we determine recipe name, epoch, version and revision from the per-recipe buildstat directory name. One previous patch made an assumption that package version starts with a number. That might not be true because of a packaging mistake or whatever reason. Thus, if a version starting with a number is not found, fall back to the "old" method of just taking the second-last dash-delimited part (the one before revision). Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
When processing buildstats we determine recipe name, epoch, version and
revision from the per-recipe buildstat directory name.  One previous
patch made an assumption that package version starts with a number.
That might not be true because of a packaging mistake or whatever
reason. Thus, if a version starting with a number is not found, fall
back to the "old" method of just taking the second-last dash-delimited
part (the one before revision).

Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>