)]}'
{
  "commit": "2edcfde44c5bf915af5fbe2f25ebafd7ba57fad3",
  "tree": "8627469d2a9ba3da5435a1bbb38b77072dff4702",
  "parents": [
    "336bb2a1c1d24f5db07394a109f7cd6c5b58b10d"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 23 22:03:56 2024 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Sep 23 22:03:56 2024 +0200"
  },
  "message": "[gdb/testsuite] Avoid large timeout in gdb.base/checkpoint.exp\n\nI ran the testsuite in an environment simulating a stressed system, and the\nonly test-cases that timed out in gdb.base were gdb.base/checkpoint.exp and\ngdb.base/checkpoint-ns.exp (which includes gdb.base/checkpoints.exp).\n\nIn test-case gdb.base/checkpoint.exp there\u0027s a part where the timeout is\nincreased with 120 seconds (in the default case that\u0027s from 10 to 130), to\naccommodate for a single command creating 600+ checkpoints.\n\nInstead, rewrite the test to present a gdb prompt each time a checkpoint is\ncreated, for which the default timeout is sufficient.\n\nAlso ensure that the amount of checkpoints added is exactly 600 rather than\n600+.\n\nTested on aarch64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f87f528e1676cca34aa38517b376e0e8cb8688db",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.base/checkpoint.exp",
      "new_id": "31b5a13bb8f94a5ac2b7eafa10407ff5fd985925",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.base/checkpoint.exp"
    }
  ]
}