|
|
Created:
5 years, 10 months ago by Deprecated (see juliatuttle) Modified:
5 years, 10 months ago CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDomain Reliability: Default to enabled
BUG=
Committed: https://crrev.com/d173a2ebe529d43147c87dafb4d8e2e988728960
Cr-Commit-Position: refs/heads/master@{#316276}
Patch Set 1 #Patch Set 2 : Fix BrowsingDataRemoverTest failures #
Total comments: 4
Patch Set 3 : Make requested changes #
Total comments: 4
Patch Set 4 : Make requested changes #Patch Set 5 : rebase #Patch Set 6 : rebase onto https://codereview.chromium.org/920923002/ to see if trybots pass #Patch Set 7 : rebase back onto master now that that's landed #
Messages
Total messages: 40 (18 generated)
ttuttle@chromium.org changed reviewers: + davidben@chromium.org
ttuttle@chromium.org changed required reviewers: + davidben@chromium.org
PTAL, davidben.
https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... File chrome/browser/browsing_data/browsing_data_remover_unittest.cc (right): https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:855: ClearDomainReliabilityTester clear_domain_reliability_tester_; I don't think we ever interleave private/protected/private like that. If the ordering matters, how about leave it private and add an accessor? Or stuff it in a scoped_ptr so you can initialize it later. https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:1784: ClearDomainReliabilityTester& tester = clear_domain_reliability_tester_; Nit: do we ever use non-const references? Pointer maybe.
PTAL, davidben. https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... File chrome/browser/browsing_data/browsing_data_remover_unittest.cc (right): https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:855: ClearDomainReliabilityTester clear_domain_reliability_tester_; On 2015/02/03 19:09:23, David Benjamin wrote: > I don't think we ever interleave private/protected/private like that. If the > ordering matters, how about leave it private and add an accessor? Or stuff it in > a scoped_ptr so you can initialize it later. Done. https://codereview.chromium.org/895683002/diff/20001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:1784: ClearDomainReliabilityTester& tester = clear_domain_reliability_tester_; On 2015/02/03 19:09:23, David Benjamin wrote: > Nit: do we ever use non-const references? Pointer maybe. Obsolete; I made it a const reference instead.
lgtm
The CQ bit was checked by ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/40001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
bauerb@chromium.org changed reviewers: + bauerb@chromium.org
LGTM w/ nits: https://codereview.chromium.org/895683002/diff/40001/chrome/browser/browsing_... File chrome/browser/browsing_data/browsing_data_remover_unittest.cc (right): https://codereview.chromium.org/895683002/diff/40001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:1837: // TODO(ttuttle): This isn't actually testing the no-monitor case, since So, what's the TODO here? https://codereview.chromium.org/895683002/diff/40001/chrome/browser/domain_re... File chrome/browser/domain_reliability/service_factory.cc (right): https://codereview.chromium.org/895683002/diff/40001/chrome/browser/domain_re... chrome/browser/domain_reliability/service_factory.cc:25: const char* kFieldTrialName = "DomRel-Enable"; const char kFieldTrialName[] = "..." etc.?
New patchsets have been uploaded after l-g-t-m from davidben@chromium.org,bauerb@chromium.org
Thanks! https://codereview.chromium.org/895683002/diff/40001/chrome/browser/browsing_... File chrome/browser/browsing_data/browsing_data_remover_unittest.cc (right): https://codereview.chromium.org/895683002/diff/40001/chrome/browser/browsing_... chrome/browser/browsing_data/browsing_data_remover_unittest.cc:1837: // TODO(ttuttle): This isn't actually testing the no-monitor case, since On 2015/02/09 18:19:04, Bernhard Bauer wrote: > So, what's the TODO here? Done. https://codereview.chromium.org/895683002/diff/40001/chrome/browser/domain_re... File chrome/browser/domain_reliability/service_factory.cc (right): https://codereview.chromium.org/895683002/diff/40001/chrome/browser/domain_re... chrome/browser/domain_reliability/service_factory.cc:25: const char* kFieldTrialName = "DomRel-Enable"; On 2015/02/09 18:19:05, Bernhard Bauer wrote: > const char kFieldTrialName[] = "..." etc.? Done.
The CQ bit was checked by ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_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 ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_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 ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_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 ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_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 ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_chromeos_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 ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/100001
The CQ bit was checked by ttuttle@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/895683002/120001
Message was sent while issue was closed.
Committed patchset #7 (id:120001)
Message was sent while issue was closed.
Patchset 7 (id:??) landed as https://crrev.com/d173a2ebe529d43147c87dafb4d8e2e988728960 Cr-Commit-Position: refs/heads/master@{#316276} |