archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <>
To: <>
Subject: [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins
Date: Thu, 24 Oct 2019 18:01:15 -0400	[thread overview]
Message-ID: <011f01d58ab6$91fee620$b5fcb260$> (raw)

Hi All,

We are running the regression suite (as we always have) in Jenkins and are
finding that t0500 is basically a complete failure. I cannot recreate it
using bash where we have a real terminal, but without one, the t0500
consistently fails. I wonder whether any other platform is experiencing the
same situation.

We also find that we cannot run the main test suite as a background job - we
get segmentation faults that I have yet to isolate, but when run in the
foreground, no problem.

I wanted to get this out there because 2.24.0 goes too far as this did not
happen in 2.23.0 or any release prior.


-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.

             reply	other threads:[~2019-10-24 22:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 22:01 Randall S. Becker [this message]
2019-10-28 13:07 ` [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins Johannes Schindelin
2019-10-28 14:15   ` Randall S. Becker
2019-10-28 14:52     ` SZEDER Gábor
2019-10-28 15:20       ` Randall S. Becker
2019-10-29 10:16         ` SZEDER Gábor
2019-10-29 14:56           ` Randall S. Becker
2019-11-01 19:29           ` Randall S. Becker

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='011f01d58ab6$91fee620$b5fcb260$' \ \ \

* 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).