From: Jeff King <peff@peff•net>
To: git@vger•kernel.org
Cc: Matthew John Cheetham <mjcheetham@outlook•com>,
Daniel Stenberg <daniel@haxx•se>
Subject: [PATCH 0/3] test-suite fixes for upcoming curl 8.18.0
Date: Thu, 18 Dec 2025 07:11:20 -0500 [thread overview]
Message-ID: <20251218121120.GA3252258@coredump.intra.peff.net> (raw)
After upgrading my Debian unstable box to libcurl 8.18.0~rc2-1, I
noticed a few new test failures. They seem to mostly be caused by
brittle expectations in the tests. These patches fix the tests to handle
both old and new versions (I tested against curl's 8_17_0 and
rc-8_18_0-2 tags).
Daniel: I'm cc-ing you in case you want to double-check that curl's
behavior changes are all OK before the release. I think it's mostly
fine, though the handling of tab versus space in the third patch is
perhaps questionable.
Matthew: I had to make some educated guesses about one of the tests in
patch 2. You might remember the original intent.
[1/3]: t5551: handle trailing slashes in expected cookies output
[2/3]: t5563: add missing end-of-line in HTTP header
[3/3]: t5563: relax whitespace assumptions for unfolded headers
t/t5551-http-fetch-smart.sh | 15 +++++++++------
t/t5563-simple-http-auth.sh | 15 +++++++++++----
2 files changed, 20 insertions(+), 10 deletions(-)
-Peff
next reply other threads:[~2025-12-18 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 12:11 Jeff King [this message]
2025-12-18 12:13 ` [PATCH 1/3] t5551: handle trailing slashes in expected cookies output Jeff King
2025-12-18 12:18 ` [PATCH 2/3] t5563: add missing end-of-line in HTTP header Jeff King
2025-12-18 13:41 ` Matthew John Cheetham
2025-12-19 7:32 ` Jeff King
2025-12-18 12:22 ` [PATCH 3/3] t5563: relax whitespace assumptions for unfolded headers Jeff King
2025-12-18 13:45 ` Matthew John Cheetham
2025-12-18 12:37 ` [PATCH 0/3] test-suite fixes for upcoming curl 8.18.0 Daniel Stenberg
2025-12-18 16:49 ` Daniel Stenberg
2025-12-19 8:04 ` Jeff King
2025-12-19 8:47 ` Daniel Stenberg
2025-12-19 23:23 ` Jeff King
2025-12-20 2:14 ` Junio C Hamano
2025-12-19 7:50 ` 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=20251218121120.GA3252258@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=daniel@haxx$(echo .)se \
--cc=git@vger$(echo .)kernel.org \
--cc=mjcheetham@outlook$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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