Index: base/trace_event/memory_dump_manager_unittest.cc |
diff --git a/base/trace_event/memory_dump_manager_unittest.cc b/base/trace_event/memory_dump_manager_unittest.cc |
index 26a826b0b00ded6598055cb3fe52f60b18399d0b..903321c777b30e5545f92ebe2ab57ff13a6acd0c 100644 |
--- a/base/trace_event/memory_dump_manager_unittest.cc |
+++ b/base/trace_event/memory_dump_manager_unittest.cc |
@@ -891,17 +891,17 @@ TEST_F(MemoryDumpManagerTest, TraceConfigExpectationsWhenIsCoordinator) { |
InitializeMemoryDumpManagerForInProcessTesting(true /* is_coordinator */); |
// Enabling memory-infra with the legacy TraceConfig (category filter) in |
- // a coordinator process should enable periodic dumps. |
+ // a coordinator process should not enable periodic dumps. |
EnableTracingWithLegacyCategories(MemoryDumpManager::kTraceCategory); |
- EXPECT_TRUE(IsPeriodicDumpingEnabled()); |
+ EXPECT_FALSE(IsPeriodicDumpingEnabled()); |
DisableTracing(); |
// Enabling memory-infra with the new (JSON) TraceConfig in a coordinator |
- // process without specifying any "memory_dump_config" section should enable |
+ // process while specifying a "memory_dump_config" section should enable |
// periodic dumps. This is to preserve the behavior chrome://tracing UI, that |
- // is: ticking memory-infra should dump periodically with the default config. |
+ // is: ticking memory-infra should dump periodically with an explicit config. |
EnableTracingWithTraceConfig( |
- TraceConfigMemoryTestUtil::GetTraceConfig_NoTriggers()); |
+ TraceConfigMemoryTestUtil::GetTraceConfig_PeriodicTriggers(100, 5)); |
EXPECT_TRUE(IsPeriodicDumpingEnabled()); |
DisableTracing(); |