Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(12)

Issue 2708803003: idl_parser: Always use PLY from third_party. (Closed)

Created:
3 years, 10 months ago by Raphael Kubo da Costa (rakuco)
Modified:
3 years, 10 months ago
Reviewers:
haraken, bashi, Yuki
CC:
chromium-reviews
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

idl_parser: Always use PLY from third_party. Stop trying to import PLY from a system installation and preferring it over the version in third_party: doing so brings the risk of incompatibilities, especially when running the unit tests. See https://codereview.chromium.org/2704653002/, for example, where the errors remain the same, but the structure output by PLY is different. R=bashi@chromium.org,haraken@chromium.org,yukishiino@chromium.org Review-Url: https://codereview.chromium.org/2708803003 Cr-Commit-Position: refs/heads/master@{#451742} Committed: https://chromium.googlesource.com/chromium/src/+/adf0559c06874185a1eb8f27a46871477d7ab0d9

Patch Set 1 #

Total comments: 1

Patch Set 2 : Use sys.path.insert() #

Unified diffs Side-by-side diffs Delta from patch set Stats (+9 lines, -30 lines) Patch
M tools/idl_parser/idl_lexer.py View 1 1 chunk +4 lines, -14 lines 0 comments Download
M tools/idl_parser/idl_parser.py View 1 1 chunk +5 lines, -16 lines 0 comments Download

Messages

Total messages: 18 (8 generated)
Raphael Kubo da Costa (rakuco)
PTAL. This is the reason I was getting different test expectations in https://codereview.chromium.org/2704653002/: I have ...
3 years, 10 months ago (2017-02-21 10:24:16 UTC) #1
haraken
LGTM
3 years, 10 months ago (2017-02-21 10:29:08 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2708803003/1
3 years, 10 months ago (2017-02-21 10:36:06 UTC) #4
Yuki
LGTM. This is what bashi@ was suspicious about. bashi@ is off tomorrow, and I think ...
3 years, 10 months ago (2017-02-21 10:39:26 UTC) #5
Raphael Kubo da Costa (rakuco)
Thanks, I've uploaded patch v2 using sys.path.insert(). I'll re-check the CQ box to land it.
3 years, 10 months ago (2017-02-21 10:43:40 UTC) #7
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2708803003/20001
3 years, 10 months ago (2017-02-21 10:44:00 UTC) #10
commit-bot: I haz the power
Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/386403)
3 years, 10 months ago (2017-02-21 11:53:08 UTC) #12
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2708803003/20001
3 years, 10 months ago (2017-02-21 11:56:28 UTC) #14
commit-bot: I haz the power
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/chromium/src/+/adf0559c06874185a1eb8f27a46871477d7ab0d9
3 years, 10 months ago (2017-02-21 12:59:06 UTC) #17
bashi
3 years, 10 months ago (2017-02-21 13:50:15 UTC) #18
Message was sent while issue was closed.
lgtm. Thanks yukishiino@ for the follow-up!

Powered by Google App Engine
This is Rietveld 408576698