All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Anton Eliasson <anton.eliasson@axis.com>
Cc: nicolas palix <nicolas.palix@imag.fr>, cocci <cocci@inria.fr>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	kernel@axis.com
Subject: Re: [cocci] [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap
Date: Thu, 2 Nov 2023 22:27:55 +0100 (CET)	[thread overview]
Message-ID: <978265928.4471013.1698960475973.JavaMail.zimbra@inria.fr> (raw)
In-Reply-To: <20231003-coccicheck-v1-1-07d2d900a52a@axis.com>



----- Mail original -----
> De: "Anton Eliasson" <anton.eliasson@axis.com>
> À: "Julia Lawall" <Julia.Lawall@inria.fr>, "nicolas palix" <nicolas.palix@imag.fr>
> Cc: "cocci" <cocci@inria.fr>, "linux-kernel" <linux-kernel@vger.kernel.org>, "Anton Eliasson" <anton.eliasson@axis.com>,
> kernel@axis.com
> Envoyé: Mardi 3 Octobre 2023 16:25:14
> Objet: [cocci] [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap

> Exiting on error breaks the chain mode. Return the error instead in
> order for the caller to propagate it or in the case of chain, try the
> next mode.
> 
> Signed-off-by: Anton Eliasson <anton.eliasson@axis.com>
> ---
> scripts/coccicheck | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/scripts/coccicheck b/scripts/coccicheck
> index e52cb43fede6..95a312730e98 100755
> --- a/scripts/coccicheck
> +++ b/scripts/coccicheck
> @@ -153,7 +153,7 @@ run_cmd_parmap() {
> 	err=$?
> 	if [[ $err -ne 0 ]]; then
> 		echo "coccicheck failed"
> -		exit $err
> +		return $err
> 	fi
> }
> 

I tried disabling OCaml in my version of Coccinelle and then ran make coccicheck with this patch.  But I didn't see any improvement.  On the other hand, it keeps going if I just remove the exit line entirely.  Is that what is wanted?  One can still see the coccicheck failed message.

julia

> --
> 2.30.2

  reply	other threads:[~2023-11-02 21:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 14:25 [cocci] [PATCH 0/2] coccicheck bugfix and CI improvement Anton Eliasson
2023-10-03 14:25 ` Anton Eliasson
2023-10-03 14:25 ` [cocci] [PATCH 1/2] scripts: coccicheck: Return error from run_cmd_parmap Anton Eliasson
2023-10-03 14:25   ` Anton Eliasson
2023-11-02 21:27   ` Julia Lawall [this message]
2023-11-17 16:36     ` [cocci] " Anton Eliasson
2023-10-03 14:25 ` [cocci] [PATCH 2/2] scripts: coccicheck: Separate spatch stdout and stderr Anton Eliasson
2023-10-03 14:25   ` Anton Eliasson
2023-10-07 19:41   ` [cocci] " Julia Lawall
2023-10-10 15:59     ` Anton Eliasson
2023-10-10 16:11       ` Julia Lawall
2023-10-11 13:19         ` Anton Eliasson
2023-10-11 13:46           ` Julia Lawall
2023-10-11 13:57             ` Anton Eliasson
2023-10-12  7:30             ` [cocci] Detecting differences according to source code analysis warnings Markus Elfring

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=978265928.4471013.1698960475973.JavaMail.zimbra@inria.fr \
    --to=julia.lawall@inria.fr \
    --cc=anton.eliasson@axis.com \
    --cc=cocci@inria.fr \
    --cc=kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.palix@imag.fr \
    /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.