New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 752613 link

Starred by 1 user
Status: Assigned
Owner:
primiano@chromium.org
Cc:
ssid@chromium.org
█ hjd@chromium.org
█ picksi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android
Pri: 2
Type: Bug
Hotlist-MemoryInfra



Sign in to add a comment

SingleProcessMemoryTracingTest.QueuedDumps test failure

Project Member Reported by joedow@chromium.org, Aug 4 2017 
This failure was seen on the Android Tests (dbg) buildbot.  I did not see any relevant / related CLs prior to the failure and it only occurred once.  Seems like it is related to device setup.

Test case excerpt:
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  Note: Google Test filter = SingleProcessMemoryTracingTest.QueuedDumps
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [==========] Running 1 test from 1 test case.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [----------] Global test environment set-up.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [----------] 1 test from SingleProcessMemoryTracingTest, where TypeParam = 
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [ RUN      ] SingleProcessMemoryTracingTest.QueuedDumps
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [WARNING:dns_config_service_posix.cc(328)] Failed to read DnsConfig.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [ERROR:devtools_http_handler.cc(229)] Cannot start http server for devtools. Stop devtools.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [WARNING:graphics_memory_dump_provider_android.cc(66)] Could not connect to the memtrack_helper daemon. Please build memtrack_helper, adb push to the device and run it before starting the trace to get graphics memory data.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [WARNING:graphics_memory_dump_provider_android.cc(66)] Could not connect to the memtrack_helper daemon. Please build memtrack_helper, adb push to the device and run it before starting the trace to get graphics memory data.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  unknown file: Failure
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  Unexpected mock function call - returning directly.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)      Function call: OnMemoryDumpDone(1, true)
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  Google Mock tried the following 3 expectations, but none matched:
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  ../../content/browser/tracing/memory_tracing_browsertest.cc:260: tried expectation #0: EXPECT_CALL(*this, OnMemoryDumpDone(0, true ))...
I  410.840s run_tests_on_device(097f1a0b0189b2c0)    Expected arg #0: is equal to 0
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: 1
I  410.840s run_tests_on_device(097f1a0b0189b2c0)           Expected: to be called once
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: called once - saturated and active
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  ../../content/browser/tracing/memory_tracing_browsertest.cc:267: tried expectation #1: EXPECT_CALL(*this, OnMemoryDumpDone(1, false ))...
I  410.840s run_tests_on_device(097f1a0b0189b2c0)    Expected arg #1: is equal to false
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: true
I  410.840s run_tests_on_device(097f1a0b0189b2c0)           Expected: to be called once
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: never called - unsatisfied and active
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  ../../content/browser/tracing/memory_tracing_browsertest.cc:272: tried expectation #2: EXPECT_CALL(*this, OnMemoryDumpDone(2, true ))...
I  410.840s run_tests_on_device(097f1a0b0189b2c0)    Expected arg #0: is equal to 2
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: 1
I  410.840s run_tests_on_device(097f1a0b0189b2c0)           Expected: to be called once
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: never called - unsatisfied and active
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [WARNING:graphics_memory_dump_provider_android.cc(66)] Could not connect to the memtrack_helper daemon. Please build memtrack_helper, adb push to the device and run it before starting the trace to get graphics memory data.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  ../../content/browser/tracing/memory_tracing_browsertest.cc:256: Failure
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  Mock function called more times than expected - returning default value.
I  410.840s run_tests_on_device(097f1a0b0189b2c0)      Function call: OnMemoryDump(@0x826fcd38 4-byte object <01-00 00-00>, 0x7d363cb8)
I  410.840s run_tests_on_device(097f1a0b0189b2c0)            Returns: false
I  410.840s run_tests_on_device(097f1a0b0189b2c0)           Expected: to be called 5 times
I  410.840s run_tests_on_device(097f1a0b0189b2c0)             Actual: called 6 times - over-saturated and active
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  [ERROR:render_process_impl.cc(176)] WebFrame LEAKED 1 TIMES
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  ../../content/browser/tracing/memory_tracing_browsertest.cc:267: Failure
I  410.840s run_tests_on_device(097f1a0b0189b2c0)  Actual function call count doesn't match EXPECT_CALL(*this, OnMemoryDumpDone(1, false ))...
I  410.841s run_tests_on_device(097f1a0b0189b2c0)           Expected: to be called once
I  410.841s run_tests_on_device(097f1a0b0189b2c0)             Actual: never called - unsatisfied and active
I  410.841s run_tests_on_device(097f1a0b0189b2c0)  [  FAILED  ] SingleProcessMemoryTracingTest.QueuedDumps, where TypeParam =  and GetParam() =  (945 ms)
I  410.841s run_tests_on_device(097f1a0b0189b2c0)  [----------] 1 test from SingleProcessMemoryTracingTest (946 ms total)

Comment 1 by joedow@chromium.org, Aug 7 2017

Labels: Sheriff-Chromium OS-Linux

Comment 2 by shimazu@chromium.org, Aug 8 2017

Components: Internals>Instrumentation>Memory
Owner: primiano@chromium.org
Status: Available (was: Untriaged)
The test seems very flaky. I've sent a patch to disable the test. https://crrev.com/c/604630

Flakiness dashboard:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=content_browsertests&tests=SingleProcessMemoryTracingTest

+primiano since issue 720352 might be relevant to this issue. 
If it's wrong, feel free to reassign to another person.
Project Member

Comment 3 by bugdroid1@chromium.org, Aug 8 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9652ffa58183a00262d59b87d88d1eda8226c26b

commit 9652ffa58183a00262d59b87d88d1eda8226c26b
Author: Makoto Shimazu <shimazu@chromium.org>
Date: Tue Aug 08 03:25:35 2017

Disabled flaky test: SingleProcessMemoryTracingTest.QueuedDumps

According to the flakiness dashboard, the test is sometimes failing.

TBR=primiano@chromium.org

Bug: 752613
Change-Id: I57a4028d259a33f7b228a2e7f9dad6da78d06939
Reviewed-on: https://chromium-review.googlesource.com/604630
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#492518}
[modify] https://crrev.com/9652ffa58183a00262d59b87d88d1eda8226c26b/content/browser/tracing/memory_tracing_browsertest.cc

Comment 4 by shimazu@chromium.org, Aug 8 2017

Labels: -Sheriff-Chromium

Comment 5 by primiano@chromium.org, Aug 8 2017

Cc: ssid@chromium.org hjd@chromium.org
I knew this would come back :(
Not high prio, but if any of you has spare cycles at some point we should check what's the new brekage.

Comment 6 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Available)
►

Sign in to add a comment