)]}'
{
  "commit": "785bdd9fa781f3e55c77d6f294a6c02c729e49ef",
  "tree": "9cdcec3e16301d9024bf705eaa3c0ba3891db6df",
  "parents": [
    "0d7014e1b20ead9739f1fce54b316152413601c3"
  ],
  "author": {
    "name": "Sam Clegg",
    "email": "sbc@chromium.org",
    "time": "Fri Jan 06 16:40:26 2023"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Jan 06 16:40:26 2023"
  },
  "message": "Don\u0027t rebuilt the cache every time the config file changes. NFC (#18462)\n\nThis effectively reverts #11196.  It turns out this caused a lot of\r\nunnecessary rebuilding for developers without much real benefit.\r\n\r\nIf we include the config hash then ever time the config file is edited\r\n(for example, to add or remove something from WASM_ENGINES or\r\nJS_ENGINES, which are only used during testing) all the libraries would\r\nthen get needlessly rebuilt.\r\n\r\nSince the sanity file already includes the emscripten version and llvm\r\nversion that should catch most of he cases where the libraries really do\r\nrequire a rebuild.\r\n\r\nChanges to the specific llvm or emscripten GIT revision do not cause the\r\ncache to get re-built even if we do include the config file hash so it\r\nisn\u0027t really providing any usefull benefit.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bfb9bb723f7abe079fa9cedcfc10d69410bbf74f",
      "old_mode": 33188,
      "old_path": "test/test_sanity.py",
      "new_id": "29094112c265a49591f9b252169384812ef07343",
      "new_mode": 33188,
      "new_path": "test/test_sanity.py"
    },
    {
      "type": "modify",
      "old_id": "0810b8357c7be86355ed59d5b5c52f65a17190c7",
      "old_mode": 33188,
      "old_path": "tools/shared.py",
      "new_id": "7b302fab9567de24ab4a1b141ec04027f226dd69",
      "new_mode": 33188,
      "new_path": "tools/shared.py"
    }
  ]
}