[PATCH 0/3] fixing expensive http test timeouts

[Jeff King <peff@peff.net>]

On Fri, Jun 26, 2026 at 04:26:28PM -0700, Michael Montalbo wrote:

> I think Peff and Patrick's suggestion to just increase the Apache timeout
> makes sense. I ran some experiments using a really long timeout with an
> artificially slowed down CI runner and all the jobs made progress
> (if slowly) without stalling, and eventually completed successfully:
> 
> https://github.com/mmontalbo/git/actions/runs/28267019651
> 
> I haven't spent a lot of time trying to figure out what the right timeout
> value should be. An hour definitely seems like overkill, with something
> on the order of 5-10 minutes seeming more reasonable, but I don't
> have a principled number.

Here are some patches to keep things moving along. I arbitrarily picked
10 minutes, because multiplying the 1-minute default by 10 felt right. ;)

The first one just bumps the timeout and should make our problems go
away. The other two are optimizations, but I'm on the fence on whether
the final patch is worth it.

Thanks again for all of the digging.

  [1/3]: t/lib-httpd: bump apache timeout
  [2/3]: t5551: put many-tags case into its own repo
  [3/3]: t5551: pack refs after creating many tags

 t/lib-httpd/apache.conf     |  1 +
 t/t5551-http-fetch-smart.sh | 10 ++++++----
 2 files changed, 7 insertions(+), 4 deletions(-)

-Peff