|
|
Chromium Code Reviews|
Created:
4 years ago by kdzwinel Modified:
4 years ago CC:
apavlov+blink_chromium.org, blink-reviews, caseq+blink_chromium.org, chromium-reviews, devtools-reviews_chromium.org, kozyatinskiy+blink_chromium.org, lushnikov+blink_chromium.org, pfeldman+blink_chromium.org, pfeldman Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDevTools: Do not lint front_end/protocol_externs.js.
This file seems to be autogenerated and currently produces ~1k eslint errors.
BUG=none
R=chenwilliam
Committed: https://crrev.com/02f72919bf98093b7c60b06112d1150099fbe7c1
Cr-Commit-Position: refs/heads/master@{#437991}
Patch Set 1 #Patch Set 2 : Add myself to the AUTHORS file #Messages
Total messages: 19 (8 generated)
PTAL
chenwilliam@chromium.org changed reviewers: + dgozman@chromium.org
Thanks for the patch. I think this happens when you're running "compile_frontend.py" (the closure compiler typecheck) which generates protocol_externs.js and then you run eslint while closure is running and compile_frontend.py hasn't deleted the generated file yet. A cleaner approach might be to generate the protocol externs file outside of front_end (e.g. devtools/ or devtools/.generated). It's on my to-do list to clean up the .eslintignore file since Pavel suggested we can use the "skip_compilation" property in module.json to automatically exclude files from linting. In short, I think this is a good quick solution. +dgozman since I'm not an owner.
On 2016/12/08 at 23:47:59, chenwilliam wrote: > Thanks for the patch. I think this happens when you're running "compile_frontend.py" (the closure compiler typecheck) which generates protocol_externs.js and then you run eslint while closure is running and compile_frontend.py hasn't deleted the generated file yet. A cleaner approach might be to generate the protocol externs file outside of front_end (e.g. devtools/ or devtools/.generated). It's on my to-do list to clean up the .eslintignore file since Pavel suggested we can use the "skip_compilation" property in module.json to automatically exclude files from linting. In short, I think this is a good quick solution. > > +dgozman since I'm not an owner. Ah, you are correct! There was `protocol_externs.js` left in my folder after aborted closure compilation. Thank you for all the information.
lgtm
The CQ bit was checked by chenwilliam@chromium.org
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
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
On 2016/12/09 20:49:27, commit-bot: I haz the power wrote: > Try jobs failed on following builders: > chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, > http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) @kdzwinel - Please add yourself to the AUTHORS file and sign the CLA. Thanks! "If you are a new contributor, please visit http://www.chromium.org/developers/contributing-code and read the "Legal" section If you are a chromite, verify the contributor signed the CLA."
On 2016/12/09 at 21:41:17, chenwilliam wrote: > On 2016/12/09 20:49:27, commit-bot: I haz the power wrote: > > Try jobs failed on following builders: > > chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, > > http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...) > > @kdzwinel - Please add yourself to the AUTHORS file and sign the CLA. Thanks! > > "If you are a new contributor, please visit > http://www.chromium.org/developers/contributing-code and read the "Legal" section > If you are a chromite, verify the contributor signed the CLA." Updated, thanks!
The CQ bit was checked by chenwilliam@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from dgozman@chromium.org Link to the patchset: https://codereview.chromium.org/2566553002/#ps20001 (title: "Add myself to the AUTHORS file")
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": 20001, "attempt_start_ts": 1481587247552030,
"parent_rev": "808c7297de83582bd9faa0cfab62c7b811e5d977", "commit_rev":
"a5934002d2c02c7bcb676744d8f0fbe8db79ad6f"}
Message was sent while issue was closed.
Description was changed from ========== DevTools: Do not lint front_end/protocol_externs.js. This file seems to be autogenerated and currently produces ~1k eslint errors. BUG=none R=chenwilliam ========== to ========== DevTools: Do not lint front_end/protocol_externs.js. This file seems to be autogenerated and currently produces ~1k eslint errors. BUG=none R=chenwilliam Review-Url: https://codereview.chromium.org/2566553002 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== DevTools: Do not lint front_end/protocol_externs.js. This file seems to be autogenerated and currently produces ~1k eslint errors. BUG=none R=chenwilliam Review-Url: https://codereview.chromium.org/2566553002 ========== to ========== DevTools: Do not lint front_end/protocol_externs.js. This file seems to be autogenerated and currently produces ~1k eslint errors. BUG=none R=chenwilliam Committed: https://crrev.com/02f72919bf98093b7c60b06112d1150099fbe7c1 Cr-Commit-Position: refs/heads/master@{#437991} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/02f72919bf98093b7c60b06112d1150099fbe7c1 Cr-Commit-Position: refs/heads/master@{#437991} |
