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

Issue 700408 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

DevToolsProtocolTest.VirtualTimeTest content_browsertests failing on chromium.linux/Android Tests

Project Member Reported by fs...@chromium.org, Mar 10 2017

Issue description

content_browsertests failing on chromium.linux/Android Tests

Builders failed on: 
- Android Tests: 
  https://build.chromium.org/p/chromium.linux/builders/Android%20Tests

This test started being flaky today? Could you guys take a look, please?

DevToolsProtocolTest.VirtualTimeTest (run #1):
[ RUN      ] DevToolsProtocolTest.VirtualTimeTest
[WARNING:dns_config_service_posix.cc(326)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.
../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:1344: Failure
Value of: console_messages_
Expected: has 2 elements where
element #0 is equal to "before",
element #1 is equal to "done"
  Actual: { "done" }, which has 1 element
../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:1355: Failure
Value of: console_messages_
Expected: has 3 elements where
element #0 is equal to "before",
element #1 is equal to "done",
element #2 is equal to "after"
  Actual: { "done", "before", "after" }, whose element #0 doesn't match
[  FAILED  ] DevToolsProtocolTest.VirtualTimeTest, where TypeParam =  and GetParam() =  (833 ms)
[----------] 1 test from DevToolsProtocolTest (834 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (835 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] DevToolsProtocolTest.VirtualTimeTest, where TypeParam =  and GetParam() =

 1 FAILED TEST
<<ScopedMainEntryLogger
[INFO:test_support_android.cc(185)] MessagePumpForUIFactory already set, unable to override.
>>ScopedMainEntryLogger
Note: Google Test filter = DeviceSensorBrowserTest.OrientationNullTest
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from DeviceSensorBrowserTest, where TypeParam =
DevToolsProtocolTest.VirtualTimeTest (run #2):
[ RUN      ] DevToolsProtocolTest.VirtualTimeTest
[WARNING:dns_config_service_posix.cc(326)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.
../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:1344: Failure
Value of: console_messages_
Expected: has 2 elements where
element #0 is equal to "before",
element #1 is equal to "done"
  Actual: { "done" }, which has 1 element
../../content/browser/devtools/protocol/devtools_protocol_browsertest.cc:1355: Failure
Value of: console_messages_
Expected: has 3 elements where
element #0 is equal to "before",
element #1 is equal to "done",
element #2 is equal to "after"
  Actual: { "done", "before", "after" }, whose element #0 doesn't match
[  FAILED  ] DevToolsProtocolTest.VirtualTimeTest, where TypeParam =  and GetParam() =  (521 ms)
[----------] 1 test from DevToolsProtocolTest (522 ms total)

 
Cc: -alexclarke@chromium.org eseckler@chromium.org
Owner: alexclarke@chromium.org
Assigning to Alex, who's the virtual time expert :)

Comment 2 Deleted

This appears to be caused by https://codereview.chromium.org/2725633002

After reverting locally I was no longer able to reproduce the flake.
Labels: -Sheriff-Chromium
content_browsertests aren't failing anymore
Project Member

Comment 5 by sheriffbot@chromium.org, Apr 2 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Internals>Headless
Status: WontFix (was: Untriaged)
Probably no longer reproducible. Alex, feel free to reopen if there's anything left to do.

Sign in to add a comment