)]}'
{
  "commit": "a7c373d26b4edd5e0a4e4ad12dbe78163341ab77",
  "tree": "858c97463fb763f77f596fdfdbc18bf57c6a3bd2",
  "parents": [
    "d9b93ccc244c39cb02fc9a3413dbeeed0ac95e70"
  ],
  "author": {
    "name": "Mike Kruskal",
    "email": "mkruskal@google.com",
    "time": "Tue Nov 03 10:32:55 2026 -0800"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Tue Nov 03 15:26:39 2026 -0800"
  },
  "message": "Fix startup and timeout races in Mutex.AcquireFromCondition test.\n\n`Mutex.AcquireFromCondition` previously used a fixed 500ms sleep to wait for the worker thread to enter `LockWhen`, followed by a 500ms `WaitWithTimeout` to wake it. Under heavy thread-creation contention (such as parallel debug shards on Windows), if the worker thread took longer than 1 second to reach `LockWhen`, the main thread finished its `WaitWithTimeout` before the worker queued on `mu0` and both threads deadlocked indefinitely until the test timed out.\n\nSynchronize using `absl::Notification` once the first condition evaluation runs so the worker is guaranteed to be queued on `mu0`, and have `WaitForCond2` signal `cv` so the main thread can use an unbounded `cv.Wait`.\n\nPiperOrigin-RevId: 1013123821\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "50b982ee4e6c9285eb71d15113e0131c40b7b23b",
      "old_mode": 33188,
      "old_path": "absl/synchronization/mutex_test.cc",
      "new_id": "037043aabeca099d82e63595fc500b2b2986bd0a",
      "new_mode": 33188,
      "new_path": "absl/synchronization/mutex_test.cc"
    }
  ]
}
