|
|
DescriptionAdding components to dependencies on iOS.
Removing all targets from components so i can add one at a time and check that it works correctly.
Adding components/bookmarks.
components/bookmarks is building correctly but it needs ios/web gn files that are not written yet.
BUG=459705
Committed: https://crrev.com/dc35ba27660f5e0a26ab4e9495efdaaf829afb10
Cr-Commit-Position: refs/heads/master@{#350148}
Patch Set 1 #
Total comments: 7
Patch Set 2 : #
Total comments: 10
Patch Set 3 : Cleaning code. #
Total comments: 1
Patch Set 4 : #Patch Set 5 : #
Total comments: 3
Patch Set 6 : Fixing errors #
Total comments: 1
Patch Set 7 : #
Total comments: 1
Patch Set 8 : #Patch Set 9 : #Patch Set 10 : #Patch Set 11 : Removing duplicated block. #
Total comments: 1
Patch Set 12 : #Patch Set 13 : #Patch Set 14 : #Patch Set 15 : #Patch Set 16 : #Patch Set 17 : #Patch Set 18 : #Patch Set 19 : #Patch Set 20 : Rebasing. #Patch Set 21 : Removing conflict #Patch Set 22 : Removing conflict. #Patch Set 23 : Rebasing #
Total comments: 2
Messages
Total messages: 120 (64 generated)
sherouk@google.com changed reviewers: + dpranke@chromium.org, jochen@chromium.org, sdefresne@chromium.org
Can you review please?
https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn#newcode186 components/BUILD.gn:186: #} just delete this block now? https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn#newcode312 components/BUILD.gn:312: # These are the deps required by the code in this target. I would just delete this comment. https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn#newcode414 components/BUILD.gn:414: deps += [ "//components/rlz:unit_tests" ] You can now move this line up to after line 405 and get rid of this clause. https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn#newcode469 components/BUILD.gn:469: #} delete this block https://codereview.chromium.org/1310513006/diff/1/components/BUILD.gn#newcode483 components/BUILD.gn:483: "//components/web_cache/browser:unit_tests", merge this block up with the block on lines 324-403 ? https://codereview.chromium.org/1310513006/diff/1/components/test/run_all_uni... File components/test/run_all_unittests.cc (right): https://codereview.chromium.org/1310513006/diff/1/components/test/run_all_uni... components/test/run_all_unittests.cc:100: #if !defined(OS_IOS) why do we need this change if we don't need it in GYP?
https://codereview.chromium.org/1310513006/diff/1/components/test/run_all_uni... File components/test/run_all_unittests.cc (right): https://codereview.chromium.org/1310513006/diff/1/components/test/run_all_uni... components/test/run_all_unittests.cc:100: #if !defined(OS_IOS) On 2015/09/09 at 20:37:28, Dirk Pranke wrote: > why do we need this change if we don't need it in GYP? This was how it was done in the version of patchset #1 of https://codereview.chromium.org/1330613004. This can now be removed as https://codereview.chromium.org/1330613004 landed and instead just protected the creation of content::TestContentClientInitializer() instance.
Patchset #2 (id:20001) has been deleted
Patchset #3 (id:60001) has been deleted
Patchset #2 (id:40001) has been deleted
Patchset #3 (id:100001) has been deleted
Patchset #2 (id:80001) has been deleted
Patchset #2 (id:120001) has been deleted
Patchset #2 (id:140001) has been deleted
Patchset #2 (id:160001) has been deleted
Patchset #2 (id:90008) has been deleted
Patchset #2 (id:190001) has been deleted
Patchset #2 (id:150008) has been deleted
Changes done.
https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:184: if (!enable_configuration_policy && !is_ios) { it seems like many of these changes are unnecessary. For example, enable_configuration_policy == !is_ios Maybe you should either move these inside the big (!is_ios) block, above, or add components/policy back to the unconditional list? https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:198: if (!is_ios && (!is_chromeos || !enable_extensions)) { same thought https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:202: if (!enable_plugins && !is_ios) { same thought. https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:288: if (toolkit_views && !is_ios) { isn't toolkit_views false on ios? https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:473: if (enable_configuration_policy && !is_ios) { same comment. https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:480: if (toolkit_views && !is_ios) { same comment. https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:604: if ((enable_basic_printing || enable_print_preview) && !is_ios) { should these flags just be disabled on ios?
Patchset #3 (id:230001) has been deleted
Patchset #3 (id:250001) has been deleted
Patchset #3 (id:270001) has been deleted
Patchset #3 (id:250002) has been deleted
Changes done. can you review it? https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:184: if (!enable_configuration_policy && !is_ios) { On 2015/09/10 22:19:43, Dirk Pranke wrote: > it seems like many of these changes are unnecessary. > > For example, enable_configuration_policy == !is_ios > > Maybe you should either move these inside the big (!is_ios) block, above, or add > components/policy back to the unconditional list? Done. https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:288: if (toolkit_views && !is_ios) { On 2015/09/10 22:19:43, Dirk Pranke wrote: > isn't toolkit_views false on ios? yes. https://codereview.chromium.org/1310513006/diff/220001/components/BUILD.gn#ne... components/BUILD.gn:604: if ((enable_basic_printing || enable_print_preview) && !is_ios) { On 2015/09/10 22:19:43, Dirk Pranke wrote: > should these flags just be disabled on ios? Done.
lgtm, thanks! https://codereview.chromium.org/1310513006/diff/300001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/300001/components/BUILD.gn#ne... components/BUILD.gn:501: if (!is_ios) { I wouldn't expect this change to be necessary?
lgtm
On 2015/09/11 17:03:59, Dirk Pranke wrote: > lgtm, thanks! > > https://codereview.chromium.org/1310513006/diff/300001/components/BUILD.gn > File components/BUILD.gn (right): > > https://codereview.chromium.org/1310513006/diff/300001/components/BUILD.gn#ne... > components/BUILD.gn:501: if (!is_ios) { > I wouldn't expect this change to be necessary? Yeah it's building without, Thanks!
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps320001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/320001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/320001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps340001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/340001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/340001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
https://codereview.chromium.org/1310513006/diff/340001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/340001/components/BUILD.gn#ne... components/BUILD.gn:37: deps = [ needs to be "deps += [" https://codereview.chromium.org/1310513006/diff/340001/components/BUILD.gn#ne... components/BUILD.gn:320: deps = [ needs to be "deps += [" https://codereview.chromium.org/1310513006/diff/340001/components/favicon/cor... File components/favicon/core/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/340001/components/favicon/cor... components/favicon/core/BUILD.gn:38: "fallback_icon_client.h", can you put those behind OS!="ios" condition in gyp file too?
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps360001 (title: "Fixing errors")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/360001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/360001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
https://codereview.chromium.org/1310513006/diff/360001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/360001/components/BUILD.gn#ne... components/BUILD.gn:453: sources = [ this should be "sources += ["
Patchset #7 (id:380001) has been deleted
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps400001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/400001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/400001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
https://codereview.chromium.org/1310513006/diff/400001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/400001/components/BUILD.gn#ne... components/BUILD.gn:451: repack("components_tests_pak") { This is incorrect it should be: repack("components_tests_pak") { sources = [ "$root_gen_dir/components/components_resources.pak", "$root_gen_dir/components/strings/components_strings_en-US.pak", ] output = "$root_out_dir/components_tests_resources.pak" if (!is_ios) { deps = [ "//components/resources", "//components/strings", ] } } Though I'm surprised that //components/resources and //components/strings are not currently building as-is on iOS.
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps420001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/420001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/420001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) android_chromium_gn_compile_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) win8_chromium_ng on tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_ng/...)
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps460001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/460001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/460001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) android_chromium_gn_compile_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps480001 (title: "removing duplicate block")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/480001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/480001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) android_chromium_gn_compile_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
I think this CL need some more work before we can send it to the CQ. Please ask for another review once you've fixed the errors (you should be able to send the CL to the try bots with "git cl try" to validate that it is not breaking other platforms). dpranke: I'm surprise that the following snippet does not warn about nested targets (are nested targets even allowed with gn). Currently, it warns about incorrect deps (i.e. a target not marked as test_only dependending on a test_only target). test("components_unittests") { sources = [ "..." ] deps = [ "..." ] repack("components_test_pack") { sources += [ "///" ] deps += [ "///" ] } } https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn#ne... components/BUILD.gn:451: repack("components_tests_pak") { repack("components_tests_pak") used to be at the top-level of the file (i.e. not nested into any other {} block) but your CL move it inside the block of the test("components_unittests") target. This is incorrect. This target cannot be nested into the other target. This is what is causing all the errors (as it pulls the deps/sources from the parent target and mix with its own). Move it back to the top-level. Please also check that you have fixed all such other issues. I don't think there should be that much moving of code around in that file just for putting some deps/sources behind "if (!is_ios)" conditions.
Patchset #13 (id:520001) has been deleted
On 2015/09/15 13:14:50, sdefresne wrote: > I think this CL need some more work before we can send it to the CQ. Please ask > for another review once you've fixed the errors (you should be able to send the > CL to the try bots with "git cl try" to validate that it is not breaking other > platforms). > > dpranke: I'm surprise that the following snippet does not warn about nested > targets (are nested targets even allowed with gn). Currently, it warns about > incorrect deps (i.e. a target not marked as test_only dependending on a > test_only target). > > test("components_unittests") { > sources = [ "..." ] > deps = [ "..." ] > repack("components_test_pack") { > sources += [ "///" ] > deps += [ "///" ] > } > } > > https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn > File components/BUILD.gn (right): > > https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn#ne... > components/BUILD.gn:451: repack("components_tests_pak") { > repack("components_tests_pak") used to be at the top-level of the file (i.e. not > nested into any other {} block) but your CL move it inside the block of the > test("components_unittests") target. > > This is incorrect. This target cannot be nested into the other target. This is > what is causing all the errors (as it pulls the deps/sources from the parent > target and mix with its own). Move it back to the top-level. > > Please also check that you have fixed all such other issues. I don't think there > should be that much moving of code around in that file just for putting some > deps/sources behind "if (!is_ios)" conditions. Now should it be done?
On 2015/09/15 at 14:17:26, sherouk wrote: > On 2015/09/15 13:14:50, sdefresne wrote: > > I think this CL need some more work before we can send it to the CQ. Please ask > > for another review once you've fixed the errors (you should be able to send the > > CL to the try bots with "git cl try" to validate that it is not breaking other > > platforms). > > > > dpranke: I'm surprise that the following snippet does not warn about nested > > targets (are nested targets even allowed with gn). Currently, it warns about > > incorrect deps (i.e. a target not marked as test_only dependending on a > > test_only target). > > > > test("components_unittests") { > > sources = [ "..." ] > > deps = [ "..." ] > > repack("components_test_pack") { > > sources += [ "///" ] > > deps += [ "///" ] > > } > > } > > > > https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn > > File components/BUILD.gn (right): > > > > https://codereview.chromium.org/1310513006/diff/480001/components/BUILD.gn#ne... > > components/BUILD.gn:451: repack("components_tests_pak") { > > repack("components_tests_pak") used to be at the top-level of the file (i.e. not > > nested into any other {} block) but your CL move it inside the block of the > > test("components_unittests") target. > > > > This is incorrect. This target cannot be nested into the other target. This is > > what is causing all the errors (as it pulls the deps/sources from the parent > > target and mix with its own). Move it back to the top-level. > > > > Please also check that you have fixed all such other issues. I don't think there > > should be that much moving of code around in that file just for putting some > > deps/sources behind "if (!is_ios)" conditions. > > Now should it be done? Can you send the CL to the try bots using "git cl try"?
On 2015/09/15 13:14:50, sdefresne wrote: > dpranke: I'm surprise that the following snippet does not warn about nested > targets (are nested targets even allowed with gn). Currently, it warns about > incorrect deps (i.e. a target not marked as test_only dependending on a > test_only target). > That should probably get filed as a bug against GN.
lgtm assuming the try jobs pass.
Patchset #15 (id:580001) has been deleted
Patchset #16 (id:620001) has been deleted
Patchset #16 (id:640001) has been deleted
Patchset #17 (id:680001) has been deleted
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from jochen@chromium.org, dpranke@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps740001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/740001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/740001
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...)
Looks like it is again failing with patch failure. I guess you'll have to again rebase it :-/ -- Sylvain On Fri, 18 Sep 2015 at 14:15 commit-bot@chromium.org via codereview.chromium.org <reply@chromiumcodereview-hr.appspotmail.com> wrote: > 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... > ) > > https://codereview.chromium.org/1310513006/ > To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps760001 (title: "Rebasing.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/760001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/760001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps780001 (title: "Removing conflict")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/780001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/780001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: android_chromium_gn_compile_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) android_chromium_gn_compile_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_gn_dbg on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps800001 (title: "Removing conflict.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/800001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/800001
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...)
Patchset #23 (id:820001) has been deleted
Patchset #23 (id:840001) has been deleted
sherouk@google.com changed reviewers: + brettw@chromium.org - dpranke@chromium.org, jochen@chromium.org, sdefresne@chromium.org
Can you review please?
sherouk@google.com changed reviewers: + dpranke@chromium.org, jochen@chromium.org, sdefresne@chromium.org
On 2015/09/18 at 13:34:12, sherouk wrote: > Can you review please? brettw: I think we need your OWNERS approval for the changes to //base/BUILD.gn. Thank you.
lgtm
The CQ bit was checked by sherouk@google.com
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org, jochen@chromium.org, brettw@chromium.org Link to the patchset: https://codereview.chromium.org/1310513006/#ps860001 (title: "Rebasing")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/860001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/860001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: win_chromium_rel_ng on tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by sherouk@google.com
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1310513006/860001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1310513006/860001
Message was sent while issue was closed.
Committed patchset #23 (id:860001)
Message was sent while issue was closed.
Patchset 23 (id:??) landed as https://crrev.com/dc35ba27660f5e0a26ab4e9495efdaaf829afb10 Cr-Commit-Position: refs/heads/master@{#350148}
Message was sent while issue was closed.
blundell@chromium.org changed reviewers: + blundell@chromium.org
Message was sent while issue was closed.
https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn File components/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... components/BUILD.gn:390: "//components/variations:unit_tests", It looks like this CL didn't move over //components/variations/service:unit_tests. Not sure if there are any others missing.
Message was sent while issue was closed.
On 2015/10/15 at 08:41:39, blundell wrote: > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn > File components/BUILD.gn (right): > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... > components/BUILD.gn:390: "//components/variations:unit_tests", > It looks like this CL didn't move over //components/variations/service:unit_tests. Not sure if there are any others missing. Only components that were know to build successfully on iOS have been added. Other may build and could be enabled, they probably just have not been tested yet.
Message was sent while issue was closed.
On 2015/10/19 06:16:41, sdefresne (OOO till 19th Oct.) wrote: > On 2015/10/15 at 08:41:39, blundell wrote: > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn > > File components/BUILD.gn (right): > > > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... > > components/BUILD.gn:390: "//components/variations:unit_tests", > > It looks like this CL didn't move over > //components/variations/service:unit_tests. Not sure if there are any others > missing. > > Only components that were know to build successfully on iOS have been added. > Other may build and could be enabled, they probably just have not been tested > yet. The problem here is that //components/variations/service:unit_tests disappeared entirely instead of being moved to the !iOS section.
Message was sent while issue was closed.
On 2015/10/19 at 06:19:54, blundell wrote: > On 2015/10/19 06:16:41, sdefresne (OOO till 19th Oct.) wrote: > > On 2015/10/15 at 08:41:39, blundell wrote: > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn > > > File components/BUILD.gn (right): > > > > > > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... > > > components/BUILD.gn:390: "//components/variations:unit_tests", > > > It looks like this CL didn't move over > > //components/variations/service:unit_tests. Not sure if there are any others > > missing. > > > > Only components that were know to build successfully on iOS have been added. > > Other may build and could be enabled, they probably just have not been tested > > yet. > > The problem here is that //components/variations/service:unit_tests disappeared entirely instead of being moved to the !iOS section. Oh, didn't catch this. I'll fix it later today. Thank you.
Message was sent while issue was closed.
On 2015/10/19 14:56:24, sdefresne (OOO till 19th Oct.) wrote: > On 2015/10/19 at 06:19:54, blundell wrote: > > On 2015/10/19 06:16:41, sdefresne (OOO till 19th Oct.) wrote: > > > On 2015/10/15 at 08:41:39, blundell wrote: > > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn > > > > File components/BUILD.gn (right): > > > > > > > > > > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... > > > > components/BUILD.gn:390: "//components/variations:unit_tests", > > > > It looks like this CL didn't move over > > > //components/variations/service:unit_tests. Not sure if there are any others > > > missing. > > > > > > Only components that were know to build successfully on iOS have been added. > > > Other may build and could be enabled, they probably just have not been > tested > > > yet. > > > > The problem here is that //components/variations/service:unit_tests > disappeared entirely instead of being moved to the !iOS section. > > Oh, didn't catch this. I'll fix it later today. Thank you. Thanks!
Message was sent while issue was closed.
I think it's being fixed already by this CL: https://codereview.chromium.org/1404583004/ On Mon, Oct 19, 2015 at 10:57 AM, <blundell@chromium.org> wrote: > On 2015/10/19 14:56:24, sdefresne (OOO till 19th Oct.) wrote: > >> On 2015/10/19 at 06:19:54, blundell wrote: >> > On 2015/10/19 06:16:41, sdefresne (OOO till 19th Oct.) wrote: >> > > On 2015/10/15 at 08:41:39, blundell wrote: >> > > > >> > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn > >> > > > File components/BUILD.gn (right): >> > > > >> > > > >> > > >> > > > https://codereview.chromium.org/1310513006/diff/860001/components/BUILD.gn#ne... > >> > > > components/BUILD.gn:390: "//components/variations:unit_tests", >> > > > It looks like this CL didn't move over >> > > //components/variations/service:unit_tests. Not sure if there are any >> > others > >> > > missing. >> > > >> > > Only components that were know to build successfully on iOS have been >> > added. > >> > > Other may build and could be enabled, they probably just have not been >> tested >> > > yet. >> > >> > The problem here is that //components/variations/service:unit_tests >> disappeared entirely instead of being moved to the !iOS section. >> > > Oh, didn't catch this. I'll fix it later today. Thank you. >> > > Thanks! > > https://codereview.chromium.org/1310513006/ > 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.
https://codereview.chromium.org/1310513006/diff/860001/components/favicon/cor... File components/favicon/core/BUILD.gn (right): https://codereview.chromium.org/1310513006/diff/860001/components/favicon/cor... components/favicon/core/BUILD.gn:36: if (!is_ios) { FYI, these files should just be moved to //components/favicon/content. I'll do that when I have some free cycles. In general it merits a second look if you're inserting a !is_ios block in a //components/foo/core/BUILD.gn file, since the purpose of //components/foo/core is precisely to share code between iOS and other platforms. |