Bug 12080 - [Morty][Test Case 1605] TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
Summary: [Morty][Test Case 1605] TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make
Status: RESOLVED NOTABUG
Alias: None
Product: eSDK
Classification: Yocto Project Subprojects
Component: eSDK (show other bugs)
Version: 2.2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2.2
Assignee: Paul Eggleton
QA Contact: Francisco Pedraza
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-09-13 16:27 UTC by Libertad
Modified: 2017-09-15 17:12 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: Don't know

Attachments
esdk error (13.28 KB, text/plain)
2017-09-13 16:27 UTC, Libertad 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.