From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: rcz@pengutronix.de
Subject: [PATCH 0/5] test: teach pytest the emulate.pl tricks
Date: Mon, 19 Jun 2023 11:52:35 +0200 [thread overview]
Message-ID: <20230619095240.4168216-1-a.fatoum@pengutronix.de> (raw)
test/emulate.pl duplicates a lot of what labgrid is already doing
in order to instantiate virtualized devices and to allow interactive
use of emulated barebox with the same environment config.
In preparation for phasing out emulate.pl, let's teach pytest how to
replace it. As a first step we add these new pytest options:
--interactive start Qemu interactively using labgrid environment
--dry-run print Qemu command line that would've been used
--rng instaiate RNG device
--console instaiate console device
--blk instaiate block device
--qemu=OPT pass OPT to qemu
The intention is to ultimately move as much as possible of this handling
into labgrid itself, e.g. labgrid already has provisions for fixing up
disk options.
Ahmad Fatoum (5):
test: add pytest.ini with defaults
test: have pytest --interactive start interactive Qemu session
test: lookup qemu binary in path if no tools key exists
test: add support for passing devices on command line
test: don't hardcode origin of OVMF.fd
.github/workflows/test-labgrid-pytest.yml | 4 -
pytest.ini | 2 +
test/arm/a15@multi_v7_defconfig.yaml | 4 +-
test/arm/a9@multi_v7_defconfig.yaml | 4 +-
test/arm/multi_v8_defconfig.yaml | 4 +-
test/arm/qemu-raspi0@multi_v7_defconfig.yaml | 4 +-
.../arm/qemu-raspi1ap@multi_v7_defconfig.yaml | 4 +-
test/arm/qemu-raspi2b@multi_v7_defconfig.yaml | 4 +-
.../qemu-sabrelite@multi_v7_defconfig.yaml | 4 +-
test/arm/virt@multi_v7_defconfig.yaml | 4 +-
test/conftest.py | 78 +++++++++++++++++
test/mips/be@qemu-malta_defconfig.yaml | 4 +-
test/mips/le@qemu-malta_defconfig.yaml | 4 +-
test/mips/qemu-malta64el_defconfig.yaml | 4 +-
test/openrisc/generic_defconfig.yaml | 4 +-
test/riscv/qemu-virt64@rv64i_defconfig.yaml | 4 +-
test/riscv/qemu@virt32_defconfig.yaml | 4 +-
test/riscv/sifive@rv64i_defconfig.yaml | 4 +-
test/strategy.py | 87 ++++++++++++++++++-
test/x86/pc@efi_defconfig.yaml | 10 +--
test/x86/q35@efi_defconfig.yaml | 10 +--
test/x86/virtio@efi_defconfig.yaml | 10 +--
22 files changed, 187 insertions(+), 74 deletions(-)
create mode 100644 pytest.ini
--
2.39.2
next reply other threads:[~2023-06-19 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:52 Ahmad Fatoum [this message]
2023-06-19 9:52 ` [PATCH 1/5] test: add pytest.ini with defaults Ahmad Fatoum
2023-06-19 9:52 ` [PATCH 2/5] test: have pytest --interactive start interactive Qemu session Ahmad Fatoum
2023-06-19 9:52 ` [PATCH 3/5] test: lookup qemu binary in path if no tools key exists Ahmad Fatoum
2023-06-19 9:52 ` [PATCH 4/5] test: add support for passing devices on command line Ahmad Fatoum
2023-06-19 9:52 ` [PATCH 5/5] test: don't hardcode origin of OVMF.fd Ahmad Fatoum
2023-06-26 9:55 ` [PATCH 0/5] test: teach pytest the emulate.pl tricks Sascha Hauer
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=20230619095240.4168216-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=rcz@pengutronix.de \
/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