)]}'
{
  "commit": "a4199c0bfe68a7d7de6e44cead3c91e7bd1e328d",
  "tree": "ca583092401d6f9876710d2b57159a0c8d597eb8",
  "parents": [
    "15129aafc3056028aa2694528ac20373f8cd34e4"
  ],
  "author": {
    "name": "Benny Siegert",
    "email": "bsiegert@google.com",
    "time": "Sun Nov 02 10:53:34 2025 +0000"
  },
  "committer": {
    "name": "Benny Siegert",
    "email": "bsiegert@google.com",
    "time": "Sun Nov 09 22:33:32 2025 -0800"
  },
  "message": "unix: fix definition of Statvfs_t for netbsd-arm.\n\nThis will fix the test failure on the netbsd-arm builder, but it is not\nquite a real fix.\n\nstruct statvfs changed between NetBSD 9 and NetBSD 10, with notably the\n\"spare\" member switching from [4]uint32 to [4]uint64. In addition, there\nis a new member at the end with label information, if available. The\nnetbsd-arm builder runs on NetBSD 10, so it runs into an issue\ncasting the binary data into a Statvfs_t with the wrong padding.\n\nI don\u0027t know why the issue does not happen on arm64.\n\nIt does not happen on 386 and amd64 because these builders are running\nNetBSD 9 still.\n\nThe real fix would be to use the statvfs90 compat syscall on NetBSD 10\nand up, but not on 9 and below.\n\nFixes golang/go#76097.\n\nChange-Id: I57ce6651d0ba05027a9fb29ee84c72a5225bcd67\nReviewed-on: https://go-review.googlesource.com/c/sys/+/717100\nRun-TryBot: Benny Siegert \u003cbsiegert@gmail.com\u003e\nTryBot-Result: Gopher Robot \u003cgobot@golang.org\u003e\nReviewed-by: Michael Knyszek \u003cmknyszek@google.com\u003e\nReviewed-by: Tobias Klauser \u003ctobias.klauser@gmail.com\u003e\nLUCI-TryBot-Result: Go LUCI \u003cgolang-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "439548ec9ad484e267e4cf42393282c119e62fca",
      "old_mode": 33188,
      "old_path": "unix/ztypes_netbsd_arm.go",
      "new_id": "50e8e644970dbe150c3ee71ce7ef832bffd69fbc",
      "new_mode": 33188,
      "new_path": "unix/ztypes_netbsd_arm.go"
    }
  ]
}