)]}'
{
  "commit": "2a01ef8ca31ab1cb889485ba8d9a20c7ba7ab54f",
  "tree": "b4220bb8abfbd3deef190ca2825065b1321820c4",
  "parents": [
    "92b269f5c5e5c1d51e9318003caf8ae9d076b4e9"
  ],
  "author": {
    "name": "Jeff King",
    "email": "peff@peff.net",
    "time": "Thu Aug 06 01:31:47 2015 -0400"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Aug 07 11:50:28 2015 -0700"
  },
  "message": "test-lib: turn off \"-x\" tracing during chain-lint check\n\nNow that GIT_TEST_CHAIN_LINT is on by default, running:\n\n    ./t0000-basic.sh -x --verbose-only\u003d1\n\nstarts with:\n\n    expecting success:\n            find .git/objects -type f -print \u003eshould-be-empty \u0026\u0026\n            test_line_count \u003d 0 should-be-empty\n\n    + exit 117\n    error: last command exited with $?\u003d117\n    + find .git/objects -type f -print\n    + test_line_count \u003d 0 should-be-empty\n    + test 3 !\u003d 3\n    + wc -l\n    + test 0 \u003d 0\n    ok 1 - .git/objects should be empty after git init in an empty repo\n\nThis is confusing, as the \"exit 117\" line and the error line\n(which is printed in red, no less!) are not part of the test\nat all, but are rather in the separate chain-lint test_eval.\nLet\u0027s unset the \"trace\" variable when eval-ing the chain\nlint check, which avoids this.\n\nNote that we cannot just do a one-shot variable like:\n\n    trace\u003d test_eval ...\n\nas the behavior of one-shot variables for function calls\nis not portable.\n\nSigned-off-by: Jeff King \u003cpeff@peff.net\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "281c1eca0925664a1bddec0e2edca017f68a1a47",
      "old_mode": 33188,
      "old_path": "t/test-lib.sh",
      "new_id": "bc20185b51ba85db9f12659096b5ca859206ca35",
      "new_mode": 33188,
      "new_path": "t/test-lib.sh"
    }
  ]
}