git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: rsbecker@nexbridge.com, 'Junio C Hamano' <gitster@pobox.com>,
	git@vger.kernel.org
Cc: git-packagers@googlegroups.com
Subject: Re: v2.37.0-rc2 - Additional Breakages on NonStop x86 (was RE: [ANNOUNCE] Git v2.37.0-rc2)
Date: Thu, 23 Jun 2022 17:21:46 +0200	[thread overview]
Message-ID: <664fcc55-1cd3-eb01-9be6-80bc4492e849@web.de> (raw)
In-Reply-To: <002401d88700$7908f6d0$6b1ae470$@nexbridge.com>

Am 23.06.22 um 14:55 schrieb rsbecker@nexbridge.com:
> On June 22, 2022 3:32 PM, Junio C Hamano wrote:
>> A release candidate Git v2.37.0-rc2 is now available for testing at the usual places.
>> It is comprised of 378 non-merge commits since v2.36.0, contributed by 64 people,
>> 19 of which are new faces [*].
>
> RC2 had numerous new test failures on NonStop that were not present in RC1, RC0, or prior git releases, ignoring the @2 problem previously reported. Failures are:
>
> t5516.113
> t5601.8
> t7031.3, 11
> t7421 (all subtests)
> t7500.46-50
> t7528.4,5,8,15,16,20

That's curious.  Here are the test names:

   t5516-fetch-push.sh
      113 - fetch warns or fails when using username:password
   t5601-clone.sh
      8 - clone warns or fails when using username:password
   t7031-verify-tag-signed-ssh.sh
      3 - verify and show ssh signatures
      11 - verify multiple tags ssh
   t7421-submodule-summary-add.sh
      1 - summary test environment setup
      2 - submodule summary output for initialized submodule
      3 - submodule summary output for deinitialized submodule
      4 - submodule summary output for submodules with changed paths
   t7500-commit-template-squash-signoff.sh
      46 - commit --squash works with -c
      47 - commit --squash works with -C for same commit
      48 - commit --squash works with -c for same commit
      49 - commit --squash works with editor
      50 - invalid message options when using --fixup
   t7528-signed-commit-ssh.sh
      4 - verify and show signatures
      5 - verify-commit exits failure on untrusted signature
      8 - verify-commit succeeds with commit date and key validity matching
      15 - show signed commit with signature
      16 - detect fudged signature
      20 - show bad signature with custom format

rc2 changed the following files:

   $ git diff --stat v2.37.0-rc1 v2.37.0-rc2
    Documentation/git-gc.txt         |  3 +--
    GIT-VERSION-GEN                  |  2 +-
    builtin/name-rev.c               |  2 +-
    contrib/completion/git-prompt.sh | 32 +++++++++++++++++---------------
    t/t9903-bash-prompt.sh           |  2 +-
    5 files changed, 21 insertions(+), 20 deletions(-)

The name-rev change only modifies a help message.  At first glance there
doesn't seem to be a way that these changes may influence the outcome of
those tests.

René

  reply	other threads:[~2022-06-23 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 12:55 v2.37.0-rc2 - Additional Breakages on NonStop x86 (was RE: [ANNOUNCE] Git v2.37.0-rc2) rsbecker
2022-06-23 15:21 ` René Scharfe [this message]
2022-06-23 16:26   ` rsbecker
2022-06-23 16:27   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=664fcc55-1cd3-eb01-9be6-80bc4492e849@web.de \
    --to=l.s.r@web.de \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=rsbecker@nexbridge.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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