)]}' { "commit": "36170420e329a8d6229eb89b38d8680cf39f1d53", "tree": "347bd307d99d456054c72aa4759434c64e868275", "parents": [ "746723ba6c1b36d6ec88de3f772a80a8d2de6e4d" ], "author": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Oct 13 11:06:36 2021 +0200" }, "committer": { "name": "Tom de Vries", "email": "tdevries@suse.de", "time": "Wed Oct 13 11:06:36 2021 +0200" }, "message": "[gdb/testsuite] Fix test name in gdb.python/python.exp\n\nWhen running test-case gdb.python/python.exp, we have:\n...\nPASS: gdb.python/python.exp: starti via gdb.execute, not from tty\nPASS: gdb.python/python.exp: starti via interactive input\n...\n\nThe two tests are instances of the same test, with different values for\nstarti command argument from_tty, so it\u0027s strange that the test names are so\ndifferent.\n\nThis is due to using a gdb_test nested in a gdb_test_multiple, with the inner\none using a different test name than the outer one. [ That could still make\nsense if both produced passes, but that\u0027s not the case here. ]\n\nFix this by using $gdb_test_name, such that we have:\n...\nPASS: gdb.python/python.exp: starti via gdb.execute, not from tty\nPASS: gdb.python/python.exp: starti via gdb.execute, from tty\n...\n\nAlso make this more readable by using variables.\n\nTested on x86_64-linux.\n", "tree_diff": [ { "type": "modify", "old_id": "a81cd5c850e1a3fd42692d86a753fae15a54a3fe", "old_mode": 33188, "old_path": "gdb/testsuite/gdb.python/python.exp", "new_id": "7f9c2b4af7ff011a09a67c8d96efe93f2d3cbd56", "new_mode": 33188, "new_path": "gdb/testsuite/gdb.python/python.exp" } ] }