Now the SDK compatibility tests are implemented but only exec two/five of them because of lack of information about what is installed see bug 9038. https://bugzilla.yoctoproject.org/show_bug.cgi?id=9038 The purpose for this bug is for verify that SDK compatiblity tests works after fix 9038.
Move to 2.2 due to my current load in QA transition.
Move to M3 and assign to Fransisco, he is currently working on eSDK tests.
(In reply to comment #2) > Move to M3 and assign to Fransisco, he is currently working on eSDK tests. Done, merged in master. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0e38688bca3bc52bd95181eb05370d452c447dc7 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1da953d631ab1574c6a9242f2c8ff9cd6b74bcd0
waiting for Paul's inputs bug 9038
I worked on this implementation. Patch sent. I added validation on each SDK compatibility test with eSDK based on generated target and host manifests files as per bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=9038 described (I already sent the patch as well). Waiting for approval. http://lists.openembedded.org/pipermail/openembedded-core/2017-February/133297.html
I sent two more versions due patch test feedback: http://lists.openembedded.org/pipermail/openembedded-core/2017-February/133339.html
Patch is sent, I will move to M4 due delay in revision.
Updated version of the patch sent: http://lists.openembedded.org/pipermail/openembedded-core/2017-June/137866.html
(In reply to comment #9) > Updated version of the patch sent: > http://lists.openembedded.org/pipermail/openembedded-core/2017-June/137866. > html http://lists.openembedded.org/pipermail/openembedded-core/2017-June/137868.html
Waiting for integration, moved to M2.
Reasigned to 2.4 M1, Merged: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=05697aa9418a107e584caa168967e9350d1ea404
validation on each SDK compatibility test with eSDK based on generated target BB_VERSION = "1.34.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal-4.8" TARGET_SYS = "i586-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "2.3" TUNE_FEATURES = "m32 i586" meta-yocto-bsp = "HEAD:05697aa9418a107e584caa168967e9350d1ea404" Test using Pre-Built SDK Installers: 1. Under poky/ do another build folder different from the previous scenario $ source oe-init-build-env build-pre-built 2. Add proper configuration to local.conf $ echo 'SDK_EXT_TYPE = "minimal"' >> conf/local.conf $ echo 'INHERIT += "testsdk"' >> conf/local.conf 3. Create sdk directory $ mkdir -p tmp/deploy/sdk 4. Download artifacts form AB under new folder created $ cd tmp/deploy/sdk $ wget <AB_LINK>/toolchain/x86_64/<ARTIFACTS_NEEDED> Example: $ wget https://autobuilder.yocto.io/pub/releases/yocto-2.4_M3.rc1/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.host.manifest NOTE: All the artifacts that should be downloaded are: - poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.target.manifest - poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.host.manifest - poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh - poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason 5. Give execution permissions to sh files. Rename files, only if it asks. $ chmod +x *.sh $ for file in *<RELEASE>*; do mv "$file" "${file/<RELEASE>/<RELEASE>+snapshot}"; done Example execute below command: $ for file in *2.3*; do mv "$file" "${file/2.3/2.3+snapshot}"; done 6. Go back to poky build folder "poky/build-pre-built" $ cd - 7. Prepare the environment to execute tests $ bitbake libxml2 9. All test should be PASSED 8. Execute the test $ bitbake core-image-minimal -c testsdkext note: log in attchament
Created attachment 4064 [details] log