10824 2016-12-19 14:24:54 +0000 morty-next fails selftest.buildoptions.ImageOptionsTests 2017-01-12 16:16:29 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.2 x86 Multiple RESOLVED FIXED High normal 2.2.1 1 jku akuster meta.mr.watcher meta.watcher richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 69213 0 jku 2016-12-19 14:24:54 +0000 Morty-next fails oeqa.selftest.buildoptions.ImageOptionsTests probably because it's missing this fix for the new uninative build: commit 1969854ec30188940a185ca19fb7c3df81cf8692 Author: Ross Burton <ross.burton@intel.com> Date: Thu Dec 15 19:09:16 2016 +0000 utils: Always use datastore's PATH for host_gcc_version BUILD_CC may reference something like ccache and expect this to come from ccache-native, we at least have some selftests which assume this. Modify the code to use PATH when runnig BUILD_CC to ensure the tests continue to work as expected. (From OE-Core rev: f3e753372baac43d0921186340cf260df056de20) This is the failure from nightly-oe-selftest: ====================================================================== FAIL: test_ccache_tool (oeqa.selftest.buildoptions.ImageOptionsTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/utils/decorators.py", line 109, in wrapped_f return func(*args, **kwargs) File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/buildoptions.py", line 38, in test_ccache_tool bitbake("m4 -c cleansstate") File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/utils/commands.py", line 136, in bitbake return runCmd(cmd, ignore_status, timeout, **options) File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/utils/commands.py", line 114, in runCmd raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, result.output)) AssertionError: Command 'bitbake m4 -c cleansstate' returned non-zero exit status 1: ERROR: Error running ccache gcc --version: /bin/sh: 1: ccache: not found 69214 1 jku 2016-12-19 14:37:36 +0000 I wonder if this is also the reason for the weird devtool test failures: https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/1065/steps/Running%20ESDK%20Sanity%20Tests/logs/stdio The gist of it is: ERROR: Error running gcc --version: ccache: error: Could not find compiler "gcc" in PATH 69755 2 richard.purdie 2017-01-12 16:16:29 +0000 Resolved in morty: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=morty&id=6c5a52ca8f47388a841eab5e3a7703b38bff3ba7