[FLEDGE] Make Reporter outlive Auction.

Previously, the InterestGroupAuction owned the
InterestGroupAuctionReporter, and ran it to completion. This CL
makes to so the InterestGroupAuctionReporter is instead passed to
the AdAuctionServiceImpl, which starts the Report, then destroys
the Auction, and then runs the Reporter to completion before passing
the auction result to the caller.

This is an intermediary step towards reporting an auction result
before running the report.

This CL adds a number of warts to try and keep it simple:

* Aborting doesn't work while the Reporter is running. This will
  become (basically) moot once the Reporter runs after auction
  completion. We already only report on swap, which helps as well.

* We perform database updates updates on auction completion (Before
  reporting starts). We should do these only when a report is swapped
  in, either having the Reporter do it, or having callback passed
  to the reporter do it.

* We don't histogram the result of the reporter, and we only record
  auction result before the Reporter starts running, so if the auction
  phase completes, but the auction is cancelled before the Reporting
  phase completes, we log it as a complete auction. We should add
  logging for this.

This CL adds TODOs for the latter two of those, and the former, as
mentioned, will become moot once things are fully hooked up.


Bug: 1394777
Change-Id: I9cab9e45f3f51176aa83566dd3e6800851dc130a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4067680
Reviewed-by: Russ Hamilton <behamilton@google.com>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1081971}
9 files changed
tree: f5c3e310f3111b869ebc643359c8185c1d0bb920
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.