From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: <git-packagers@googlegroups.com>
Subject: RE: [ANNOUNCE] Git v2.26.0 - Test Results NonStop Platform
Date: Tue, 24 Mar 2020 14:37:01 -0400 [thread overview]
Message-ID: <031c01d6020b$38f58a80$aae09f80$@nexbridge.com> (raw)
In-Reply-To:
On March 23, 2020 5:25 PM, I wrote:
> To: 'Junio C Hamano' <gitster@pobox.com>; 'git@vger.kernel.org'
> <git@vger.kernel.org>
> Cc: 'git-packagers@googlegroups.com' <git-packagers@googlegroups.com>
> Subject: RE: [ANNOUNCE] Git v2.26.0 - Test Results NonStop Platform
>
> On March 22, 2020 9:10 PM, Junio C Hamano wrote:
> > The latest feature release Git v2.26.0 is now available at the usual
> > places. It is comprised of 504 non-merge commits since v2.25.0,
> > contributed by 64 people, 12 of which are new faces.
>
> We had t0301 fail again. This is run entirely within bash as we gave up on ksh.
> I need some advice on what to do here. It does look like this is actually in git
> rather than the tests, based on below.
>
> What is really strange is that the subtests are transiently failing and not the
> same test each time. I cannot get any consistency during test runs. I also do
> not see anything in the differences that might account for this, unless
> somehow the unicode length. I did revert and retried the test, which also
> resulted in transient failures. It all works fine when I use -x, so I can't shed
> light on it from there. An example of the failure is:
>
> --- expect-stdout 2020-03-23 20:40:57 +0000
> +++ stdout 2020-03-23 20:40:58 +0000
> @@ -1,4 +1,4 @@
> protocol=https
> host=example.com
> -username=askpass-username
> -password=askpass-password
> +username=store-user
> +password=store-pass
> not ok 21 - helper (cache) can forget host
>
> We also had a hang in subtest 23 at
>
> expecting success of 0301.23 'helper (cache) can forget user':
> check reject $HELPER <<-\EOF &&
> protocol=https
> host=example.com
> username=user1
> EOF
> check fill $HELPER <<-\EOF
> protocol=https
> host=example.com
> username=user1
> --
> protocol=https
> host=example.com
> username=user1
> password=askpass-password
> --
> askpass: Password for 'https://user1@example.com':
> EOF
>
> ++ check reject cache
> ++ credential_opts=
> ++ credential_cmd=reject
> ++ shift
> ++ for arg in "$@"
> ++ credential_opts=' -c credential.helper='\''cache'\'''
> ++ read_chunk
> ++ read line
> ++ case "$line" in
> ++ echo protocol=https
> ++ read line
> ++ case "$line" in
> ++ echo host=example.com
> ++ read line
> ++ case "$line" in
> ++ echo username=user1
> ++ read line
> ++ read_chunk
> ++ read line
> ++ read_chunk
> ++ read line
> ++ eval 'git -c credential.helper='\''cache'\'' credential reject <stdin >stdout
> 2>stderr'
> +++ git -c credential.helper=cache credential reject
I should have mentioned that we are currently on OpenSSL 1.0.2t. The 1.1.x series is not yet available.
next reply other threads:[~2020-03-24 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 18:37 Randall S. Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 21:25 [ANNOUNCE] Git v2.26.0 - Test Results NonStop Platform Randall S. Becker
2020-03-24 3:52 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='031c01d6020b$38f58a80$aae09f80$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).