)]}' { "commit": "ed1b95a44b38f2a2a1fe82747524344c7710074c", "tree": "a4e9a8ec74f47e212398b7113d0116cf1fadc79d", "parents": [ "ed9b2a07665e1531f9e81bd42ef94d789de2c004" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu Dec 12 19:04:51 2019 -0500" }, "committer": { "name": "Commit Bot", "email": "commit-bot@chromium.org", "time": "Fri Dec 13 05:25:37 2019 +0000" }, "message": "pre-upload: overhaul commit progress output\n\nOur existing output shows each commit \u0026 hook being run, and then\ndumps the full failure messages at the end. Lets switch to the\nstyle used in AOSP repohooks where output is more dynamic and\nimmediate when things go wrong. For single commits this isn\u0027t a\nbig deal, but for multiple commits, this can be huge.\n\nBUG\u003dNone\nTEST\u003d`repo upload` shows commit progress\n\nChange-Id: I5b14488b7fe22f9d2e29adf7201db7f00590872a\nReviewed-on: https://chromium-review.googlesource.com/c/chromiumos/repohooks/+/1965403\nReviewed-by: Michael Mortensen \u003cmmortensen@google.com\u003e\nCommit-Queue: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "35c0433e011c9ff8e660f2414c869bc7fb5a6175", "old_mode": 33188, "old_path": "errors.py", "new_id": "35ede84ce65c17fc61756c17078fe7685d4ff33e", "new_mode": 33188, "new_path": "errors.py" }, { "type": "modify", "old_id": "1ab1ef8218b088e1fe9fc7cb6860e4429611e89d", "old_mode": 33261, "old_path": "pre-upload.py", "new_id": "e5f61e3dd2b31d4f25da4f99a72adeee0c7607e4", "new_mode": 33261, "new_path": "pre-upload.py" } ] }