Yocto has built-in qemu targets for this purpose, and associated infrastructure to start qemu VMs and run tests in them. But to make it practical, these qemu images need to be started on a baremetal L

Not sure what happened here, I published the patches in https://github.com/kanavin/ptest-runner2 Alex

From: Alexander Kanavin <alex@...> In addition to the testresult json, testimage class now also provides task logs and qemu console output (splitted into folders by image name to avoid clutt

The best way is to fix the app. Such major downgrades are firmly uncharted territory, and aren't supported. If you have errors, you need to figure out yourself how to fix them - but if you provide the

I think we might be having an 'unresponsive maintainer' situation? How can Anibal be reached? Alex

For me it's a different use case: archiving the logs regardless of whether things fail or not. They can also be just too large and unwieldy to get printed directly. The patch to testimage.bbclass spli

Currently, ptest-runner simply kills the offending test without further ado, which is not at all helpful when trying to figure out why it happens (especially if such hangs are intermittent and rare).

if poll()'s timeout expires that means the test did not produce any output, which is exactly what we need to catch. So there's no need to set up separate timeouts with signals and alarms, and this gre

I also took the opportunity to correct a weird API that returns a result (or not), depending on some internal condition. Signed-off-by: Alexander Kanavin <alex@...> --- tests/utils.c | 35 ++

There are additional logs there (such as task log or qemu console output), which can be useful for debugging test failures. [YOCTO #14518] Signed-off-by: Alexander Kanavin <alex@...> --- scr

Cheers, will add now. Also, dmesg will be collected and archived through a separate channel, and regardless of whether something is stuck or not :) http://git.yoctoproject.org/cgit/cgit.cgi/poky-contr

Currently, ptest-runner simply kills the offending test without further ado, which is not at all helpful when trying to figure out why it happens (especially if such hangs are intermittent and rare).

if poll()'s timeout expires that means the test did not produce any output, which is exactly what we need to catch. So there's no need to set up separate timeouts with signals and alarms, and this gre

I also took the opportunity to correct a weird API that returns a result (or not), depending on some internal condition. Signed-off-by: Alexander Kanavin <alex@...> --- tests/utils.c | 35 ++

I also took the opportunity to correct a weird API that returns a result (or not), depending on some internal condition. Signed-off-by: Alexander Kanavin <alex@...> --- tests/utils.c | 35 ++

It's right there at the very end: NOTE: Exit code 127. Output: /home/wlsom/YoctoCode/poky/build-microchip/tmp/work/sama5d27_wlsom1_ek_sd-poky-linux-gnueabi/utec-mcdgrill-image/1.0-r0/intercept_scripts

#yocto

I think you need to move the recipe from a workspace to the layer first with 'devtool finish'. When the recipe is in a workspace, it's taking the source code from the workspace as well, and additional

openssl 1.0.2 went out of support at the end of 2019 and you should not be using it. What is the problem you need to solve? Alex

This change is prompted by the recent period where musl patches wouldn't even apply to systemd, which broke half of AUH upgrade attempts. You need to enable systemd/musl on the autobuilder matrix firs

Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- scripts/auh-config/local.conf.append | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/auh-config/local.conf.a