Bug 12329

Summary: testimage execution interrupted for nightly-x86
Product: [QA/Testing] Runtime Testing Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: generalAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: joshuagloe, randy.macleod, richard.purdie
Version: 2.5   
Target Milestone: 2.5 M1   
Hardware: x86   
OS: Multiple   
See Also: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12183
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Leonardo Sandoval Gonzalez 2017-11-09 14:57:36 UTC 
Log is below, indicating that all tests passed **however** for some reason the execution was interrupted (SIGTERM signal).

-------
core-image-sato-sdk () - Ran 48 tests in 87.559s
core-image-sato-sdk - OK - All required tests passed
NOTE: recipe core-image-sato-sdk-1.0-r0: task do_testimage: Succeeded
WARNING: core-image-sato-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201711090025_qemu
ERROR: core-image-sato-1.0-r0 do_testimage: testimage received SIGTERM, shutting down...
ERROR: core-image-sato-1.0-r0 do_testimage: core-image-sato - FAILED - tests were interrupted during execution
ERROR: core-image-sato-1.0-r0 do_testimage: Function failed: do_testimage
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/build/tmp/work/qemux86-poky-linux/core-image-sato/1.0-r0/temp/log.do_testimage.2160
NOTE: recipe core-image-sato-1.0-r0: task do_testimage: Failed
-------

AB build info:

----------
Build status: FAILURE Build worker for this Build: fedora26.yocto.io
Complete logs for all build steps: https://autobuilder.yocto.io/builders/nightly-x86/builds/595
Build Reason: Triggerable(trigger_main-build)
Build Properties:
• Contents of bblayers.conf (Note. LCONF_VERSION will not show up correctly)
POKY_BBLAYERS_CONF_VERSION =
BBPATH = "${TOPDIR}"
BBFILES ?=""
BBLAYERS &#43;= " \
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/meta \
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/meta-poky \
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86/build/meta-yocto-bsp \
"

• BuildImages : -c populate_sdk_ext core-image-minimal core-image-sato
• DEST : /srv/autobuilder/autobuilder.yoctoproject.org/pub/nightly/20171108-7
• DISTRO : poky
• KEEP_BUILD_HIST : False
• Contents of auto.conf (local.conf for autobuilders)
INHERIT &#43;= "report-error"
DISTRO = "poky"
PACKAGE_CLASSES = "package_rpm package_deb package_ipk"
BB_NUMBER_THREADS = "24"
PARALLEL_MAKE = "-j 28"
SDKMACHINE ?= "x86_64"
BB_TASK_NICE_LEVEL = "5"
BB_TASK_NICE_LEVEL_task-testimage = "0"
BB_TASK_IONICE_LEVEL = "2.7"
BB_TASK_IONICE_LEVEL_task-testimage = "2.1"
DL_DIR = "/srv/autobuilder/autobuilder.yoctoproject.org/current_sources"
SSTATE_DIR ?= "/srv/autobuilder/autobuilder.yoctoproject.org/pub/sstate/"
MACHINE = "qemux86"
PREMIRRORS = ""
BB_GENERATE_MIRROR_TARBALLS = "1"
PRSERV_HOST = "localhost:0"
ADTREPO = "http://adtrepo.yoctoproject.org//2.4"
QEMU_USE_KVM = "True"
SDK_EXT_TYPE = "minimal"
SDK_INCLUDE_TOOLCHAIN = "1"
SANITY_TESTED_DISTROS = ""
-----
Comment 1 Richard Purdie 2017-11-10 16:20:31 UTC 
On the autobuilder, the logs showed the kernel booting up into userspace and X but there was no login prompt in the qemu logs. I've detailed the investigation in https://wiki.yoctoproject.org/wiki/Entropy_on_Autobuilders , the summary is that we need more entropy else userspace doesn't boot as its blocked by rng-tools (which we don't even need).

As an asside, the SIGTERM here is misleading and is a logging issue, this is addressed with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=702f4692a25c670d7d14da106f545b86e55473ce.

The entropy issue has been dealt with by installing rng-tools/haveged onto the autobuilder workers.