Reland "[floc] Remove the EventTrigger field in the FlocIdComputed event"
This is a reland of e16309d9 The diff: disable floc event logging for 2 user-event related sync test suite: SingleClientUserEventsSyncTest & TwoClientUserEventsSyncTest. Add a wait-for-floc-network-response call at the end of ProfileSyncServiceHarness::AwaitSyncSetupCompletion, so that the user event logging behavior now becomes more deterministic and new flaky test won't be added by accident. Original change's description: > [floc] Remove the EventTrigger field in the FlocIdComputed event > > Why: That field is never used & not useful for the server side analysis. > > This CL also removes a workaround that disables the initial floc > loggings when permission disallows > (in FlocIdProviderImpl::LogFlocComputedEvent). We had this workaround > because otherwise the logging would mess up with the user event > expectations in SingleClientUserEventsSyncTest, but that workaround is > not ideal. This CL fixes it by disabling kFlocIdComputedEventLogging for > the test suite, and adds a new test for the enabled case. The impact > of this fix is it will cause additional events to be logged. > > > Bug: 1148358 > Change-Id: I70cef531b89b434b5572b419acc8dd2412888498 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572733 > Reviewed-by: Josh Karlin <jkarlin@chromium.org> > Reviewed-by: Marc Treib <treib@chromium.org> > Commit-Queue: Yao Xiao <yaoxia@chromium.org> > Cr-Commit-Position: refs/heads/master@{#835468} Bug: 1148358 Change-Id: I12c8230ee5edc3de7337e9daa8c07143ae83949d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2584607 Commit-Queue: Yao Xiao <yaoxia@chromium.org> Reviewed-by:Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#836637}
Showing
This diff is collapsed.
Please register or sign in to comment