10794 2016-12-12 21:43:21 +0000 Update sanity tests to cope with minimal eSDK installer 2017-12-06 17:20:07 +0000 1 1 10 QA/Testing Runtime Testing general 2.3 x86 Multiple RESOLVED FIXED http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=aca3afcb592ef4ff070760ab2aafba03152a57fb Medium+ normal 2.3 M3 10958 9596 1 joshuagloe ross.burton anibal.limon bluelightning francisco.j.pedraza.gonzalez leonardo.sandoval.gonzalez ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 69058 0 joshuagloe 2016-12-12 21:43:21 +0000 After making changes to the autobuilder to build a minimal eSDK we observed unexpected eSDK sanity test failures. This is because the tests implicitly rely on a full eSDK installer, rather than installing any required components into the eSDK before testing. In order to enable minimal eSDK installers on the autobuilder, and therefore for publishing with project releases, we need the eSDK sanity tests to handle running against a minimal eSDK installer. 69829 1 francisco.j.pedraza.gonzalez 2017-01-16 17:09:21 +0000 I just ran: $ . oe-init-build-env $ echo 'SDK_EXT_TYPE = "minimal' >> conf/local.conf $ bitbake core-image-minimal core-image-sato -c populate_sdk_ext $ echo 'INHERIT += "testsdk"' >> conf/local.conf $ DISPLAY=:1 bitbake core-image-minimal core-image-sato -c testsdkext and I successfully could reproduce the error. 69839 2 anibal.limon 2017-01-16 21:07:51 +0000 Hi, Currently there is no way to see what is installed in the extensible sdk see bug [1], so i suggest to add a checking like [2] but this will end in no tests runs on FULL eSDK because of the bug [1]. [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=9038 [2] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdk/gcc.py#n9 69841 3 anibal.limon 2017-01-16 21:08:34 +0000 (In reply to comment #2) > Hi, > > Currently there is no way to see what is installed in the extensible sdk see > bug [1], so i suggest to add a checking like [2] but this will end in no > tests runs on FULL eSDK because of the bug [1]. > > [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=9038 > [2] > http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdk/gcc. > py#n9 I think the missing package is autotools, right Joshua? 69842 4 francisco.j.pedraza.gonzalez 2017-01-16 21:46:47 +0000 (In reply to comment #3) > (In reply to comment #2) > > Hi, > > > > Currently there is no way to see what is installed in the extensible sdk see > > bug [1], so i suggest to add a checking like [2] but this will end in no > > tests runs on FULL eSDK because of the bug [1]. > > > > [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=9038 > > [2] > > http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/lib/oeqa/sdk/gcc. > > py#n9 > > I think the missing package is autotools, right Joshua? Thanks Anibal, working on it. 69875 5 francisco.j.pedraza.gonzalez 2017-01-18 02:26:14 +0000 Implemented the same procedure as sdk/gcc.py if not oeSDKTest.hasHostPackage(" " + machine): skipModule("SDK doesn't contain a cross-canadian toolchain"). Getting good skiping, however I got a regression for "test_extend_autotools_recipe_creation", will check this tomorrow. 69970 6 francisco.j.pedraza.gonzalez 2017-01-20 18:05:41 +0000 (In reply to comment #5) > Implemented the same procedure as sdk/gcc.py > if not oeSDKTest.hasHostPackage(" " + machine): > skipModule("SDK doesn't contain a cross-canadian toolchain"). > Getting good skiping, however I got a regression for > "test_extend_autotools_recipe_creation", will check this tomorrow. I just noticed that gcc is not installed on minimal and that could be the failure. Still working on it. 69977 7 bluelightning 2017-01-20 20:16:14 +0000 Currently that's by design, unless SDK_INCLUDE_TOOLCHAIN = "1" is set. The expectation is that you use devtool exclusively or you install the toolchain using devtool sdk-install. 70066 8 francisco.j.pedraza.gonzalez 2017-01-23 23:17:09 +0000 Created bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=10958 due some issues after modified files at "~/oeqa/sdk/buildiptables.py" and "~/oeqa/sdk/buildcvs.py". That bug blockes this one. 70096 9 francisco.j.pedraza.gonzalez 2017-01-24 21:32:18 +0000 (In reply to comment #7) > Currently that's by design, unless SDK_INCLUDE_TOOLCHAIN = "1" is set. The > expectation is that you use devtool exclusively or you install the toolchain > using devtool sdk-install. Thank you Paul, I just fixed this. Regards 70099 10 francisco.j.pedraza.gonzalez 2017-01-24 21:45:50 +0000 Pushed to contrib: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=fjpedraz/eSDK_sanity_tests 70130 11 francisco.j.pedraza.gonzalez 2017-01-25 17:09:47 +0000 Moved to "In Progress Review" http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131773.html already sent the patch. 70313 12 francisco.j.pedraza.gonzalez 2017-02-01 02:13:46 +0000 Fix commited in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=aca3afcb592ef4ff070760ab2aafba03152a57fb 70962 13 ross.burton 2017-02-27 16:43:33 +0000 https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/1132/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio The tests are not updated for minimal test cases, they just skip some of the tests but not all of them so the tests still fail. In a minimal SDK the SDK has nothing in the sysroot. I think the first thing the tests need to do is populate the SDK sysroot, which means running: $ bitbake <IMAGENAME> -c rootfs- (trailing hyphen) 71139 14 ross.burton 2017-03-08 17:24:39 +0000 oe-core 20c6e876ed6b8c8ac007848e2b36e9a8a56bb703 contains all the fixes.