From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH v4] automation/eclair: add new analysis jobs with differing configurations
Date: Mon, 24 Nov 2025 18:15:43 +0100 [thread overview]
Message-ID: <84bc6efff60733ae9fbcdfd253bc5542@bugseng.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2511031448530.495094@ubuntu-linux-20-04-desktop>
On 2025-11-03 23:52, Stefano Stabellini wrote:
> On Mon, 3 Nov 2025, Nicola Vetrini wrote:
>> The following analysis jobs are performed:
>> - eclair-{x86_64,ARM64}: analyze Xen using the default configuration
>> for
>> that architecture; runs on runners tagged `eclair-analysis'.
>>
>> - eclair-{x86-64,ARM64}-safety: analyze Xen using the configuration
>> for
>> safety, which is more restricted; runs on runners tagged
>> `eclair-analysis-safety`.
>>
>> - eclair-{x86_64,ARM64}-testing: analyze Xen using the default
>> configuration for the purposes of testing new runner updates; runs
>> on
>> runners tagged `eclair-analysis-testing`.
>>
>> Signed-off-by: Nicola Vetrini <nicola.vetrini@bugseng.com>
>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
>
> I'll commit it as soon as the tree reopens.
>
Hi Stefano,
could you merge the change or do you want me to rebase? (there should be
no conflicts however)
Thanks
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
prev parent reply other threads:[~2025-11-24 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 19:34 [XEN PATCH v4] automation/eclair: add new analysis jobs with differing configurations Nicola Vetrini
2025-11-03 22:52 ` Stefano Stabellini
2025-11-24 17:15 ` Nicola Vetrini [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=84bc6efff60733ae9fbcdfd253bc5542@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.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.