linux/poky.git/meta/lib, branch 2.7_M3

oeqa/manual/toaster: updated test id naming

2019-03-19T10:40:35+00:00

All test id (eg. @alias) inside manual testcase file shall follow the same test id naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc), where the test id consists of ... Furthermore, there shall be only 1 unique test_module per each manual testcases file, where test_module match the file name itself. This file was using test_module name that does not match the file name itself. Fixed test_module name as well as the test_suite name. (From OE-Core rev: f24178993e7b0830510900e80e879c7f9f8e28f0) Signed-off-by: Yeoh Ee Peng Signed-off-by: Richard Purdie

oeqa/manual/toaster: transfer manual toaster test cases to oeqa

2019-03-18T22:59:58+00:00

As part of the solution to replace Testopia, manual test cases need to be migrated to OEQA. These manual test case json files will serve two use cases. Use case#1: as input to the future commandline-based manual test runner script, where this script will display actions and expected result information in user friendly text, then it will capture user input for test result and log, finally it will write test result and log into existing standardize test result json format from OEQA framework for automated tests. Use case#2: QA will open and read these json file manually for planning manual test execution. Any reader interested in understanding manual test cases will open and read these files. (From OE-Core rev: fbeecb059d9c006f50a2a11bed5a42740722e3e8) Signed-off-by: Yeoh Ee Peng Signed-off-by: Richard Purdie

oeqa/manual/kernel-dev.json: test id updated

2019-03-18T11:12:26+00:00

All test id (eg. @alias) inside manual testcase file shall follow the same test id naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc), where the test id consists of ... Furthermore, there shall be only 1 unique test_module per each manual testcases file. This file was using more than 1 unique test_module for testcases. Furthermore, some of the testcases were defined using different test_suite where it was not needed. This patch fix the manual testcases file to have only 1 unique test_module as well as test_suite to simplify test id naming. (From OE-Core rev: be7cbe86f046bf29082c3da574377f9828aff5f4) Signed-off-by: sangeeta jain Signed-off-by: Richard Purdie

oeqa/manual/compliance-test.json: test id updated and missing test cases added

2019-03-18T11:12:26+00:00

Two changes made in oeqa/manual/compliance-test.json: 1. All test id (eg. @alias) inside manual testcase file shall follow the same test id naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc), where the test id consists of ... Furthermore, there shall be only 1 unique test_module per each manual testcases file. This file was using more than 1 unique test_module for testcases. Furthermore, some of the testcases were defined using different test_suite where it was not needed. This patch fix the manual testcases file to have only 1 unique test_module as well as test_suite to simplify test id naming. 2. Added 2 missing test cases for Beaglebone Stress Test. (From OE-Core rev: 5c5402bc6e6505da0203ca9245a3599bd4940dad) Signed-off-by: sangeeta jain Signed-off-by: Richard Purdie

oeqa/manual/bsp-hw.json: test id updated and obsolete test cases removed

2019-03-18T11:12:26+00:00

Two changes made in oeqa/manual/bsp-hw.json: 1. All test id (eg. @alias) inside manual testcase file shall follow the same test id naming convention from oeqa automated tests (eg. selftest, runtime, sdk, etc), where the test id consists of ... Furthermore, there shall be only 1 unique test_module per each manual testcases file. This file was using more than 1 unique test_module for testcases. Furthermore, some of the testcases were defined using different test_suite where it was not needed. This patch fix the manual testcases file to have only 1 unique test_module as well as test_suite to simplify test id naming. 2. As per review by Intel and Windriver team, 7 testcases were found obsolete. Removed 7 testcases. (From OE-Core rev: e1136bae81672894a277512d7084d27f4e3416b9) Signed-off-by: sangeeta jain Signed-off-by: Richard Purdie

metadata.py: return info after fallback methods

2019-03-07T13:00:40+00:00

If python3 git module is not installed, we fall back to some git command to get info. A previous commit (b8d22ed6) accidently deleted the return statement, causing errors like below. Exception: UnboundLocalError: local variable 'InvalidGitRepositoryError' referenced before assignment (From OE-Core rev: cd8aedc408afa4f8589f79e4d85befc7cac76ac6) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

imagefeatures: Add test to blacklist building busybox

2019-03-06T23:12:27+00:00

Now that we have a packagegroup that can be used to replace the overall functionality of busybox as base-utils, add a test that we can continue to build a fairly complex image without busybox being available. This also doubles as documentation-by-test of how to do this. (From OE-Core rev: 6319a59c1d30eeb8ad4871d43641e3469fb543ba) Signed-off-by: Tom Rini Signed-off-by: Richard Purdie

devtool: Support kmeta directory usage with devtool modify/finish

2019-03-06T10:39:25+00:00

When using Kmeta directories, devtool finish will add every single file in the directory to the bbappend. This is because in the current implementation, the get_recipe_local_files function treats the kmeta directory like a file. Modifying the function to loop through the provided directories and return all included files instead of just the top level directory. This will enable correct file to file comparison when determing which files are new/changed and need to be added to the bbappend. Adding an extra check in devtool-source.bbclass to not copy the cfg file if its already included somewhere in the kmeta directory Also during 'modify', when moving necessary files in the kmeta directory from the workdir to oe-local-files, the dangling parent directories are left behind. This in itself is not an issue as the temporary devtool workspace is automatically deleted, but this causes an incorrect include directory to be added in kernel-yocto.bbclass. Changing the order of the if statements to catch the correct conditional. This is safe to do as when not in the devtool context, there will be no oe-local-files directory. (From OE-Core rev: 4671011b5b02d0989aa0fdcb50e18cb385a0e95e) Signed-off-by: Jaewon Lee Signed-off-by: Alejandro Enedino Hernandez Samaniego Acked-by: Paul Eggleton Signed-off-by: Richard Purdie

masterimage: remove code duplication

2019-03-04T22:57:05+00:00

Two identical classes exist for SystemdbootTarget, introduced in commit f9a61d3400ad ("gummiboot: Remove/change gummiboot references with systemd-boot") poky commit 2dce2648e3d8 Remove the duplicated copy. (From OE-Core rev: a59562c7ddbda1a266f0ea22ab78fb86de4861a3) Signed-off-by: André Draszik Signed-off-by: Richard Purdie

selftest: add tests for virgl GL acceleration

2019-03-04T14:27:06+00:00

Note that the tests require that the host machine has a X display, has mesa development files installed and is able to create OpenGL contexts. (From OE-Core rev: 2868e8dfb9e62b49cd06f6c2d010405079d3a71c) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie