)]}'
{
  "commit": "5c534de59c845a59f9fd3493ee36bf4bf54ab49b",
  "tree": "253e8cfaedd52de5215966cdd108f228d1e1c124",
  "parents": [
    "fd56e6b3a856a68600c843bc5da8d3e2b5bd33e1"
  ],
  "author": {
    "name": "Mike Kruskal",
    "email": "mkruskal@google.com",
    "time": "Thu Oct 22 15:29:36 2026 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Fri Oct 23 10:58:44 2026 -0700"
  },
  "message": "Skip building non-test targets in Windows MSVC Bazel test runs.\n\nIn Abseil, many benchmarks are defined as cc_binary targets with tags \u003d [\"benchmark\"], so --test_tag_filters\u003d-benchmark does not prevent bazel test from compiling and linking them alongside @google_benchmark. Enabling --build_tests_only on windows-msvc (while keeping --nobuild_tests_only on windows-clangcl for Windows benchmark build coverage) avoids compiling ~85 benchmark binaries across the six slow MSVC matrix jobs.\n\nPiperOrigin-RevId: 1005099652\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9ca58b2f1a9ca46d3e616fb00519b9579035c4c0",
      "old_mode": 33188,
      "old_path": ".bazelrc",
      "new_id": "96a34792ea46169584061ceaa9bfb8445c4f2586",
      "new_mode": 33188,
      "new_path": ".bazelrc"
    }
  ]
}