Issue metadata
Sign in to add a comment
|
Allocator/StatisticsRecorderTest.NotInitialized/[0|1] started failing under Fuchsia FYI |
||||||||||||||||||||||
Issue descriptionTests fail with: [ RUN ] Allocator/StatisticsRecorderTest.NotInitialized/0 ../../base/metrics/statistics_recorder_unittest.cc:127: Failure Value of: StatisticsRecorder::IsActive() Actual: true Expected: false [ FAILED ] Allocator/StatisticsRecorderTest.NotInitialized/0, where GetParam() = false (9 ms) suggesting that some global state from an earlier test is not being properly torn down.
,
Jan 3 2018
,
Jan 3 2018
This started with the landing of https://chromium-review.googlesource.com/830997, which changed the way that the "global" StatisticsRecorder instance is managed. By inspection, it appears that the tests will fail if anything calls StatisticsRecorder::Initialize() in the test process - then StatisticsRecorder::IsActive() will be true even after the test has uninitialized the test instance of the StatisticsRecorder, because UninitializeForTesting() was removed, so the global instance, if any, is not correctly cleaned-up before the tests run. See https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia%20ARM64/3848 for an example of a failed run. I'll revert this for now.
,
Jan 3 2018
Reverted by https://chromium-review.googlesource.com/c/chromium/src/+/848273. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by asvitk...@chromium.org
, Jan 3 2018