From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Jacob Abel <jacobabel@nullpo.dev>,
"D. Ben Knoble" <ben.knoble@gmail.com>, Git <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: t2400 on freebsd12
Date: Fri, 14 Jul 2023 14:06:15 -0700 [thread overview]
Message-ID: <xmqq8rbinqyg.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cRMXJkrEgyVtC0u2QK=5QNnJOQnXBU_rE+JiGufEYH9sg@mail.gmail.com> (Eric Sunshine's message of "Fri, 14 Jul 2023 12:19:41 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
> I haven't been following this thread closely, but I wonder if the
> `grep` introduced by patch [3/8] of the cited patch series is
> problematic:
>
> grep -E "fatal:( options)? .* cannot be used together" actual
>
> since BSD lineage regexp (including macOS) historically did not
> support the "?" repetition operator. Perhaps an easy fix would be to
> simplify this to:
>
> grep "cannot be used together" actual
We do not seem to get the same breakage on macOS CI runs (otherwise
this would have been caught much earlier). We do have many "grep
-E" invocations to ask for ERE but not many of them uses zero-or-one
'?' in our test suite. But I would be somewhat surprised if
test_dir_is_empty is broken on FreeBSD and nobody has noticed it for
this long.
I got an impression from the discussion so far that this breakage is
flaky and not always reproducible. I wonder if "stress" thing helps
the chance to reproduce for those with FreeBSD boxes?
$ cd t && sh ./t2400-* --stress
Thanks.
next prev parent reply other threads:[~2023-07-14 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 17:37 t2400 on freebsd12 D. Ben Knoble
2023-07-13 19:17 ` D. Ben Knoble
2023-07-13 20:27 ` Junio C Hamano
2023-07-13 20:43 ` Eric Sunshine
2023-07-13 21:44 ` D. Ben Knoble
2023-07-14 6:22 ` Jacob Abel
2023-07-14 16:19 ` Eric Sunshine
2023-07-14 19:45 ` Jacob Abel
2023-07-14 21:06 ` Junio C Hamano [this message]
2023-07-15 3:02 ` Jacob Abel
2023-07-16 2:51 ` Eric Sunshine
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=xmqq8rbinqyg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=jacobabel@nullpo.dev \
--cc=johannes.schindelin@gmx.de \
--cc=sunshine@sunshineco.com \
/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).