From: Paul Chaignon <paul@cilium.io>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Exit with non-zero status
Date: Wed, 6 May 2020 14:01:09 +0200 [thread overview]
Message-ID: <20200506120107.GA3242@Mem> (raw)
In-Reply-To: <78195706-c910-5c3b-5887-da94c244b61c@web.de>
On Tue, May 05, 2020 at 01:08:26PM +0200, Markus Elfring wrote:
> > For the record, I enabled Coccinelle in our CI (GitHub Actions)
> > yesterday and worked around that issue with the following script:
> >
> > make -C bpf/ coccicheck | tee /tmp/stdout
> > exit $(grep -c "[prefix of warning messages]" /tmp/stdout)
>
> I propose to improve the data processing approach according to your recent
> commit “coccinelle: Run coccicheck with GitHub Actions”.
> https://github.com/cilium/cilium/commit/35d299a4ee996dc2f4beec3c88b77dedbd00b2ba
>
>
> > Please see above script. I currently exit with number of failures,
> > but having just 0 (success) and 1 (fail) statuses would be enough.
>
> I suggest to stick to a more traditional handling of the program
> exit status because of development concerns around software portability.
>
>
> >> Will the usage of additional data structures become more interesting?
> >
> > Not sure I understand the question. What data structures?
>
> Examples:
>
> * Ordinary text files for the standard output and error channels.
>
> * Would you like to store any search results into database tables?
>
> * How do you think about to perform data transmissions by higher level
> programming interfaces for distributed processes?
>
>
> Which software extensions can become more interesting also for
> applications around your continuous integration system?
I see. We're not planning to use any of the above in the medium term.
We're only planning to add Coccinelle rules in the future. If we need more
complex post-processing, we'll likely implement it in GitHub Actions and
not directly in Coccinelle scripts.
Paul
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-05-06 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 18:40 [Cocci] Exit with non-zero status Markus Elfring
2020-04-29 19:07 ` Paul Chaignon
2020-04-29 19:50 ` Markus Elfring
2020-05-05 9:59 ` Paul Chaignon
2020-05-05 11:08 ` Markus Elfring
2020-05-06 12:01 ` Paul Chaignon [this message]
2020-05-06 12:24 ` Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2020-04-29 14:39 Paul Chaignon
2020-04-29 15:07 ` Julia Lawall
2020-04-29 15:16 ` Paul Chaignon
2020-04-29 15:25 ` Julia Lawall
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=20200506120107.GA3242@Mem \
--to=paul@cilium.io \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).