You're right, the commit which fixed the issue: https://github.com/SCons/scons/commit/a4ab466c6df5bd3187e78c36bfa8f68e1fb7659e said #4231 so I went with this less cool number (without noticing that my

FWIW: this isn't specific to RISCV64, I had the same in my branch for a while and I was seeing it on qemux86: But it was introduced only in newer gcc-13 snapshots, from my commit message: * since newe

* fixes: https://github.com/SCons/scons/issues/4231 which caused e.g. iotifity to fail in do_compile Signed-off-by: Martin Jansa <Martin.Jansa@...> --- .../python/{python3-scons_4.5.1.bb => pyth

* master branch was removed upstream: downloads/git2/github.com.intel.bmap-tools $ git remote prune origin Pruning origin URL: https://github.com/intel/bmap-tools * [pruned] refs/heads/master * [prune

IIRC we already need buildtools-tarball (regular was enough, not the extended one) for 18.04 because of python Mickledore needs newer python-3.8 (e.g. 3.8.10 in Focal) than 3.6.9 in Bionic since:https

* passing -std=c2x to avoid build failure with gcc-13 on host works as well, but the resulting zic then segfaults when used in tzdata, use a fix from upstream instead * reported upstream in https://mm

meta/classes-recipe/npm.bbclass:85: DeprecationWarning: invalid escape sequence '\.' '--transform', 's,^\./,package/,', Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/classes-recipe/npm

* there are few more autodetected compression libs --disable-zlib disable zlib compression support [default=auto] --disable-bzlib disable bz2lib compression support [default=auto] --disable-xzlib disa

No need, "without meta-selftest included" explains why you haven't fixed it already. I was reading "I run themmanually every now and then." as that you're triggering some special job on AB manually, b

Thanks, can you confirm that git-submodule-test is currently failing for you (and probably was for long time) and that binutils is often reporting failure?

* with 1 preconfigured tap device you cannot run testimage on multiple images at the same time in my case have /tmp/qemu-tap-locks/tap0.skip (tap0 is used by openvpn on builder) and /etc/runqemu-nosud

* I was hit by oe-selftest -r eSDK.oeSDKExtSelfTest.test_install_libraries_headers running all tests except only this selected one: poky $ oe-selftest -v -r eSDK.oeSDKExtSelfTest.test_install_librarie

* skipped modules were triggering an ERROR before: poky $ oe-selftest -v -r eSDK.oeSDKExtSelfTest.test_install_libraries_headers imagefeatures.ImageFeatures.test_image_gen_debugfs -K -B /OE/build/poky

* these cases were correctly respecting IMAGE_LINK_NAME in most tests * the only exception was relatively wide glob for manifest: "test-empty-image-*.manifest" * and even wider glob for -dbg: "*-dbg.r

* to better indicate how it's used in get_first_file * cmd* is used in other places for actual shell commands to execute * RunQemuError('KERNEL not found: %s, %s or %s' % cmds) also looked weird to me

* it's not in self.td causing: 2023-03-12 18:06:29,591 - oe-selftest - DEBUG - Checking if qemux86-64 is not this MACHINE 2023-03-12 18:06:29,594 - oe-selftest - INFO - ... ERROR 2023-03-12 18:06:29,5

* use IMAGE_LINK_NAME instead of hardcoding core-image-minimal-${MACHINE} assumption [YOCTO #12937] Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/lib/oeqa/selftest/cases/minidebuginfo.

* use IMAGE_LINK_NAME instead of hardcoding core-image-minimal-${MACHINE} assumption [YOCTO #12937] Signed-off-by: Martin Jansa <Martin.Jansa@...> --- meta/lib/oeqa/selftest/cases/gdbserver.py |

* to make it easier for projects to avoid default -${MACHINE} suffix if the ${MACHINE} named DEPLOY_DIR_IMAGE works better for them * also use IMAGE_LINK_NAME in IMAGE_NAME to make it more clear that

* use these variables instead of assuming: "fitImage-its-%s-%s-%s" % (image_type, machine, machine) notice that these files have no extension and the -machine suffix is duplicated (once from core-imag