|
|
Chromium Code Reviews
DescriptionFactored stdio parsing out of graph_json.
These functions will be used in a future CL to show debugging info for
stoppage alerts.
Also added additional testing.
BUG=catapult:#3132
Review-Url: https://codereview.chromium.org/2620713002
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/0c9efe760d2cb739ac5cc81463961afd0a4c710b
Patch Set 1 #Patch Set 2 : Use same links in tests as in datastore #Patch Set 3 : fix tests #Patch Set 4 : fix more typos in unit tests #
Total comments: 4
Messages
Total messages: 27 (21 generated)
The CQ bit was checked by sullivan@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
sullivan@chromium.org changed reviewers: + eakuefner@chromium.org
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: Catapult Linux Tryserver on master.tryserver.client.catapult (JOB_FAILED, https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Li...) Catapult Mac Tryserver on master.tryserver.client.catapult (JOB_FAILED, https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Ma...)
The CQ bit was checked by sullivan@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: Catapult Mac Tryserver on master.tryserver.client.catapult (JOB_FAILED, https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Ma...)
The CQ bit was checked by sullivan@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: Catapult Linux Tryserver on master.tryserver.client.catapult (JOB_FAILED, https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Li...) Catapult Mac Tryserver on master.tryserver.client.catapult (JOB_FAILED, https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Ma...)
The CQ bit was checked by sullivan@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... File dashboard/dashboard/common/utils.py (right): https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... dashboard/dashboard/common/utils.py:471: no_details = (None, None, None, None, None) I'm a little worried about using such a large tuple because of the potential for confusion. Is it worth using a POD instead? Up to you. https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... dashboard/dashboard/common/utils.py:503: bot = re.sub(r'[ \(\)]', '_', bot) Is this needed because it's a substitution that Logdog makes? Otherwise, urllib.quote will already urlencode the parens and spaces.
Would also like BUG= here.
Description was changed from ========== Factored stdio parsing out of graph_json. These functions will be used in a future CL to show debugging info for stoppage alerts. Also added additional testing. ========== to ========== Factored stdio parsing out of graph_json. These functions will be used in a future CL to show debugging info for stoppage alerts. Also added additional testing. BUG=catapult:#3132 ==========
The CQ bit was checked by sullivan@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 60001, "attempt_start_ts": 1483999962330130,
"parent_rev": "cc4ede7dec5c85f6166b882d553fc931b65bc464", "commit_rev":
"0c9efe760d2cb739ac5cc81463961afd0a4c710b"}
Message was sent while issue was closed.
Description was changed from ========== Factored stdio parsing out of graph_json. These functions will be used in a future CL to show debugging info for stoppage alerts. Also added additional testing. BUG=catapult:#3132 ========== to ========== Factored stdio parsing out of graph_json. These functions will be used in a future CL to show debugging info for stoppage alerts. Also added additional testing. BUG=catapult:#3132 Review-Url: https://codereview.chromium.org/2620713002 Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapu... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
Message was sent while issue was closed.
https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... File dashboard/dashboard/common/utils.py (right): https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... dashboard/dashboard/common/utils.py:471: no_details = (None, None, None, None, None) On 2017/01/09 21:45:19, eakuefner wrote: > I'm a little worried about using such a large tuple because of the potential for > confusion. Is it worth using a POD instead? Up to you. I think it's okay because this method is mostly used by the two methods below. https://codereview.chromium.org/2620713002/diff/60001/dashboard/dashboard/com... dashboard/dashboard/common/utils.py:503: bot = re.sub(r'[ \(\)]', '_', bot) On 2017/01/09 21:45:19, eakuefner wrote: > Is this needed because it's a substitution that Logdog makes? Otherwise, > urllib.quote will already urlencode the parens and spaces. Yes, exactly, logdog does totally different substitution than url encoding. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
