git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.35.0-rc1
Date: Mon, 17 Jan 2022 10:42:02 -0800	[thread overview]
Message-ID: <xmqqy23eurut.fsf@gitster.g> (raw)
In-Reply-To: <026201d80bbc$10a251a0$31e6f4e0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Mon, 17 Jan 2022 11:05:31 -0500")

<rsbecker@nexbridge.com> writes:

> On January 14, 2022 9:19 PM, Junio wrote:
>> A release candidate Git v2.35.0-rc1 is now available for testing at the usual places.
>> It is comprised of 467 non-merge commits since v2.34.0, contributed by 80
>> people, 32 of which are new faces [*].
>
> FYI: rc1 built/test (mostly) passes on both NonStop x86 and ia64 platforms.
>
> We seem to have a recurrence of a transient failure in t5562 from a few releases ago. Retesting makes the problem disappear.
>
> Subtest 8
> #	
> #		test_env HTTP_CONTENT_ENCODING="gzip" test_http_env upload empty_body &&
> #		! verify_http_result "200 OK"
> #	
> Subtest 14
> #	
> #		test_env HTTP_CONTENT_ENCODING="gzip" test_http_env receive empty_body &&
> #		! verify_http_result "200 OK"
> #	
>
> Am I mistaken that using the ! verify_http_result construct is not recommended or am I misremembering the discussion?
>
> Regards,
> --Randall

I do not recall anything about that shell function.

I found a half-thread with similar-looking report on an obscure
system, since the 2.25 era:

https://lore.kernel.org/git/nycvar.QRO.7.76.6.2003252000200.46@tvgsbejvaqbjf.bet/

And then from you that is even older, in the 2.21 era:

https://lore.kernel.org/git/002201d4c560$5a319c40$0e94d4c0$@nexbridge.com/

But neither seems to lead to a discussion on the use of verify_http_result
helper.


  reply	other threads:[~2022-01-17 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-15  2:18 [ANNOUNCE] Git v2.35.0-rc1 Junio C Hamano
2022-01-17 16:05 ` rsbecker
2022-01-17 18:42   ` Junio C Hamano [this message]
2022-01-17 18:52     ` rsbecker

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=xmqqy23eurut.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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).