linux/poky.git/meta/lib, branch uninative-1.7

oe-selftest: wic: change mkfs.btrfs options

2017-07-27T21:36:52+00:00

test_mkfs_extraopts test case fails on ab with error caused by using -K --mixed options: output: extent-tree.c:2696: btrfs_reserve_extent: BUG_ON `ret` triggered, value -28 For this test case it's not important to use particular options, so changing options to anything less influential is OK. Changed extra options for mkfs.btrfs to '--quiet' to fix the failure. (From OE-Core rev: 6a1489f8deb2b26181ca340a0f6ef62aa18a5188) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

oeqa/buildperf: Add 'bitbake -m' on sync function to ensure bitbake is unloaded

2017-07-25T22:15:53+00:00

Add 'bitbake -m' to the sync method and ensure all process related to bitbake are correctly unloaded before doing the different measurements. Also add a call to sync funtion on Test4 before final measurment of eSDK deploy dir disk usage. (From OE-Core rev: 9210c9ce051dfffaa7afa36bb4a926cea289ffd4) Signed-off-by: Jose Perez Carranza Signed-off-by: Richard Purdie

oe-selftest: wic: add test_mkfs_extraopts test case

2017-07-21T21:51:38+00:00

Test new wks option --mkfs-extraopts with all filesystems supported by wic. (From OE-Core rev: 79e853c450708e1e06684cf1216337cbad964770) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe/copy_buildsystem: check_sstate_task_list also pop BBPATH from env

2017-07-21T07:44:25+00:00

The BBPATH environment could be set and can make a failure when try to build an extensible sdk because it will look the bitbake.lock file in the original build folder. Example: $ export BBPATH=`pwd` $ bitbake core-image-minimal -c populate_sdk_ext ERROR: bitbake failed: ERROR: Only one copy of bitbake should be run against a build directory ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Function failed: copy_buildsystem (From OE-Core rev: 33634b4c38d84e1c5d06056766933f1fe4f47e8d) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

oeqa/selftest/{context,case}: Handle KeyboardInterrupt/SIGINT and SIGTERM

2017-07-21T07:44:25+00:00

In order to avoid corrupt local.conf and bblayers.conf adds signal handler for SIGTERM and use try/finally (KeyboardIntrrupt) block to restore previously backuped configuration. [YOCTO #11650] (From OE-Core rev: 9419c81e69d2facc82e39c846466670c09e6b444) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

selftest/cases/package: Call parent setUpClass method

2017-07-21T07:44:25+00:00

Since config paths are now passed in Test context the setUpClass method is expected to be call. (From OE-Core rev: 7281c995ff2b009c3fb23c7af1d91fe106ca8f87) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

oeqa/core/loader: Generate function _make_failed_test dynamically

2017-07-21T07:44:25+00:00

Python versions has different features from branches 3.4.x, 3.5.x and 3.6.x, i expected in wrong mode that was incremental for example changes in 3.4.4 be in 3.5.x but that's not true. The _make_failed_test internal method differs and is only available in certain versions >= 3.4.4 and in 3.5.x and 3.6.x branches but not realeses have been made including it. So to avoid futher problems inspect the _make_failed_test and generates function definition according what parameters are needed, the unique supossition is that exception argument is always passed. Related to, http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d8380d098a290510b442a7abd2dd5a50cabf5844 (From OE-Core rev: b4740d2b325a80bcecc5e56dff9add9081fcd31b) Signed-off-by: Aníbal Limón Signed-off-by: Richard Purdie

oeqa/eSDK: Ignore errors during directory cleanup

2017-07-21T07:44:25+00:00

The cleanup can fail with: ERROR [0.000s]: tearDownClass (eSDK.oeSDKExtSelfTest) FileNotFoundError: [Errno 2] No such file or directory: 'bitbake.sock' which is due to bitbake taking a small amount of time to shut down the server. The easiest fix is just to ignore these kinds of errors, bitbake shouldn't create any new files during shutdown. (From OE-Core rev: 68009f4eb323e07cec8c4421d546bd3125dec033) Signed-off-by: Richard Purdie

sign_rpm: support signing files in RPM payload

2017-07-17T13:01:37+00:00

Currently, RPM4 supports to sign the files in RPM payload with plugin mechanism. We introduce more definitions to make the file signing available for the users: - RPM_FILE_CHECKSUM_DIGEST Global switch to enable file signing. - RPM_FSK_PATH The file signing key. - RPM_FSK_PASSWORD The password of file signing key. - RPM_FILE_CHECKSUM_DIGEST The file checksum digest. (From OE-Core rev: 95b9ee33d5595078e90c633f6155ec9ba3d184f0) Signed-off-by: Lans Zhang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gpg_sign.py: fix overwriting the RPM macro __gpg in a wrong way

2017-07-17T13:01:37+00:00

The RPM macro used in --define option should not be prefixed by %%. (From OE-Core rev: 2fda41cef26b600d599dfb7f2e61c5829e2b309c) Signed-off-by: Lans Zhang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie