)]}'
{
  "commit": "ee2ff2eaa51ab83e24a14feae968cd575276e6a7",
  "tree": "25c4b2f37068891370a720c1eb3066d70c4de1d2",
  "parents": [
    "203a9824347042e0f7580994cbe7a1eb8dc1e893"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 27 11:33:12 2021 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 27 11:33:12 2021 +0200"
  },
  "message": "[gdb/testsuite] Fix gdb.base/dcache-flush.exp\n\nWhen running test-case gdb.base/dcache-flush.exp on ubuntu 18.04.5, I run into:\n...\n(gdb) PASS: gdb.base/dcache-flush.exp: p var2\ninfo dcache^M\nDcache 4096 lines of 64 bytes each.^M\nContains data for Thread 0x7ffff7fc6b80 (LWP 3551)^M\nLine 0: address 0x7fffffffd4c0 [47 hits]^M\nLine 1: address 0x7fffffffd500 [31 hits]^M\nLine 2: address 0x7fffffffd5c0 [7 hits]^M\nCache state: 3 active lines, 85 hits^M\n(gdb) FAIL: gdb.base/dcache-flush.exp: check dcache before flushing\n...\nThe regexp expects \"Contains data for process $decimal\".\n\nThis is another case of thread_db_target::pid_to_str being used.\n\nFix this by updating the regexp.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ac10b9fab1cca722d493008a6d15b2b4269b67a",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/dcache-flush.exp",
      "new_id": "ff59b2bb7ae4ffa85e9e4f9586c649d885e1359b",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/dcache-flush.exp"
    }
  ]
}