From: Julia Lawall <julia.lawall@inria.fr>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Nicolas Palix <nicolas.palix@imag.fr>, cocci@inria.fr
Subject: Re: [cocci] EXN: Coccinelle_modules.Common.Timeout
Date: Mon, 8 Jan 2024 07:37:54 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2401080736450.3630@hadrien> (raw)
In-Reply-To: <20240107144227.273e0233@kernel.org>
On Sun, 7 Jan 2024, Jakub Kicinski wrote:
> On Sun, 7 Jan 2024 21:15:54 +0100 (CET) Julia Lawall wrote:
> > > I couldn't google out any meaningful info about this. Is the timeout
> > > something I can increase locally? Is something wrong?
> >
> > Perhaps if you pull from github it will work better now, ie keep going
> > after the timeouts.
>
> Thank you! I fetched from github, and after an hour it's still making
> progress, previously it error'ed out after 10 minutes or so!
Great.
> Next issue.. :) when I run with --use-patch-diff commit1..commit2
> I get these three lines for every spatch run:
>
> grep: warning: + at start of expression
> grep: warning: + at start of expression
> grep: warning: + at start of expression
OK, will look into it. I think this comes from coccicheck, not from
Coccinelle.
julia
prev parent reply other threads:[~2024-01-08 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 18:35 [cocci] EXN: Coccinelle_modules.Common.Timeout Jakub Kicinski
2024-01-07 18:52 ` Julia Lawall
2024-01-08 7:30 ` [cocci] Reconsidering error handling strategy for coccicheck Markus Elfring
2024-01-07 20:15 ` [cocci] EXN: Coccinelle_modules.Common.Timeout Julia Lawall
[not found] ` <20240107144227.273e0233@kernel.org>
2024-01-08 6:37 ` Julia Lawall [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=alpine.DEB.2.22.394.2401080736450.3630@hadrien \
--to=julia.lawall@inria.fr \
--cc=cocci@inria.fr \
--cc=kuba@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.