From: Julia Lawall <julia.lawall@inria.fr>
To: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Cc: cocci@inria.fr
Subject: Re: [cocci] Spatch 1.1.1 backward incompatibility
Date: Fri, 16 Feb 2024 14:05:47 +0100 (CET) [thread overview]
Message-ID: <5f7a6b3d-89b2-c7b8-bada-87741dfe2c92@inria.fr> (raw)
In-Reply-To: <86f82a44-129a-4a84-be4d-4b230c2c018e@linbit.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On Fri, 16 Feb 2024, Christoph Böhmwalder wrote:
> Am 16.02.24 um 10:51 schrieb Julia Lawall:
> >
> > Thanks for the report. If convenient you could try the github version.
>
> The latest GitHub version (0df3efff) has the same problem. It also seems
> to have some other issue, because it took 1385.5s (instead of the usual
> ~25) to process the patch.
>
> I also noticed that Fedora used OCaml 5.0, so I tried with the same
> commit the Fedora version is based on (0afff7f), but compiled with OCaml
> 4.14. It didn't make a difference, so it's not an issue with OCaml 5.
>
> I'm trying to bisect this now, will report if I find anything.
OK, thanks. It may be sufficient to bisect your example. You can try for
example
--debug --show-trying
to see at what function it is getting stuck.
julia
>
> >
> > I really need to make a new release...
>
> I was going to ask about that... :)
>
> >
> > julia
> --
> Christoph Böhmwalder
> LINBIT | Keeping the Digital World Running
> DRBD HA — Disaster Recovery — Software defined Storage
>
prev parent reply other threads:[~2024-02-16 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 9:24 [cocci] Spatch 1.1.1 backward incompatibility Christoph Böhmwalder
2024-02-16 9:51 ` Julia Lawall
2024-02-16 12:20 ` Christoph Böhmwalder
2024-02-16 12:47 ` Markus Elfring
2024-02-16 13:05 ` 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=5f7a6b3d-89b2-c7b8-bada-87741dfe2c92@inria.fr \
--to=julia.lawall@inria.fr \
--cc=christoph.boehmwalder@linbit.com \
--cc=cocci@inria.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 read-only IMAP folder(s) and NNTP newsgroup(s).