I didn't look into why. Does this have to use EXPECT_DOUBLE_EQ or can be EXPECT_NEAR?

[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from ProcessDataCollectorTest
[ RUN      ] ProcessDataCollectorTest.ExpAveragingMultistep
../../chrome/browser/chromeos/power/process_data_collector_unittest.cc:488: Failure
Expected equality of these values:
  process.power_usage_fraction
    Which is: 0.23255813953488358
  timestep_info.expected_averages.at(pid)
    Which is: 0.23255813953488372
For PID 6 the expected and calculated average CPU usages didn't match.
Stack trace:
#0 0x563d2eef534c testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop()
#1 0x563d2eef4d39 testing::internal::AssertHelper::operator=()
#2 0x563d2ed259a3 chromeos::ProcessDataCollectorTest::RunTest()
#3 0x563d2ed286ea chromeos::ProcessDataCollectorTest_ExpAveragingMultistep_Test::TestBody()

[  FAILED  ] ProcessDataCollectorTest.ExpAveragingMultistep (42 ms)