From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: Ross Burton <ross.burton@arm.com>, Jon Mason <Jon.Mason@arm.com>
Subject: Running large numbers of testimage tasks in parallel
Date: Thu, 16 Jul 2026 17:35:44 +0100 [thread overview]
Message-ID: <69fa5e90b4238c1c2cc38c82323c009ef0a3eed3.camel@linuxfoundation.org> (raw)
In order to try and attempt to reproduce the autobuilder qemuarm*
hangs, I wanted to share a quick guide on how to hack things to make
running multiple testimage tasks in parallel easy.
Firstly, I added:
BBCLASSEXTEND = "${@' '.join(['mcextend:'+str(x) for x in range(0,100)])}"
to core-image-sato.bb
I then deleted the test case files listed at the end of the email to
make the tests run faster. The hangs are generally in the boot process
before login so if we reach that point, it isn't a hang scenario. I
could have probably set TEST_SUITES instead.
I then ran "bitbake core-image-sato" to get a base image to run the
tests with. After that, I used the following script fragment:
cd tmp/deploy/images/qemuarm64
for i in `seq 1 100`
do
ln -s core-image-sato{,-$i}-qemuarm64.rootfs.manifest
ln -s core-image-sato{,-$i}-qemuarm64.rootfs.ext4.zst
ln -s core-image-sato{,-$i}-qemuarm64.rootfs.testdata.json
done
I could the run 100 testimages in parallel with:
bitbake `for ((i=1; i<=80; i++)); do echo -n "core-image-sato-$i "; done` -c testimage
(which will run BB_NUMBER_THREADS in parallel)
I'm sure there are neater ways to do it but this basically works.
I haven't had any luck reproducing hangs with qemuarm64 with this yet.
I did have to switch from using a DISPLAY over ssh to unsetting DISPLAY
and using qemu's local vnc as otherwise the display traffic over ssh
was limiting the CPU load I could trigger on my server.
Hope someone finds this useful!
Cheers,
Richard
deleted: meta-
selftest/lib/oeqa/runtime/cases/dnf_runtime.py
deleted: meta/lib/oeqa/runtime/cases/_qemutiny.py
deleted: meta/lib/oeqa/runtime/cases/apt.py
deleted: meta/lib/oeqa/runtime/cases/buildcpio.py
deleted: meta/lib/oeqa/runtime/cases/buildgalculator.py
deleted: meta/lib/oeqa/runtime/cases/buildlzip.py
deleted: meta/lib/oeqa/runtime/cases/connman.py
deleted: meta/lib/oeqa/runtime/cases/dnf.py
deleted: meta/lib/oeqa/runtime/cases/ethernet_ip_connman.py
deleted: meta/lib/oeqa/runtime/cases/gcc.py
deleted: meta/lib/oeqa/runtime/cases/gi.py
deleted: meta/lib/oeqa/runtime/cases/go.py
deleted: meta/lib/oeqa/runtime/cases/gstreamer.py
deleted: meta/lib/oeqa/runtime/cases/kernelmodule.py
deleted: meta/lib/oeqa/runtime/cases/ksample.py
deleted: meta/lib/oeqa/runtime/cases/ldd.py
deleted: meta/lib/oeqa/runtime/cases/logrotate.py
deleted: meta/lib/oeqa/runtime/cases/ltp.py
deleted: meta/lib/oeqa/runtime/cases/ltp_compliance.py
deleted: meta/lib/oeqa/runtime/cases/ltp_stress.py
deleted: meta/lib/oeqa/runtime/cases/maturin.py
deleted: meta/lib/oeqa/runtime/cases/multilib.py
deleted: meta/lib/oeqa/runtime/cases/oe_syslog.py
deleted: meta/lib/oeqa/runtime/cases/opkg.py
deleted: meta/lib/oeqa/runtime/cases/pam.py
deleted: meta/lib/oeqa/runtime/cases/ptest.py
deleted: meta/lib/oeqa/runtime/cases/python.py
deleted: meta/lib/oeqa/runtime/cases/rpm.py
deleted: meta/lib/oeqa/runtime/cases/rt.py
deleted: meta/lib/oeqa/runtime/cases/rtc.py
deleted: meta/lib/oeqa/runtime/cases/rust.py
deleted: meta/lib/oeqa/runtime/cases/scons.py
deleted: meta/lib/oeqa/runtime/cases/stap.py
deleted: meta/lib/oeqa/runtime/cases/storage.py
deleted: meta/lib/oeqa/runtime/cases/suspend.py
deleted: meta/lib/oeqa/runtime/cases/systemd.py
deleted: meta/lib/oeqa/runtime/cases/terminal.py
deleted: meta/lib/oeqa/runtime/cases/uki.py
deleted: meta/lib/oeqa/runtime/cases/usb_hid.py
deleted: meta/lib/oeqa/runtime/cases/weston.py
deleted: meta/lib/oeqa/runtime/cases/x32lib.py
reply other threads:[~2026-07-16 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69fa5e90b4238c1c2cc38c82323c009ef0a3eed3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox