|
|
Created:
6 years, 5 months ago by sky Modified:
6 years, 4 months ago CC:
chromium-reviews Base URL:
svn://svn.chromium.org/chrome/trunk/src Project:
chromium Visibility:
Public. |
DescriptionAdds tools/whitespace.txt to the list of files that trigger compile
This file is used by the cq to measure loads and other stats. We want
changes to it to result in a compile and test.
BUG=383609
TEST=none
R=iannucci@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=284522
Patch Set 1 #
Messages
Total messages: 17 (0 generated)
lgtm Does/will this change also affect blink?
Right now the only bot running the analyze step is the linux clang bot. I want to turn it on for all try bots (that run the same recipe), but it'll be a while.
The CQ bit was checked by sky@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/sky@chromium.org/403393007/1
The CQ bit was unchecked by commit-bot@chromium.org
No LGTM from a valid reviewer yet. Only full committers are accepted. Even if an LGTM may have been provided, it was from a non-committer or a provisional committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
lgtm
The CQ bit was unchecked by sky@chromium.org
The CQ bit was checked by sky@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/sky@chromium.org/403393007/1
Message was sent while issue was closed.
Change committed as 284522
Message was sent while issue was closed.
On 2014/07/21 22:38:50, I haz the power (commit-bot) wrote: > Change committed as 284522 We have used build/whitespace_file.txt for this for years. Why the new whitespace file?
No idea there. Hopefully one of the guys that created the new file could tell you. On Tue, Jul 22, 2014 at 6:41 AM, <thakis@chromium.org> wrote: > On 2014/07/21 22:38:50, I haz the power (commit-bot) wrote: >> >> Change committed as 284522 > > > We have used build/whitespace_file.txt for this for years. Why the new > whitespace file? > > https://codereview.chromium.org/403393007/ To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
We just pick a folder without OWNER restriction. The tools/whitespace.txt will never be committed so it shouldn't affect the repo. Best regards, Sheng On Tue, Jul 22, 2014 at 9:13 AM, Scott Violet <sky@chromium.org> wrote: > No idea there. Hopefully one of the guys that created the new file > could tell you. > > On Tue, Jul 22, 2014 at 6:41 AM, <thakis@chromium.org> wrote: > > On 2014/07/21 22:38:50, I haz the power (commit-bot) wrote: > >> > >> Change committed as 284522 > > > > > > We have used build/whitespace_file.txt for this for years. Why the new > > whitespace file? > > > > https://codereview.chromium.org/403393007/ > To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
You could make the file have a * in OWNERS. That gives the same effect. -Scott On Tue, Jul 22, 2014 at 9:19 AM, Sheng Yang <sheyang@google.com> wrote: > We just pick a folder without OWNER restriction. The tools/whitespace.txt > will never be committed so it shouldn't affect the repo. > > Best regards, > > Sheng > > > On Tue, Jul 22, 2014 at 9:13 AM, Scott Violet <sky@chromium.org> wrote: >> >> No idea there. Hopefully one of the guys that created the new file >> could tell you. >> >> On Tue, Jul 22, 2014 at 6:41 AM, <thakis@chromium.org> wrote: >> > On 2014/07/21 22:38:50, I haz the power (commit-bot) wrote: >> >> >> >> Change committed as 284522 >> > >> > >> > We have used build/whitespace_file.txt for this for years. Why the new >> > whitespace file? >> > >> > https://codereview.chromium.org/403393007/ > > To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
Message was sent while issue was closed.
Also, build/OWNERS currently contains * too, so build/whitespace_file.txt would work just as well? |