)]}' { "commit": "6484857c6ac9eef7600e2d49a06a377f950a1ce6", "tree": "66076f8a9d0e0851dd33559492bb49b37c7eec8e", "parents": [ "d77247da9970c7d1ca19298f1136ef262f28213d" ], "author": { "name": "Daniel Wang", "email": "wonderfly@google.com", "time": "Mon Nov 23 15:11:26 2015 -0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Dec 16 21:49:38 2015 -0800" }, "message": "gce_au_worker: Add a loop counter to avoid instance name collision\n\nInstances are named with the timestamp (second precision) when they are created.\nIf multiple instances are created in the same second, name collisions happen.\nWhile this may sound rare, due to the fact that instance names are bound in a\nnon-blocking forloop, this does happen, actually frequently. So we are adding a\nforloop counter as a suffix to avoid collisions.\n\nBUG\u003db:25849966\nTEST\u003dunit test and trybot run against lakitu-pre-cq, with a custom\n gce_tests.json that has multiple test entries.\n\nChange-Id: I1bc29e6322be2e81387215cb152ae73b0f5575ab\nReviewed-on: https://chromium-review.googlesource.com/314111\nCommit-Ready: Daniel Wang \u003cwonderfly@google.com\u003e\nTested-by: Daniel Wang \u003cwonderfly@google.com\u003e\nReviewed-by: Amey Deshpande \u003cameyd@google.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "266f74d7229f3de6ce99f21ac73e41941b23bd94", "old_mode": 33188, "old_path": "au_test_harness/gce_au_worker.py", "new_id": "cf25b6670134c246221ad98978846e7dba901f43", "new_mode": 33188, "new_path": "au_test_harness/gce_au_worker.py" } ] }