From: Federico Serafini <federico.serafini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
Federico Serafini <federico.serafini@bugseng.com>,
Simone Ballarin <simone.ballarin@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [XEN PATCH 0/3] automation/eclair: do not allow failure for triggered analyses
Date: Mon, 29 Apr 2024 17:21:56 +0200 [thread overview]
Message-ID: <cover.1714401209.git.federico.serafini@bugseng.com> (raw)
Patch 1/3 does some preparation work.
Patch 2/3, as the title says, removes allow_failure = true for triggered
analyses.
Patch 3/3 makes explicit that initally no files are tagged as adopted, this
is needed by the scheduled analysis.
Federico Serafini (3):
automation/eclair: tag Rule 7.2 as clean and temporarily remove Rules
1.1 and 8.2
automation: do not allow failure for triggered analyses
automation/eclair: make explicit there are no adopted files by default
automation/eclair_analysis/ECLAIR/analysis.ecl | 4 ++++
automation/eclair_analysis/ECLAIR/tagging.ecl | 2 +-
automation/gitlab-ci/analyze.yaml | 1 -
3 files changed, 5 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-29 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 15:21 Federico Serafini [this message]
2024-04-29 15:21 ` [XEN PATCH 1/3] automation/eclair: tag Rule 7.2 as clean and temporarily remove Rules 1.1 and 8.2 Federico Serafini
2024-05-01 19:45 ` Stefano Stabellini
2024-04-29 15:21 ` [XEN PATCH 2/3] automation: do not allow failure for triggered analyses Federico Serafini
2024-05-01 19:45 ` Stefano Stabellini
2024-04-29 15:21 ` [XEN PATCH 3/3] automation/eclair: make explicit there are no adopted files by default Federico Serafini
2024-05-01 19:46 ` Stefano Stabellini
2024-05-03 19:14 ` [REGRESSION] Re: [XEN PATCH 0/3] automation/eclair: do not allow failure for triggered analyses Andrew Cooper
2024-05-03 19:44 ` Federico Serafini
2024-05-03 19:46 ` Andrew Cooper
2024-05-03 20:01 ` Federico Serafini
2024-05-03 20:06 ` Andrew Cooper
2024-05-06 6:45 ` Nicola Vetrini
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=cover.1714401209.git.federico.serafini@bugseng.com \
--to=federico.serafini@bugseng.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=simone.ballarin@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.