git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: rsbecker@nexbridge.com
Cc: 'Junio C Hamano' <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Test Failure t5516.113 RE: [ANNOUNCE] Git v2.37.0-rc0
Date: Wed, 15 Jun 2022 12:46:21 +0200	[thread overview]
Message-ID: <220615.86ilp2xky8.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <01e801d880a0$2c5e4d50$851ae7f0$@nexbridge.com>


On Wed, Jun 15 2022, rsbecker@nexbridge.com wrote:

> On June 13, 2022 9:46 PM, Junio C Hamano wrote:
>>An early preview release Git v2.37.0-rc0 is now available for testing at the usual
>>places.  It is comprised of 339 non-merge commits since v2.36.0, contributed by 59
>>people, 18 of which are new faces [*].  There are a few topics that we may want to
>>merge before the final release, which will be in -rc1 that is planned to be tagged at
>>around the end of the week.
>
> This one keeps showing up occasionally. I am not sure why, but I am
> not certain bash likes ! grep. This only happens on our NonStop x86
> build, which is a more recent platform than the ia64, where the
> construct succeeds. Have we not moved away from that?
>
> not ok 113 - fetch warns or fails when using username:password
> #	
> #		message="URL 'https://username:<redacted>@localhost/' uses plaintext credentials" &&
> #		test_must_fail git -c fetch.credentialsInUrl=allow fetch https://username:password@localhost 2>err &&
> #		! grep "$message" err &&
> #	
> #		test_must_fail git -c fetch.credentialsInUrl=warn fetch https://username:password@localhost 2>err &&
> #		grep "warning: $message" err >warnings &&
> #		test_line_count = 3 warnings &&
> #	
> #		test_must_fail git -c fetch.credentialsInUrl=die fetch https://username:password@localhost 2>err &&
> #		grep "fatal: $message" err >warnings &&
> #		test_line_count = 1 warnings &&
> #	
> #		test_must_fail git -c fetch.credentialsInUrl=die fetch https://username:@localhost 2>err &&
> #		grep "fatal: $message" err >warnings &&
> #		test_line_count = 1 warnings
> #	

I've submitted
https://lore.kernel.org/git/cover-0.1-00000000000-20220615T103609Z-avarab@gmail.com
to fix this (but spotted this thread just afterwards, I fixed the bug
yesterday).

This happens on all platforms, you just happen to have NO_CURL=Y only in
your nonstop build.

      reply	other threads:[~2022-06-15 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 10:10 Test Failure t5516.113 RE: [ANNOUNCE] Git v2.37.0-rc0 rsbecker
2022-06-15 10:46 ` Ævar Arnfjörð Bjarmason [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:
  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=220615.86ilp2xky8.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.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).