)]}'
{
  "commit": "cd6c17ea89ca811b50a52d243876e78e397ee3ff",
  "tree": "24dccbe9040db5c69ae575cede88ca94bc9bee02",
  "parents": [
    "5afd8ff8df0e0850b4b5671676f4bb057b33dada",
    "18af84b1380cd5af07d5fa09c0cad19d5ef55243"
  ],
  "author": {
    "name": "Stuart Cook",
    "email": "Zalathar@users.noreply.github.com",
    "time": "Tue Dec 02 13:56:32 2025 +1100"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Dec 02 13:56:32 2025 +1100"
  },
  "message": "Rollup merge of #149525 - RalfJung:debuginfo-test-comments, r\u003djieyouxu\n\ndebuginfo/macro-stepping test: extend comments\n\nThose `#locN` markers look like they are debuginfo compiletest magic (since `#break` is debuginfo compiletest magic). However, they are actually just magic strings used by the `check` commands in the test itself. This threw me off when I looked at the test (prompted by a CI failure), so let\u0027s leave a comment for the next poor soul that ends up lost in this test.\n\nAlso, for some reason the lldb instructions do not check for `#loc6`, unlike the gdb instructions. I do not know of an lldb version that actually makes the test pass (do we even run it with lldb at all on CI?), so I won\u0027t try to add a check for loc6, but let\u0027s at least add a comment to increase the chance that someone more knowledgeable about lldb and our test suite notices this in the future.\n",
  "tree_diff": []
}