|
|
Chromium Code Reviews
DescriptionWebUI: disable optimizations (vulcanize) in debug builds
When enable_vulcanize = true, HTML/CSS and JS are combined and optimized.
This takes a little more build-time work, but produces faster pages
for users but also munges the code a bunch.
Let's disable the extra compile-time stuff and make the code cleaner
for developers (i.e. in debug builds by default).
R=sky@chromium.org
BUG=673825, 691965
Review-Url: https://codereview.chromium.org/2654723002
Cr-Commit-Position: refs/heads/master@{#451240}
Committed: https://chromium.googlesource.com/chromium/src/+/6bd4c19f45d6e2bba69f9668516a829f39ca9a1f
Patch Set 1 : no dep #Patch Set 2 : add comment #Messages
Total messages: 34 (24 generated)
Patchset #1 (id:1) has been deleted
The CQ bit was checked by dbeam@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...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
Description was changed from ========== WebUI: turn off vulcanize for debug builds R= BUG=673825 ========== to ========== WebUI: turn off vulcanize for debug builds R=brettw@chromium.org BUG=673825 ==========
dbeam@chromium.org changed reviewers: + brettw@chromium.org
Description was changed from ========== WebUI: turn off vulcanize for debug builds R=brettw@chromium.org BUG=673825 ========== to ========== WebUI: disable optimizations (vulcanize) in debug builds R=brettw@chromium.org BUG=673825 ==========
The CQ bit was checked by dbeam@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...
On 2017/02/14 at 20:48:36, dbeam wrote: > LGTM. Perhaps add a comment in the CL description, that optimizations make the prod code faster, but the tests slower (because they load the entire JS/HTML bundle for each unit test).
Description was changed from ========== WebUI: disable optimizations (vulcanize) in debug builds R=brettw@chromium.org BUG=673825 ========== to ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=brettw@chromium.org BUG=673825 ==========
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2017/02/14 at 20:50:10, dpapad wrote: > On 2017/02/14 at 20:48:36, dbeam wrote: > > > > LGTM. Perhaps add a comment in the CL description, that optimizations make the prod code faster, but the tests slower (because they load the entire JS/HTML bundle for each unit test). Also, maybe link this CL to issue 691965 too.
ping brettw@
Description was changed from ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=brettw@chromium.org BUG=673825 ========== to ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=brettw@chromium.org BUG=673825,691965 ==========
dpapad@chromium.org changed reviewers: + dpapad@chromium.org
sky@chromium.org changed reviewers: + sky@chromium.org
LGTM - but please add a comment as to why the flag is based on build type.
Description was changed from ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=brettw@chromium.org BUG=673825,691965 ========== to ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=sky@chromium.org BUG=673825,691965 ==========
dbeam@chromium.org changed reviewers: - brettw@chromium.org
On 2017/02/17 00:10:05, sky wrote: > LGTM - but please add a comment as to why the flag is based on build type. Done.
The CQ bit was checked by dbeam@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org, dpapad@chromium.org Link to the patchset: https://codereview.chromium.org/2654723002/#ps40001 (title: "add comment")
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_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
The CQ bit was checked by dbeam@chromium.org
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": 40001, "attempt_start_ts": 1487300278371590,
"parent_rev": "7234ea5d5045f6fedbc01503613cc26a2e264670", "commit_rev":
"6bd4c19f45d6e2bba69f9668516a829f39ca9a1f"}
Message was sent while issue was closed.
Description was changed from ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=sky@chromium.org BUG=673825,691965 ========== to ========== WebUI: disable optimizations (vulcanize) in debug builds When enable_vulcanize = true, HTML/CSS and JS are combined and optimized. This takes a little more build-time work, but produces faster pages for users but also munges the code a bunch. Let's disable the extra compile-time stuff and make the code cleaner for developers (i.e. in debug builds by default). R=sky@chromium.org BUG=673825,691965 Review-Url: https://codereview.chromium.org/2654723002 Cr-Commit-Position: refs/heads/master@{#451240} Committed: https://chromium.googlesource.com/chromium/src/+/6bd4c19f45d6e2bba69f9668516a... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:40001) as https://chromium.googlesource.com/chromium/src/+/6bd4c19f45d6e2bba69f9668516a... |
