)]}'
{
  "commit": "f6ef747a7c7a80be7f53a832d0a7d28617071c3d",
  "tree": "a47f024e9ed54b9269f78f6b799183173598b1af",
  "parents": [
    "dc51aedd5302677f80bb09e7df627e441111dd3f"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Sun Jun 28 04:03:45 2026 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Mon Jun 29 07:54:42 2026 -0700"
  },
  "message": "t5551: put many-tags case into its own repo\n\nMost of the t5551 http fetch tests use a handful of refs. But there are\na few test cases which check our handling of large numbers of refs.\nThese tests use the same server-side repo, so all subsequent tests end\nup having to consider those extra refs, too.\n\nThe result is that the test script is a bit slower than it needs to be.\nIn a normal run, moving the \"2,000 tags\" test into its own repo drops my\nruntime for the whole script from ~2.7s to ~1.9s.\n\nThis is a modest gain, but when we add the \"--long\" flag it gets much\nbigger. There we trigger a test (marked with EXPENSIVE) that adds\n100,000 tags, and the script runtime jumps to ~95s. But if we use the\nsame \"many tags\" repo for that, our runtime drops to just ~37s.\n\nThis is a pretty easy win to drop the cost of the script. It may even be\na larger gain on a heavily loaded system, since one of the main costs\nhere is unpacked refs, which are heavy on system time and I/O costs.\n\nIt\u0027s possible we are reducing test coverage, since all of those other\ntests were inadvertently using large ref advertisements (and thus could\nhave uncovered some unexpected interaction). But that seems somewhat\nunlikely; the tests targeted at the large number of refs are doing\nroughly similar things to the other tests.\n\nNote that the real performance culprit is the 100k-tag --long test, not\nthe 2k-tag one. So we could just let the 100k one use its own repo, and\nkeep the 2k tags in the main repo. But since these two tests are\nsomewhat interlinked, it\u0027s easier to just move them both (and it does\nprovide a small gain even for the 2000-tag test). I also notice that the\n2000-tag test is gated on the CMDLINE_LIMIT prereq, and without that the\nlater EXPENSIVE test will fail (since we won\u0027t have a too-many-refs\nclone). Nobody seems to have noticed or complained after many years, and\nI left it alone for this patch.\n\nSigned-off-by: Jeff King \u003cpeff@peff.net\u003e\n[jc: made the new \"many-tags.git\" bare to match the original \"repo.git\"]\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e236e526f0defb22497c4c3c449614884ba3bf01",
      "old_mode": 33261,
      "old_path": "t/t5551-http-fetch-smart.sh",
      "new_id": "dcff0bc7d46421dc8793b23d831b528b3778a7c8",
      "new_mode": 33261,
      "new_path": "t/t5551-http-fetch-smart.sh"
    }
  ]
}