)]}'
{
  "commit": "0e471fde0742bbbc8e34f0d082d1b35c19aee96f",
  "tree": "4363dd29eb1c96ebf5832e42c1ee6f0258fd5f3b",
  "parents": [
    "08b326ee0a6384508703f9187905bb00bfe3d5d9"
  ],
  "author": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Wed Jun 08 14:04:36 2022 +0100"
  },
  "committer": {
    "name": "Andrew Burgess",
    "email": "aburgess@redhat.com",
    "time": "Thu Jun 09 14:40:48 2022 +0100"
  },
  "message": "gdb/testsuite: handle errors better in test_compiler_info\n\nNow that get_compiler_info might actually fail (if the language is not\nhandled), then we should try to handle this failure better in\ntest_compiler_info.\n\nAfter this commit, if get_compiler_info fails then we will return a\nsuitable result depending on how the user called test_compiler_info.\n\nIf the user does something like:\n\n  set version [test_compiler_info \"\" \"unknown-language\"]\n\nThen test_compiler_info will return an empty string.  My assumption is\nthat the user will be trying to match \u0027version\u0027 against something, and\nthe empty string hopefully will not match.\n\nIf the user does something like:\n\n  if { [test_compiler_info \"some_pattern\" \"unknown-language\"] } {\n    ....\n  }\n\nThen test_compiler_info will return false which seems the obvious\nchoice.\n\nThere should be no change in the test results after this commit.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e530ba05a61cb31427a86b57312c085258ee100c",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/lib/gdb.exp",
      "new_id": "e28c33e8455b5fda65b3d358f311c9fba01b8e59",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/lib/gdb.exp"
    }
  ]
}