)]}' { "commit": "75d8f1bfbbb3dfc870fcbc22f53cd16b66ac7f23", "tree": "176b8e34cf9a327fb7974a444b91fe18eb654a9a", "parents": [ "7638006e103c860f7f5a4ebe4c5822759600e793" ], "author": { "name": "Charlie Mooney", "email": "charliemooney@chromium.org", "time": "Tue Jun 14 21:48:50 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Jun 21 21:48:58 2016" }, "message": "Simplify the qstep.py output\n\nThe qstep.py script for latency measurement has somewhat confusing\noutput currently because it computes the latency with two different\napproaches and displays both results. This CL simply blocks one of the\nmethods and fixed the units on the remaining one to make the output\neasier to read. Now that people other than myself are running this\nscript, this should help prevent confusion.\n\nOver several runs the method that remains proved to be much more stable\nwhen using a robot (as our testing lab will) so that one was picked.\n\nBUG\u003dchromium:620090\nTEST\u003dmanually tested\n\nChange-Id: I88767998b2e713ce1f0656071fca154d32ad0281\nSigned-off-by: Charlie Mooney \u003ccharliemooney@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/352611\nReviewed-by: Shyh-In Hwang \u003cjosephsih@chromium.org\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "c8af55d978ce46b72bcaa3d7c90398303f9a7dbc", "old_mode": 33188, "old_path": "quickstep/latency_measurement.py", "new_id": "e216a6dee874e7dd43b226b15268a487ddb60e78", "new_mode": 33188, "new_path": "quickstep/latency_measurement.py" }, { "type": "modify", "old_id": "9f43fc55525a385815dbe52cd04fd719b9ded23a", "old_mode": 33188, "old_path": "quickstep/qstep.py", "new_id": "a9ee6fcde3995b6f8f91091ed2b0daccdac9dc8d", "new_mode": 33188, "new_path": "quickstep/qstep.py" } ] }