Revert "[battery] Add ResourceCoalitionMacTest.Busy."

This reverts commit 856342886a5ef49b6998730111e08f12d347ff72.

Reason for revert: failing on Mac10.13 Tests:
https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.13%20Tests/47610/overview

Summary:
[ RUN      ] ResourceCoalitionMacTest.Busy
../../components/power_metrics/resource_coalition_mac_unittest.mm:99: Failure
Expected: (end->cpu_instructions) > (begin->cpu_instructions), actual: 0 vs 0
Stack trace:
0   components_unittests                0x000000010b1da1e6 power_metrics::ResourceCoalitionMacTest_Busy_Test::TestBody() + 1014

../../components/power_metrics/resource_coalition_mac_unittest.mm:100: Failure
Expected: (end->cpu_cycles) > (begin->cpu_cycles), actual: 0 vs 0
Stack trace:
0   components_unittests                0x000000010b1da2d5 power_metrics::ResourceCoalitionMacTest_Busy_Test::TestBody() + 1253

[  FAILED  ] ResourceCoalitionMacTest.Busy (1113 ms)

Original change's description:
> [battery] Add ResourceCoalitionMacTest.Busy.
>
> This test verifies that CPU instructions, CPU cycles and CPU time
> reported by `GetCoalitionResourceUsage` increase after burning CPU.
> This is a basic expectations for `GetCoalitionResourceUsage` so it
> should be tested from //components/power_metrics/. In an upcoming
> CL, this will allow removing
> //chrome/browser/performance_monitor/resource_coalition_mac_unittest.mm
> without losing tests.
>
> Bug: 1293465
> Change-Id: I7232bd6b67406600b9fc89b7f7f80ad8db47c5f1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3437567
> Reviewed-by: Patrick Monette <pmonette@chromium.org>
> Commit-Queue: Francois Pierre Doray <fdoray@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#967015}

Bug: 1293465
Change-Id: Iea672af3c27d0484b75832f820f7e4a75c2cd4e2
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3440125
Auto-Submit: Olga Sharonova <olka@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Olga Sharonova <olka@google.com>
Commit-Queue: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#967154}
1 file changed
tree: ec27be1141749a1ed84c1ea65ebb8bc071f06a33
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.