)]}'
{
  "commit": "0d00a5f9d429c7cbae87b9d1057fb4f9e4ae18c2",
  "tree": "6bac754bc07752004aaa97a3c9a6cbedab431b8c",
  "parents": [
    "25035d2122ea23c943f0c77360dfc0770750a2e6"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Apr 25 08:33:56 2023 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Apr 25 08:33:56 2023 +0200"
  },
  "message": "[gdb/testsuite] Add warning for timeout in accept_gdb_output\n\nIn accept_gdb_output we have:\n...\n            timeout {\n                # Assume a timeout means we somehow missed the\n                # expected result, and carry on.\n                return 0\n            }\n...\n\nThe timeout is silent, and though in some places the return value is checked,\nthis is not done consistently, and consequently there are silent timeouts\nwhen running the TUI testsuite (gdb.tui/*.exp and gdb.python/tui*.exp).\n\nEach timeout is 10 seconds, and there are 5 in total in the TUI tests, taking\n50 seconds overall:\n...\nreal    1m0.275s\nuser    0m10.440s\nsys     0m1.343s\n...\n\nWith an entire testsuite run taking about 30 minutes, that is about 2.5% of\nthe time spent waiting in TUI tests.\n\nLet\u0027s make the timeouts visible using a warning, such that they can be fixed.\n\nTested on x86_64-linux.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "05edfe9a5b1b07d73e5d6fb573748822aebcd5bd",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/tuiterm.exp",
      "new_id": "ff38af082dab97dd6f44c60ffaf410ba91e36d3d",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/tuiterm.exp"
    }
  ]
}