list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Randall S. Becker" <>
To: "'Johannes Schindelin'" <>
Cc: "'Junio C Hamano'" <>, <>
Subject: RE: [ANNOUNCE] Git v2.22.0-rc2
Date: Mon, 3 Jun 2019 10:13:44 -0400	[thread overview]
Message-ID: <003701d51a16$913f38e0$b3bdaaa0$> (raw)
In-Reply-To: <>

On Monday, June 3, 2019 9:50 AM, Johannes Schindelin wrote:
> To: Randall S. Becker <>
> Cc: 'Junio C Hamano' <>;
> Subject: RE: [ANNOUNCE] Git v2.22.0-rc2
> Hi Randall,
> On Sun, 2 Jun 2019, Randall S. Becker wrote:
> > Just a few small nits from RC2 test results on the NonStop TNS/E
> > platform:
> >
> > 1. t0021 subtest 15 is being flakey. It fails on the first run (make
> > -k
> > test) but succeeds when run in isolation. This is new on the NonStop
> > TNS/E platform. t0021 has been a bit flakey in the past, but not
> > recently. Just thought I'd mention it. It's only slightly
> > disconcerting because I make very heavy use of smudge filters but
> > since it runs fine in isolation, I'm going to assume it is fine. We
> > had one unsubstantiated report of an occasional misfire of smudge
> > filters, but no substantive evidence at this point to reproduce the
> t0021.15 is indeed flaky, and not only for NonStop. It is so flaky, even,
that I
> opened


> > 2. t7519 subtest 25 still does not pass (previously reported for RC1)
> > when run via "make -k test" the first time. This runs successfully
> > when run in isolation or the second time.
> I offered a fix for that in js/fsmonitor-unflake, and it already made it
> `next` (and hopefully into v2.22.0) as you can see here:
> (look for the
> branch symbol below the commit message).

I'll keep an eye out for it. We are good with RC2 anyway.

> > 3. t9001, t9020, t9600, t9601, t9602, t9604, fail, but should not run
> > on platform (not new, just a reminder). We do not have sendmail or
> > subversion.
> At least for Subversion, this should be detected. For send-email, I don't
> know... There *was* a bug in t9001 where it failed to mark a send-email
> tests cases with the `PERL` prerequisite, but that was fixed, and I guess
> have Perl anyway?

Yes, we do have Perl on the box. However, the send-email functions do not
work - probably missing modules. As far as SVN goes, we have the git SVN
modules, but not the actual SVM modules in our Perl. There has been some
effort to port those, but we have had CPAN issues for a while now. I am
trying to find a resource to help with porting - personally, I could really
use the SVN module to allow svn2git to function on box. That would make my
life a whole lot easier.


      reply	other threads:[~2019-06-03 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 21:23 Junio C Hamano
2019-05-31 12:13 ` Git for Windows v2.22.0-rc2, was " Johannes Schindelin
2019-06-02 14:27 ` Randall S. Becker
2019-06-03 13:49   ` Johannes Schindelin
2019-06-03 14:13     ` Randall S. Becker [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:

  List information:

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

  git send-email \
    --in-reply-to='003701d51a16$913f38e0$b3bdaaa0$' \ \ \ \ \

* 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.
Code repositories for project(s) associated with this inbox:

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