)]}'
{
  "commit": "9730fe2168ced0889a227855cbc28762f49c1bd5",
  "tree": "62cc39dd3af12821406469c678cde15a73f4974b",
  "parents": [
    "d589045a772678d5ca131f4c8087d001b9258380"
  ],
  "author": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Mon May 11 00:56:25 2026 -0700"
  },
  "committer": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Mon May 11 01:06:49 2026 -0700"
  },
  "message": "Disable fork detection test on qemu.\n\nIts madvise() is still broken today (just in a different way from the\npast - it still returns success on invalid advice flags, which means\nthat we cannot distinguish pre- and post-MADV_WIPEONFORK implementation\nversions of qemu.\n\nI also thought of another way - namely, checking MADV_WIPEONFORK on a\nMAP_SHARED mapping - which qemu correctly refuses, but FreeBSD\u0027s\nlinux.ko does not. So given it\u0027s inaccurate anyway, let\u0027s keep the\ncurrent detection and behaviour as is, namely, that we always draw\nentropy when needing random data when on qemu.\n\nChange-Id: Ib28994d8d22a7360dcfdcc8a6cc5e66f6a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/95107\nReviewed-by: Xiangfei Ding \u003cxfding@google.com\u003e\nCommit-Queue: Rudolf Polzer \u003crpolzer@google.com\u003e\nCommit-Queue: Xiangfei Ding \u003cxfding@google.com\u003e\nAuto-Submit: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "15f3fc0503d5ecd0194517a9bad1919c90224695",
      "old_mode": 33188,
      "old_path": "crypto/rand/fork_detect_test.cc",
      "new_id": "b219f89e597b913c3726ad879c7f7aed00aa43db",
      "new_mode": 33188,
      "new_path": "crypto/rand/fork_detect_test.cc"
    }
  ]
}