)]}'
{
  "commit": "0dcc6e231d36e41a1f2d07d1aa0094846d684099",
  "tree": "30ee825c77242e0823e63eade60057d15a17af81",
  "parents": [
    "f06254c739023bf3808f9b066c3ece6c1c368d4b"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Wed Jan 15 15:29:33 2020 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Wed Jan 15 21:08:58 2020 +0000"
  },
  "message": "Disable Wycheproof primality test cases on non-x86 (too slow)\n\nI had hoped outputting regularly would solve things, but one of\nChromium\u0027s Android builders is still timing out. Limit it to x86 and\nx86_64, which typically is correlated with a more powerful CPU in\ndownstream CIs.\n\nThis isn\u0027t great, but we still run non-Wycheproof primality tests and\nprimality testing doesn\u0027t have any dedicated platform-specific assembly.\nIt does run platform-specific assembly by way of lower-level BIGNUM\noperations, but those are also tested elsewhere. bn_mod_u16_consttime\ndepends on 32-bit vs 64-bit, but that is covered by running on both\n32-bit and 64-bit x86.\n\nUse the GTest DISABLED_Foo mechanism so they may still be run manually\nwith --gtest_also_run_disabled_tests.\n\nChange-Id: Ie422096db5bb4186145532f4fd2d4063372b8988\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39604\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Adam Langley \u003cagl@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "18a7edca2572b528b135acd67b8db53bbe84e378",
      "old_mode": 33188,
      "old_path": "crypto/fipsmodule/bn/bn_test.cc",
      "new_id": "8fb2ed8401d65d38ea96d060d6b204ebd6529271",
      "new_mode": 33188,
      "new_path": "crypto/fipsmodule/bn/bn_test.cc"
    }
  ]
}