|
|
Created:
8 years, 6 months ago by Avi (use Gerrit) Modified:
8 years, 6 months ago Reviewers:
Mark Mentovai CC:
chromium-reviews Base URL:
svn://svn.chromium.org/chrome/trunk/src Visibility:
Public. |
DescriptionAdded presubmit warnings about base coordinate system.
BUG=132984
TEST=none
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=142578
Patch Set 1 #
Total comments: 4
Patch Set 2 : . #Patch Set 3 : banhammer #Patch Set 4 : ban/warn #Patch Set 5 : real data #Messages
Total messages: 20 (0 generated)
Should it be an error rather than a warning?
https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py File PRESUBMIT.py (right): https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py#newcode34 PRESUBMIT.py:34: _BANNED_FUNCTIONS = ( I would name this _BANNED_FUNCTIONS_OBJC… https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py#newcode286 PRESUBMIT.py:286: file_filter = lambda f: f.LocalPath().endswith(('.cc', '.mm', '.h')) …and omit .cc but include .m.
Once you’re done fixing things up, how many violations will exist in Chrome code where the presubmit script would find them?
> Once you’re done fixing things up, how many violations will exist in Chrome code > where the presubmit script would find them? If they were modified? Re the base calls, there are two legitimate ones that exist; I fixed all the rest. Re the tracking area/rect calls, too many to count :( https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py File PRESUBMIT.py (right): https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py#newcode286 PRESUBMIT.py:286: file_filter = lambda f: f.LocalPath().endswith(('.cc', '.mm', '.h')) I did it this way deliberately. I wanted a general mechanism; if other platforms want to plug into this, they just need to add to the table.
> Re the tracking area/rect calls, too many to count :( If [almost] all of those are wrong, then it’s OK to make this a hard error. Otherwise, it’s best as a warning. https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py File PRESUBMIT.py (right): https://chromiumcodereview.appspot.com/10556015/diff/1/PRESUBMIT.py#newcode286 PRESUBMIT.py:286: file_filter = lambda f: f.LocalPath().endswith(('.cc', '.mm', '.h')) Avi wrote: > I did it this way deliberately. I wanted a general mechanism; if other platforms > want to plug into this, they just need to add to the table. Then give ’em another table to plug into? I don’t see the point in checking for Objective-C-isms in .cc files.
Re the tracking areas, it's hard to say if they're _wrong_. Talk to rsesek about http://code.google.com/p/chromium/issues/detail?id=48709 . We already banned their use. Re the table, do you want me to pre-create it and leave it empty?
Yeah, exactly, an empty table. I don’t know, I’m on the warning/error fence, then. Maybe you can add an extra attribute to your table and have the ones we’re sure we’ve eradicated be errors, and have the ones we can’t decide about be warnings?
OK, please take a look.
LGTM
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/avi@chromium.org/10556015/12001
Try job failure for 10556015-12001 (retry) on linux_chromeos for step "compile" (clobber build). It's a second try, previously, step "compile" failed. http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...
Ha, yeah right!
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/avi@chromium.org/10556015/12001
Try job failure for 10556015-12001 (retry) on android for steps "compile, build" (clobber build). It's a second try, previously, steps "compile, build" failed. http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=android&nu...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/avi@chromium.org/10556015/12001
Try job failure for 10556015-12001 (retry) on linux_chromeos for step "compile" (clobber build). It's a second try, previously, step "compile" failed. http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_chro...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/avi@chromium.org/10556015/12001
Try job failure for 10556015-12001 (retry) on win for step "compile" (clobber build). It's a second try, previously, step "compile" failed. http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/avi@chromium.org/10556015/12001
Change committed as 142578 |