git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephane Odul <stephane@clumio.com>
To: git@vger.kernel.org
Subject: Suspected git grep regression in git 2.40.0
Date: Tue, 21 Mar 2023 01:04:08 -0700	[thread overview]
Message-ID: <7E83DAA1-F9A9-4151-8D07-D80EA6D59EEA@clumio.com> (raw)

We have a CI pipeline on a private repository that started failing consistently while running `git grep -P` commands. The command fails with an exit code of -11 and is failing pretty consistently. With prior versions of git there is no issue whatsoever, but with 2.40.0 it always fails on the same call. Other git grep calls are fine, but that one is failing consistently.

I was not able to reproduce locally but my main machine is an M1 MacBook Pro, the CI pipeline runs under Kubernetes in AWS and the container is based on Ubuntu 20.04 with the git client installed via the PPA.

The error is for this pattern `git grep -cP '^\w+ = json.load'`.

As a  workaround we tried to download and install the microsoft-git v2.39.2 deb package since it allows us to downgrade, but then the git grep commands just got stuck.

Thank you,
Stephane Odul

             reply	other threads:[~2023-03-21  8:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21  8:04 Stephane Odul [this message]
2023-03-21 12:33 ` Suspected git grep regression in git 2.40.0 Bagas Sanjaya
2023-03-21 16:33 ` Junio C Hamano
2023-03-21 19:20   ` Mathias Krause
2023-03-21 20:46     ` [EXTERNAL SENDER] " Stephane Odul
2023-03-22 19:52       ` Mathias Krause
2023-03-22 20:04         ` [EXTERNAL SENDER] " Stephane Odul
2023-03-23 14:40         ` Suspected git grep regression in git 2.40.0 - proposed fix Mathias Krause
2023-03-23 16:19           ` Junio C Hamano
2023-03-23 16:36             ` Mathias Krause
2023-03-23 17:25           ` [PATCH v2] grep: work around UTF-8 related JIT bug in PCRE2 <= 10.34 Mathias Krause

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=7E83DAA1-F9A9-4151-8D07-D80EA6D59EEA@clumio.com \
    --to=stephane@clumio.com \
    --cc=git@vger.kernel.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 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).