Bug 12080

Summary: [Morty][Test Case 1605] TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
Product: [Yocto Project Subprojects] eSDK Reporter: Libertad <libertad.gonzalez.de.la.cruz>
Component: eSDKAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED NOTABUG QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: ross.burton
Version: 2.2.2   
Target Milestone: 2.2.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: Don't know
Attachments:
Description Flags
esdk error none

Description Libertad 2017-09-13 16:27:23 UTC 
Created attachment 4005 [details]
esdk error

STATUS: FAILED
BUILD: 2.2.2: rc2-60402978fe3648bf560b3386c6e9dd661cdf2083
ENVIRONMENT: Debian 8 and Ubuntu
STEPS TO REPRODUCE: 


1. clone poky
2. source oe-init-build-env
3. echo 'SDK_EXT_TYPE = "minimal"' >> conf/local.conf 
4. bitbake core-image-minimal  -c populate_sdk_ext
5. echo 'INHERIT += "testsdk"' >> conf/local.conf
6. bitbake core-image-minimal -c testsdkext



EXPECTED OUTCOME: 

Testcases to execute correctly 


Note log is attached
Comment 1 Ross Burton 2017-09-15 16:11:26 UTC 
Did this fail on the autobuilder, or in your own testing?

Morty eSDKs shouldn't be tested with minimal eSDKs because testsdk doesn't work (fails exactly as you have described).  We changed the test procedure to use minimal eSDKs from Pyro onwards, but the old non-minimal eSDKs should be used for Morty.

Can you retest without the SDK_EXT_TYPE assignment?
Comment 2 Libertad 2017-09-15 17:12:59 UTC 
eSDK passed without the SDK_EXT_TYPE variable, changing the documented Testcases to prevent this confusion. This can be closed.