|
|
Created:
5 years, 9 months ago by mikecase (-- gone --) Modified:
5 years, 9 months ago CC:
chromium-reviews, jbudorick+watch_chromium.org, klundberg+watch_chromium.org, yfriedman+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionAdds option to allow lint.py script to exit with nonzero exit status (fail builds).
We want to remove downstream lint script. We will need this script to be able to fail
builds if we want to replace the downstream script with this one.
BUG=266140
Committed: https://crrev.com/2b6f0c85fc4dcdb1746c4ac717b4b71c96e6e22a
Cr-Commit-Position: refs/heads/master@{#319481}
Patch Set 1 #
Messages
Total messages: 19 (7 generated)
mikecase@chromium.org changed reviewers: + aurimas@chromium.org
Why do we need an option for this? When do we want not to fail builds?
On 2015/03/05 00:48:19, aurimas wrote: > Why do we need an option for this? When do we want not to fail builds? The upstream lint.py will currently never fail the build. # Lint errors do not fail the build. return 0 Currently, if you build you get quite a few lint errors. So if I make the change to have the script always fail the build, it would cause lots of stuff to fail. Once all the current lint errors are fixed it would be nice to make this script fail builds so people don't make new lint errors. Really this change is so I can delete the downstream lint script. That downstream lint script is run by some of the bots (downstream clang builder for example) and to replace it I need the upstream lint script to fail (nonzero exit status) for the bots to show up red if there are lint errors.
lgtm
The CQ bit was checked by mikecase@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/982683002/1
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
mikecase@chromium.org changed reviewers: + cjhopman@chromium.org
+ cjhopman for review of build/android/gyp. Also, cjhopman, would it be ok with you if I moved lint.py from build/android/gyp/lint.py to build/android/lint/lint.py?
On 2015/03/05 17:52:03, mikecase wrote: > + cjhopman for review of build/android/gyp. > > Also, cjhopman, would it be ok with you if I moved lint.py from > build/android/gyp/lint.py to build/android/lint/lint.py? lgtm I would prefer if it stayed in build/android/gyp. Why do you want to move it?
The CQ bit was checked by mikecase@chromium.org
The CQ bit was unchecked by mikecase@chromium.org
On 2015/03/06 01:29:33, cjhopman wrote: > On 2015/03/05 17:52:03, mikecase wrote: > > + cjhopman for review of build/android/gyp. > > > > Also, cjhopman, would it be ok with you if I moved lint.py from > > build/android/gyp/lint.py to build/android/lint/lint.py? > > lgtm > > I would prefer if it stayed in build/android/gyp. Why do you want to move it? Not a big deal, I'm fine with leaving it. Some of the bots that are using the downstream lint script (like the clang builder) I'm changing to use this lint script instead. Since they just call the script directly and not indirectly through building, I thought it was a little awkward for the script to be in gyp/. Also the lint/ folder already exists and the only thing it has is the lint_suppression xml created by this script.
The CQ bit was checked by mikecase@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/982683002/1
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/2b6f0c85fc4dcdb1746c4ac717b4b71c96e6e22a Cr-Commit-Position: refs/heads/master@{#319481} |