Bug 12082

Summary: [Morty] TCTEMP_2.3_AUTO_oeselftest_eSDK_test_image_generation_binary_feeds
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: Undecided CC: richard.purdie
Version: 2.2.2   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
esdk error none

Description Libertad 2017-09-13 22:04:29 UTC
Created attachment 4008 [details]
esdk error

STATUS: FAILED
BUILD: 2.2.2: rc2-60402978fe3648bf560b3386c6e9dd661cdf2083
ENVIRONMENT: Centos 7.1
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
7. conf/bblayers.conf
8. meta-selftest layer
9. oe-selftest --run-tests eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds

10. oe-selftest --run-tests eSDK.oeSDKExtSelfTest.test_install_libraries_headers




EXPECTED OUTCOME: 

testcases to execute correctly

Note logs are attached
Comment 1 Richard Purdie 2017-09-14 14:54:35 UTC
WARNING: The free space of /tmp/eSDKQAvzdyjzmf/sstate-cache (/dev/sda3) is running low (0.996GB left)
ERROR: No new tasks can be executed since the disk space monitor action is "STOPTASKS"!
WARNING: The free space of /tmp/eSDKQAvzdyjzmf/tmp (/dev/sda3) is running low (0.994GB left)
ERROR: No new tasks can be executed since the disk space monitor action is "STOPTASKS"!
WARNING: The free space of /tmp/eSDKQAvzdyjzmf/downloads (/dev/sda3) is running low (0.994GB left)
ERROR: No new tasks can be executed since the disk space monitor action is "STOPTASKS"!
NOTE: recipe qemu-native-2.7.0-r1: task do_install: Succeeded

The testing machine ran out of disk space while this was being executed?