)]}'
{
  "commit": "1bcaeecb7fd8a23f05033bc9a340696b685db17f",
  "tree": "28b5ae5a4ce20d8b1eaa34f1cd1b32c99ce9c703",
  "parents": [
    "13d4a4bd5a7a686d8d5473a4c93b7798de97f745"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Feb 20 11:16:02 2023 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Feb 20 11:16:02 2023 +0100"
  },
  "message": "[gdb/testsuite] Add xfail case in gdb.python/py-record-btrace.exp\n\nI came across:\n...\ngdb) PASS: gdb.python/py-record-btrace.exp: prepare record: stepi 100\npython insn \u003d r.instruction_history^M\nwarning: Non-contiguous trace at instruction 1 (offset \u003d 0x3e10).^M\n(gdb) FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn \u003d r.i\\\nnstruction_history\n...\n\nI\u0027m assuming it\u0027s the same root cause as for the already present XFAIL.\n\nFix this by recognizing above warning in the xfail regexp.\n\nTested on x86_64-linux, although sofar I was not able to trigger the warning\nagain.\n\nApproved-By: Markus T. Metzger \u003cmarkus.t.metzger@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c055a882f859b62e19b202115dff2a81f22a340b",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-record-btrace.exp",
      "new_id": "703db0ce8e144f15735662d2fd6392592da5a203",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-record-btrace.exp"
    }
  ]
}
