On Thu, Feb 09, 2023 at 01:45:10PM -0800, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> 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
