)]}'
{
  "commit": "1dc13c7e9f47718b51d8206e0b7cc8b244271ce4",
  "tree": "d33b46212d99e1031e8b2311441724b1bfb3ed20",
  "parents": [
    "348290c7ef4b731f3ff851d7922d038e671fea4a"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Dec 03 22:54:23 2024 +0100"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Tue Dec 03 22:54:23 2024 +0100"
  },
  "message": "[gdb/testsuite] Fix gdb.python/py-startup-opt.exp with empty PYTHONDONTWRITEBYTECODE\n\nWhen running test-case gdb.python/py-startup-opt.exp with empty\nPYTHONDONTWRITEBYTECODE:\n...\n$ cd build/gdb/testsuite\n$ PYTHONDONTWRITEBYTECODE\u003d make check \\\n    RUNTESTFLAGS\u003dgdb.python/py-startup-opt.exp\n...\nI get:\n...\nend^M\ndont_write_bytecode is off^M\n(gdb) FAIL: $exp: attr\u003ddont_write_bytecode: testname: input 6: end\n...\n\nThe problem is that the test-case expects dont_write_bytecode to be\non, which is incorrect because PYTHONDONTWRITEBYTECODE only has effect if set\nto a non-empty string [1].\n\nFix this by correctly setting expectations in the test-case.\n\nTested on x86_64-linux, with:\n- PYTHONDONTWRITEBYTECODE\u003d\n- PYTHONDONTWRITEBYTECODE\u003d1\n- unset PYTHONDONTWRITEBYTECODE\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\n[1] https://docs.python.org/3/using/cmdline.html#envvar-PYTHONDONTWRITEBYTECODE\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cf2a2cf6768fa89b4bac2fa11640a90e4d3a488c",
      "old_mode": 33188,
      "old_path": "gdb/testsuite/gdb.python/py-startup-opt.exp",
      "new_id": "014aff5725a62421b954fd6cd0b6443c660ffb49",
      "new_mode": 33188,
      "new_path": "gdb/testsuite/gdb.python/py-startup-opt.exp"
    }
  ]
}