From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Michal Orzel <michal.orzel@amd.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>,
Community Manager <community.manager@xenproject.org>
Subject: Re: [PATCH 8/8] automation/cirrus-ci: add smoke tests for the FreeBSD builds
Date: Tue, 18 Mar 2025 10:47:56 +0100 [thread overview]
Message-ID: <Z9lBTCXN_Jb1XsSh@macbook.local> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2503171708070.3477110@ubuntu-linux-20-04-desktop>
On Mon, Mar 17, 2025 at 05:09:25PM -0700, Stefano Stabellini wrote:
> On Mon, 17 Mar 2025, Roger Pau Monne wrote:
> > Introduce a basic set of smoke tests using the XTF selftest image, and run
> > them on QEMU. Use the matrix keyword to create a different task for each
> > XTF flavor on each FreeBSD build.
> >
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> > ---
> > I've used the current version of FreeBSD to run the tests, but it might be
> > safer to use the latest production (release) version instead.
>
> It is better to avoid using "current" (I called it "latest" in my
> previous email) if it is rolling. Otherwise, it is OK.
Yes, will adjust to use production instead of current and resend the
tail of the series.
> Other than that, it is great.
Thanks. Afterwards I would like to add a specific UBSAN enabled
build, and do some more testing with it. I found clang UBSAN more
complete than gcc (specially with the UB pointer arithmetic checks).
Roger.
prev parent reply other threads:[~2025-03-18 9:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 12:16 [PATCH 0/8] automation/cirrus-ci: add smoke tests of the FreeBSD builds Roger Pau Monne
2025-03-17 12:16 ` [PATCH 1/8] automation/cirrus-ci: add timestamps Roger Pau Monne
2025-03-17 23:48 ` Stefano Stabellini
2025-03-17 12:16 ` [PATCH 2/8] automation/cirrus-ci: update FreeBSD to 13.5 Roger Pau Monne
2025-03-17 23:48 ` Stefano Stabellini
2025-03-17 12:16 ` [PATCH 3/8] automation/cirrus-ci: store Xen Kconfig before doing a build Roger Pau Monne
2025-03-17 23:50 ` Stefano Stabellini
2025-03-17 12:16 ` [PATCH 4/8] automation/cirrus-ci: use matrix keyword to generate per-version build tasks Roger Pau Monne
2025-03-18 0:06 ` Stefano Stabellini
2025-03-17 12:16 ` [PATCH 5/8] automation/cirrus-ci: build XTF Roger Pau Monne
2025-03-18 0:07 ` Stefano Stabellini
2025-03-18 9:43 ` Roger Pau Monné
2025-03-17 12:16 ` [PATCH 6/8] automation/cirrus-ci: store XTF and Xen build artifacts Roger Pau Monne
2025-03-18 0:07 ` Stefano Stabellini
2025-03-17 12:16 ` [PATCH 7/8] automation/console.exp: do not assume expect is always at /usr/bin/ Roger Pau Monne
2025-03-17 23:48 ` Stefano Stabellini
2025-03-18 9:45 ` Roger Pau Monné
2025-03-17 12:16 ` [PATCH 8/8] automation/cirrus-ci: add smoke tests for the FreeBSD builds Roger Pau Monne
2025-03-17 16:45 ` Oleksii Kurochko
2025-03-18 0:09 ` Stefano Stabellini
2025-03-18 9:47 ` Roger Pau Monné [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=Z9lBTCXN_Jb1XsSh@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=community.manager@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=oleksii.kurochko@gmail.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.