We have a test in meta/lib/oeqa/sdkext/sdk_update.py that tests that sdk-update doesn't outright fail, but it does not verify if the update process actually works i.e. that it's capable of updating an installed SDK when a new one gets published. We need to have this tested so it doesn't regress.
This is currently written as an image test but may be simpler as a selftest. The workflow should look something like this: bitbake -c populate-sdk-ext [some-image] run ${SDK_DEPLOY}/${TOOLCHAINEXT_OUTPUTNAME}.sh oe-publish-sdk [esdk] [path-to-http] IMAGE_INSTALL_appends += [some-lib] bitbake -c populate-sdk-ext [some-image] devtool sdk-update The key is to check that some files have actually be downloaded from the newly appended and published eSDK. The sysroot of that eSDK should contain the updated files.
I will work on this.
Adding the test case on "oe-selftest" at /meta/lib/oeqa/selftest/eSDK.py and working with the "perl" recipe over local.conf
commited to Contrib [1] and running on local AB. [1] - http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=fjpedraz/eSDK_update
(In reply to comment #4) > commited to Contrib [1] and running on local AB. > [1] - > http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=fjpedraz/ > eSDK_update Added an update on contrib due an issue with rebase on master: http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=fjpedraz/eSDK_sdk_update&id=e245d0e49598ac05cc14f752eb9fcfb6fefc1375
Patch sent to OpenEmbedded core lists: http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131234.html Waiting for review.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=51b6df76f2640a3de085e75fe14f96668d6af94a Merged in master.
Assigning to Jair in order to verify this.