From: dmkhn@proton.me
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
cardoe@cardoe.com, marmarek@invisiblethingslab.com,
dmukhin@ford.com
Subject: Re: [PATCH v1 4/4] CI: add argo x86 XTF test
Date: Thu, 17 Apr 2025 18:37:56 +0000 [thread overview]
Message-ID: <aAFKfhGrs0eFAAEA@kraken> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2504161708470.8008@ubuntu-linux-20-04-desktop>
On Wed, Apr 16, 2025 at 05:11:51PM -0700, Stefano Stabellini wrote:
> On Wed, 16 Apr 2025, dmkhn@proton.me wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > Introduce new CI job to run x86 XTF argo test under QEMU to smoke test argo
> > feature functionality in upstream CI.
> >
> > The new job lead time is ~30s, limit max job duration to 60s.
> >
> > Signed-off-by: Denis Mukhin <dmukhin@ford.com>
> > ---
> > automation/gitlab-ci/test.yaml | 9 +++++++++
> > automation/scripts/include/xtf-runner | 7 +++++++
> > 2 files changed, 16 insertions(+)
> >
> > diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> > index d6e4a0a622..9001efb45c 100644
> > --- a/automation/gitlab-ci/test.yaml
> > +++ b/automation/gitlab-ci/test.yaml
> > @@ -691,6 +691,15 @@ qemu-smoke-x86-64-gcc-efi:
> > needs:
> > - debian-12-x86_64-gcc-debug
> >
> > +qemu-xtf-argo-x86_64-gcc-debug:
> > + extends: .qemu-smoke-x86-64
> > + variables:
> > + TEST_TIMEOUT_OVERRIDE: 60
> > + script:
> > + - ./automation/scripts/qemu-xtf.sh x86-64 pv64 argo 2>&1 | tee ${LOGFILE}
> > + needs:
> > + - alpine-3.18-gcc-debug
> > +
> > qemu-smoke-riscv64-gcc:
> > extends: .qemu-riscv64
> > script:
> > diff --git a/automation/scripts/include/xtf-runner b/automation/scripts/include/xtf-runner
> > index 55b7b34b89..12470b3979 100644
> > --- a/automation/scripts/include/xtf-runner
> > +++ b/automation/scripts/include/xtf-runner
> > @@ -70,6 +70,9 @@ function xtf_build_cmdline()
> > local xtf_variant=$1
> > local xtf_name=$2
> > declare -a cmdline=()
> > + declare -A per_test_args=(
> > + [argo]="argo=1 mac-permissive=1"
> > + )
> > +
> > cmdline+=("loglvl=all noreboot console_timestamps=boot")
> > cmdline+=("console=${XEN_CONSOLE}")
> > @@ -79,6 +82,10 @@ function xtf_build_cmdline()
> > cmdline+=("dom0-iommu=none dom0=pvh")
> > fi
> >
> > + if [[ -v per_test_args[${xtf_name}] ]]; then
> > + cmdline+=("${per_test_args[${xtf_name}]}")
> > + fi
> > +
>
> This is all within the same bash function so I think we could avoid
> using the per_test_args array and just do:
>
> if test "$xtf_name"
> then
> cmdline+=("argo=1 mac-permissive=1")
> fi
>
> The indirection is not required as far as I can tell. I do realize it is
> a matter of taste and it works either way so I wouldn't insist.
Some XTFs may need special configuration.
I added this to be a placeholder for test-specific Xen run-time configuration.
>
>
>
> > export XEN_CMDLINE="${cmdline[@]}"
> > }
> >
> > --
> > 2.34.1
> >
> >
prev parent reply other threads:[~2025-04-17 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 5:32 [PATCH v1 0/4] CI: updates to XTF CI runners dmkhn
2025-04-16 5:32 ` [PATCH v1 1/4] CI: unify x86 XTF test runner dmkhn
2025-04-17 0:16 ` Stefano Stabellini
2025-04-17 18:50 ` dmkhn
2025-04-16 5:32 ` [PATCH v1 2/4] CI: switch x86 EFI smoke test runner to qemu-xtf.sh dmkhn
2025-04-17 0:14 ` Stefano Stabellini
2025-04-17 18:34 ` dmkhn
2025-04-16 5:32 ` [PATCH v1 3/4] CI: switch arm64 XTF " dmkhn
2025-04-17 0:12 ` Stefano Stabellini
2025-04-17 18:51 ` dmkhn
2025-04-16 5:32 ` [PATCH v1 4/4] CI: add argo x86 XTF test dmkhn
2025-04-17 0:11 ` Stefano Stabellini
2025-04-17 18:37 ` dmkhn [this message]
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=aAFKfhGrs0eFAAEA@kraken \
--to=dmkhn@proton.me \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=dmukhin@ford.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.