)]}'
{
  "commit": "2bba46058789196c1c384896933cbc9692ef4933",
  "tree": "3555d740917b5201d566038cc32a6f1b87441630",
  "parents": [
    "5a43f7f040d45ca1bc0066019131cf71d7836cb8"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Sat Oct 26 11:18:40 2024 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Sat Oct 26 11:31:31 2024 +0100"
  },
  "message": "gdb/testsuite: fix test pattern after switch to -lbl matching\n\nAfter commit:\n\n  commit a1ccc78ea7ba8cad3ff37cbde9b5d3bba0194796\n  Date:   Fri Oct 25 06:14:03 2024 +0200\n\n      [gdb/testsuite] Fix some test-cases for check-read1 (-lbl)\n\nI notice that gdb.base/sect-cmd.exp would sometimes fail.  The problem\nis that by switching to line by line matching we now need to ensure\nthat the gdb_test_multiple patterns match up to the end of the line,\nbut don\u0027t actually include the trailing \\r\\n (yeah, our line by line\nmatching is weird).  We need to be especially careful anywhere \u0027.*\u0027 is\nused as this can potentially match content on a subsequent line.\n\nI have replaced \u0027.*\u0027 with \u0027\\[^\\r\\n\\]*(?\u003d\\r\\n)\u0027, matching everything up\nto the end of the line, but not the end of line itself, and I\u0027ve made\nuse of \u0027(?\u003d\\r\\n)\u0027 in a couple of other places to ensure we match up to\nthe end of the line, but don\u0027t match the line terminator itself.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2a5758a94c622b8999a913dfd0d9d61ef82a6dab",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/sect-cmd.exp",
      "new_id": "49a94cd9019016f5bfb719d1db64a3bf143a9ab0",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/sect-cmd.exp"
    }
  ]
}