From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [PATCH v2 4/4] automation: add tools/tests jobs on the AMD Zen3+ runner too
Date: Sat, 15 Feb 2025 01:54:14 +0100 [thread overview]
Message-ID: <Z6_lt1Kd9ELpmv5e@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2502141629420.3858257@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 2415 bytes --]
On Fri, Feb 14, 2025 at 04:33:07PM -0800, Stefano Stabellini wrote:
> On Fri, 14 Feb 2025, Marek Marczykowski-Górecki wrote:
> > Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> > ---
> > new in v2
> > If those tests are sensitive to underlying hardware, I guess it makes
> > sense to run them on other runners too. Are they?
> > Similarly - does it matter if dom0 is PV or PVH for those tests? If not,
> > probably better to put just one of those jobs (PV?) to save CI
> > time.
>
> It should make a difference for the vpci test probably. I think we
> should keep both a PV and a PVH test of it. I think it is less important
> to run them on multiple runners, but it cannot hurt.
>
> > ---
> > automation/gitlab-ci/test.yaml | 23 +++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> > index 93632f1f9204..fc7663e3367a 100644
> > --- a/automation/gitlab-ci/test.yaml
> > +++ b/automation/gitlab-ci/test.yaml
> > @@ -162,6 +162,7 @@
> > PCIDEV: "01:00.0"
> > PCIDEV_INTR: "MSI-X"
> > CONSOLE_OPTS: "console=com1 com1=115200,8n1,pci,msi"
> > + SUT_ADDR: test-11.testnet
> > tags:
> > - qubes-hw11
>
> Is this a spurious change?
No, the SUT_ADDR variable is used by the test script to extract the
junit xml file via network.
> > @@ -340,6 +341,28 @@ zen3p-pvshim-x86-64-gcc-debug:
> > - *x86-64-test-needs
> > - alpine-3.18-gcc-debug
> >
> > +zen3p-tools-tests-pv-x86-64-gcc-debug:
> > + extends: .zen3p-x86-64
> > + script:
> > + - ./automation/scripts/qubes-x86-64.sh tools-tests-pv 2>&1 | tee ${LOGFILE}
> > + artifacts:
> > + reports:
> > + junit: tests-junit.xml
> > + needs:
> > + - *x86-64-test-needs
> > + - alpine-3.18-gcc-debug
> > +
> > +zen3p-tools-tests-pvh-x86-64-gcc-debug:
> > + extends: .zen3p-x86-64
> > + script:
> > + - ./automation/scripts/qubes-x86-64.sh tools-tests-pvh 2>&1 | tee ${LOGFILE}
> > + artifacts:
> > + reports:
> > + junit: tests-junit.xml
> > + needs:
> > + - *x86-64-test-needs
> > + - alpine-3.18-gcc-debug
> > +
> > qemu-smoke-dom0-arm64-gcc:
> > extends: .qemu-arm64
> > script:
> > --
> > git-series 0.9.1
> >
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-15 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 1:28 [PATCH v2 0/4] Few CI improvements Marek Marczykowski-Górecki
2025-02-14 1:28 ` [PATCH v2 1/4] automation: skip building domU if there is no test defined for it Marek Marczykowski-Górecki
2025-02-14 1:28 ` [PATCH v2 2/4] automation: add jobs running tests from tools/tests/* Marek Marczykowski-Górecki
2025-02-15 0:26 ` Stefano Stabellini
2025-02-14 1:28 ` [PATCH v2 3/4] automation: allow selecting individual jobs via CI variables Marek Marczykowski-Górecki
2025-02-15 0:29 ` Stefano Stabellini
2025-02-15 1:14 ` Marek Marczykowski-Górecki
2025-02-15 2:28 ` Stefano Stabellini
2025-02-14 1:28 ` [PATCH v2 4/4] automation: add tools/tests jobs on the AMD Zen3+ runner too Marek Marczykowski-Górecki
2025-02-15 0:33 ` Stefano Stabellini
2025-02-15 0:54 ` Marek Marczykowski-Górecki [this message]
2025-02-15 2:17 ` Stefano Stabellini
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=Z6_lt1Kd9ELpmv5e@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.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.