git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Todd Zullinger <tmz@pobox.com>, git@vger.kernel.org
Subject: Re: t5559 breaks with apache 2.4.55
Date: Fri, 10 Feb 2023 21:20:29 -0500	[thread overview]
Message-ID: <Y+b7bTs2vdXAe/ky@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq357ems2h.fsf@gitster.g>

On Thu, Feb 09, 2023 at 01:45:10PM -0800, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > ...
> > But that does at least give me more confidence that the bug is in
> > mod_http2, and isn't, say, some intentional behavior change there that
> > happens to trigger a bug in curl.
> >
> > I opened an issue here: https://github.com/icing/mod_h2/issues/243
> >
> > So we'll see if that helps.
> 
> Thanks.  I've seen that the above issue may have redirected the
> investigation to cURL, and over time, I expect taht this will start
> to trigger in more environments (as Apache 2.4.55 and mod_h2 2.0.10
> propagates) before it fixes itself (as fixed versions of these
> things we use in our tests percolates down).

Yeah, I am worried that this will bite other people, though it's not
clear to me yet how common the problematic version will be. But...

> In the meantime, perhaps we should punt with a patch like this?
> 
> 
> ------------ >8 ------------
> Subject: [PATCH] t5559: skip a known-to-be-broken test
> 
> t5559 runs the same set of tests as t5551 under HTTP/2 but one of
> them started failing with Apache 2.4.55 and mod_h2 2.0.10 (but not
> with HTTP/1.1).  Newer mod_h2 is known to have fixed the issue.
> 
> In the meantime, skip the test.

I'm not sure this is really sufficient. As I was running t5559 over and
over to test various versions, I noticed a few other cases that seemed
to fail, some of them racily. So I'm a bit worried that the problem may
be more extensive, and it is only that this particular test happened to
trigger it reliably.

In which case the right solution may be ditching t5559, or at the very
least adding a knob or version check to disable it.

So I'm tempted to just punt for now and see how often this bites people
in the real world. And if it does become a problem, we'll have more data
on what exactly should be changed.

-Peff

  reply	other threads:[~2023-02-11  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22  8:00 t5559 breaks with apache 2.4.55 Jeff King
2023-01-22 16:33 ` Todd Zullinger
2023-01-26 11:39   ` Jeff King
2023-01-29  6:35     ` Jeff King
2023-02-09 21:45       ` Junio C Hamano
2023-02-11  2:20         ` Jeff King [this message]
2023-02-11  2:34           ` Junio C Hamano
2023-02-11  3:00             ` 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

  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=Y+b7bTs2vdXAe/ky@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tmz@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.
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).