From: Todd Zullinger <tmz@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
Junio C Hamano <gitster@pobox.com>
Subject: t5559-http-fetch-smart-http2 failures
Date: Wed, 30 Nov 2022 17:09:34 -0500 [thread overview]
Message-ID: <Y4fUntdlc1mqwad5@pobox.com> (raw)
Hi,
I started seeing failures in rc0 but I was distracted by the
long weekend.
The changes in 73c49a4474 (t: run t5551 tests with both HTTP
and HTTP/2, 2022-11-11) seem to rather frequently trigger
test failures on Fedora.
The most frequent test to fail is "large fetch-pack requests
can be sent using chunked encoding" (t5559.30), but earlier
tests have also failed on occasion. For the common failure,
the test exits with:
expecting success of 5559.30 'large fetch-pack requests can be sent using chunked encoding':
GIT_TRACE_CURL=true git -c http.postbuffer=65536 \
clone --bare "$HTTPD_URL/smart/repo.git" split.git 2>err &&
{
test_have_prereq HTTP2 ||
grep "^=> Send header: Transfer-Encoding: chunked" err
}
+++ GIT_TRACE_CURL=true
+++ git -c http.postbuffer=65536 clone --bare http://127.0.0.1:5559/smart/repo.git split.git
error: last command exited with $?=128
not ok 30 - large fetch-pack requests can be sent using chunked encoding
(Less frequently, I've seen the last command exit 141.)
I haven't been able to track down the problem, which happens
a lot on the Fedora build system but less often during local
builds. Obviously, the bug is too shy to show itself while
anyone is watching. ;)
I can easily disable the failing tests for a bit, but does
anyone have an idea what might be the cause or how to better
debug it when it occurs on a buildsystem without direct
access?
Thanks,
--
Todd
next reply other threads:[~2022-11-30 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 22:09 Todd Zullinger [this message]
2022-12-01 20:25 ` t5559-http-fetch-smart-http2 failures Jeff King
2022-12-09 2:20 ` Todd Zullinger
2022-12-09 20:59 ` 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=Y4fUntdlc1mqwad5@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).