archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <>
To: "Randall S. Becker" <>
Subject: Re: [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins
Date: Mon, 28 Oct 2019 14:07:21 +0100 (CET)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <011f01d58ab6$91fee620$b5fcb260$>

Hi Randall,

On Thu, 24 Oct 2019, Randall S. Becker wrote:

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

This says that a test failed, but it lacks the verbose log, so there is
little else left to the willing reader than wild guesses that are almost
certainly completely missing the culprit.

In other words: verbose log, please. That is, the output of the test
script when run with `-i -v -x` (or `-i -V -x` in which case you will
want to analyze the contents of
`t/test-results/t0500-progress-display.out` and if that does not help,
paste it into a reply).


> 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.
> Sincerely,
> Randall
> -- 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-28 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 22:01 [BUG] git 2.24.0-rc1 t0500 on NonStop in Jenkins Randall S. Becker
2019-10-28 13:07 ` Johannes Schindelin [this message]
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 \ \ \ \ \

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