On Wed, Jan 25, 2023 at 09:03:03AM +0100, Alexander Kanavin wrote:
> Perhaps you could show a sample output before and after all the changes?

With kirkstone and build config:

MACHINE ??= "qemuarm64"
PACKAGE_CLASSES = "package_ipk"
INHERIT += "rm_work"
INHERIT += "buildhistory"
BUILDHISTORY_COMMIT = "1"
DISTRO_FEATURES:append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
IMAGE_CLASSES += "testimage"
IMAGE_FEATURES += "ssh-server-openssh package-management"
TEST_RUNQEMUPARAMS = "slirp nographic novga"
TEST_SUITES = "\
    ping \
    ssh \
    date \
    df \
    parselogs \
    ptest \
"
QEMU_USE_SLIRP = "1"
# only localhost to access via ssh
QB_SLIRP_OPT = "-netdev user,id=net0,hostfwd=tcp:127.0.0.1:2222-:22"
TEST_SERVER_IP = "127.0.0.1"

With this I compiled core-image-minimal and ran do_testimage:

 * before this patch series: https://pastebin.com/raw/rzhgRGix

 * with this patch series: https://pastebin.com/raw/3R5mUutS

Major difference is that with the series full boot log is do_testimage
task debug output. It's not in bitbake output though, that remains
unchanged. Now if there are any hangs, timeouts or other problems, the
do_testimage logs with the patch series will contain information where
exactly the failure happened. And without this patch series, a hang in
qemu goes undetected and whole test execution hangs, and in multiple
locations: first in test ssh command output select() read() loop for
every command executed on target and then in the QMP debug output
for every ssh command which fails with return value 255.

Cheers,

-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#176346): 
https://lists.openembedded.org/g/openembedded-core/message/176346
Mute This Topic: https://lists.openembedded.org/mt/96401356/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to