)]}'
{
  "commit": "64dd0e593f8e438764ced983a9f3f96061df748c",
  "tree": "0baeca49c16ed33238b14954bd931ef863478d35",
  "parents": [
    "00ecbd06930234f70ca6cfa623201489b9e10b71"
  ],
  "author": {
    "name": "Pâris",
    "email": "pmeuleman@chromium.org",
    "time": "Thu May 04 08:23:52 2023"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Thu May 04 08:34:31 2023"
  },
  "message": "Suppress repetitive errors for libs not available in stack tool\n\ntools/python/llvm_symbolizer.py generates error logs, which when\ncalled from the stack symbolization scripts can produce a lot of\nunhelpful logs, notably the error logged when the |lib| parameter\nof |GetSymbolInformation| is not valid:\n\"Can\u0027t run llvm-symbolizer! Given binary is not a valid target. path\u003d%s\"\nSee for instance these logs:\nhttps://chromium-swarm.appspot.com/task?id\u003d61a979f2cac67b10\u0026w\u003dtrue\n\nThis intents to silence most of those errors, especially for the test\nbots, by updating the stack tool:\nthird_party/android_platform/development/scripts/stack et al.\nThis prevent calls to |GetSymbolInformation| if:\n  - the library is not a .so file\n  - the library is not a valid file\nLogs are produced only if the script is run in verbose mode.\n\nBug: 1340999\nChange-Id: I36e21e6f0567809297e83002722743dda30288f3\nReviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4444157\nReviewed-by: Andrew Grieve \u003cagrieve@chromium.org\u003e\nCommit-Queue: Pâris Meuleman \u003cpmeuleman@chromium.org\u003e\nCr-Commit-Position: refs/heads/main@{#1139389}\nNOKEYCHECK\u003dTrue\nGitOrigin-RevId: 51b9b254a06cacbc8378455a2d50868cccd7f480\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "abd8fa75649ec2ff8c4a7c5f1af03b8ec9bef776",
      "old_mode": 33188,
      "old_path": "llvm_symbolizer.py",
      "new_id": "a36aef1c3a63bfc734a908f2e9cbc611404839c7",
      "new_mode": 33188,
      "new_path": "llvm_symbolizer.py"
    }
  ]
}