|
|
DescriptionAdjust CSS property maximum tracking to be more clang-format friendly.
BUG=649969
Committed: https://crrev.com/dd1a7ad9f71c9e1d990f651f8f1cc15c0130f1e1
Cr-Commit-Position: refs/heads/master@{#420911}
Patch Set 1 #Patch Set 2 : Revert .clang-format #
Total comments: 2
Patch Set 3 : Remove parens #
Messages
Total messages: 29 (15 generated)
dcheng@chromium.org changed reviewers: + thakis@chromium.org
Still need to figure out what to do with the remaining PRESUBMIT.py check in here, since clang-format puts case statements on their own line. But this one is easy-ish at least.
The CQ bit was checked by dcheng@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...
Lgtm Huh why was this a function? In general, I think if some Python script tries to parse a c++ file to extract information, we should probably have that information in some other form and then generate the cpp file from there (and have py load it directly) https://codereview.chromium.org/2368103003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/frame/UseCounter.cpp (right): https://codereview.chromium.org/2368103003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/frame/UseCounter.cpp:582: // 2. Update kMaximumCSSSampleId() with the new maximum value. No parens
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
On 2016/09/25 21:08:13, Nico wrote: > Lgtm > > Huh why was this a function? > > In general, I think if some Python script tries to parse a c++ file to extract > information, we should probably have that information in some other form and > then generate the cpp file from there (and have py load it directly) I have no idea why this is a function. As for making this all generated, it's a bit tricky and I'd like to avoid tying clang-format to fixing this up. The CSS enum values in question are all generated from https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/css/CSSPr..., and there's no real correlation to the order they are currently defined and the UMA reporting value. Parsing C++ is inherently fragile (there's a fair number of false positives from check-webkit-style)... but this is the easiest approach for now. https://codereview.chromium.org/2368103003/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/core/frame/UseCounter.cpp (right): https://codereview.chromium.org/2368103003/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/core/frame/UseCounter.cpp:582: // 2. Update kMaximumCSSSampleId() with the new maximum value. On 2016/09/25 21:08:12, Nico wrote: > No parens Done.
The CQ bit was checked by dcheng@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from thakis@chromium.org Link to the patchset: https://codereview.chromium.org/2368103003/#ps40001 (title: "Remove parens")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by dcheng@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: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by dcheng@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: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by dcheng@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: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by thakis@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Adjust CSS property maximum tracking to be more clang-format friendly. BUG=649969 ========== to ========== Adjust CSS property maximum tracking to be more clang-format friendly. BUG=649969 Committed: https://crrev.com/dd1a7ad9f71c9e1d990f651f8f1cc15c0130f1e1 Cr-Commit-Position: refs/heads/master@{#420911} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/dd1a7ad9f71c9e1d990f651f8f1cc15c0130f1e1 Cr-Commit-Position: refs/heads/master@{#420911}
Message was sent while issue was closed.
A revert of this CL (patchset #3 id:40001) has been created in https://codereview.chromium.org/2383153003/ by dcheng@chromium.org. The reason for reverting is: Yet another test.. |