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

Issue 616388 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

WebRtcDataChannelTest.DataChannelGC flaky

Project Member Reported by guidou@chromium.org, Jun 1 2016

Issue description

See https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%28dbg%29%281%29/builds/49227

Not clear why it became flaky, but it also became flaky on Android ASAN a few weeks ago.

In the meantime, disabling the test.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 1 2016

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

commit 4fd18283e9b646ecb0368c92d8fd5c5fcedb7fc4
Author: guidou <guidou@chromium.org>
Date: Wed Jun 01 09:34:53 2016

Disable WebRTC DataChannel GC test on Windows.

It has become flaky on the Win7 Tests bot.
Root cause for the flakiness is not clear yet.

BUG= 616388 
TBR=phoglung@chromium.org

Review-Url: https://codereview.chromium.org/2027963002
Cr-Commit-Position: refs/heads/master@{#397092}

[modify] https://crrev.com/4fd18283e9b646ecb0368c92d8fd5c5fcedb7fc4/content/browser/media/webrtc/webrtc_datachannel_browsertest.cc

Components: Blink>WebRTC
Labels: M-53 OS-Windows
Although tests aren't tied to releases, I'm adding the M53 label so this doesn't fall into a black hole. :)
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 7 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: MissingTests
guidou@ are you the right owner for this and if so, when you can land a fix? Please update the milestone accordingly.

Comment 6 by hbos@chromium.org, Sep 28 2016

E.g.

I  221.246s run_tests_on_device(ZX1G22X9R4)  [ RUN      ] WebRtcDataChannelTest.DataChannelGC
I  221.246s run_tests_on_device(ZX1G22X9R4)  [WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
I  221.246s run_tests_on_device(ZX1G22X9R4)  [ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.
I  221.246s run_tests_on_device(ZX1G22X9R4)  [WARNING:simple_synchronous_entry.cc(1054)] Could not open platform files for entry.
I  221.246s run_tests_on_device(ZX1G22X9R4)  [ERROR:shell_android.cc(72)] Not implemented reached in void content::Shell::PlatformSetTitle(const string16&): RTCDataChannel Content Browser Test
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(53)] "creating offer", source: http://127.0.0.1:37398/media/datachannel_test.html (53)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(57)] "creating answer", source: http://127.0.0.1:37398/media/datachannel_test.html (57)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(26)] "dc1/open event", source: http://127.0.0.1:37398/media/datachannel_test.html (26)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(45)] "pc2/datachannel event", source: http://127.0.0.1:37398/media/datachannel_test.html (45)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #0", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(48)] "dc2/message event: "probe #0"", source: http://127.0.0.1:37398/media/datachannel_test.html (48)
I  221.246s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #1", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(48)] "dc2/message event: "probe #1"", source: http://127.0.0.1:37398/media/datachannel_test.html (48)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #2", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(48)] "dc2/message event: "probe #2"", source: http://127.0.0.1:37398/media/datachannel_test.html (48)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #3", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #4", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(48)] "dc2/message event: "probe #3"", source: http://127.0.0.1:37398/media/datachannel_test.html (48)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #5", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(48)] "dc2/message event: "probe #4"", source: http://127.0.0.1:37398/media/datachannel_test.html (48)
I  221.247s run_tests_on_device(ZX1G22X9R4)  [INFO:CONSOLE(29)] "dc1/time: probe #6", source: http://127.0.0.1:37398/media/datachannel_test.html (29)
I  221.247s run_tests_on_device(ZX1G22X9R4)  referenceTable head length=54 1
I  221.247s run_tests_on_device(ZX1G22X9R4)  From javascript: Error: expected '6', got '5'.
I  221.247s run_tests_on_device(ZX1G22X9R4)      at failTest (http://127.0.0.1:37398/media/webrtc_test_utilities.js:40:15)
I  221.247s run_tests_on_device(ZX1G22X9R4)      at assertEquals (http://127.0.0.1:37398/media/webrtc_test_utilities.js:250:5)
I  221.247s run_tests_on_device(ZX1G22X9R4)      at http://127.0.0.1:37398/media/datachannel_test.html:32:9
I  221.247s run_tests_on_device(ZX1G22X9R4)  When executing 'testDataChannelGC();'
I  221.247s run_tests_on_device(ZX1G22X9R4)  ../../content/browser/webrtc/webrtc_content_browsertest_base.cc:90: Failure
I  221.247s run_tests_on_device(ZX1G22X9R4)  Failed
I  221.247s run_tests_on_device(ZX1G22X9R4)  [  FAILED  ] WebRtcDataChannelTest.DataChannelGC, where TypeParam =  and GetParam() =  (951 ms)

Comment 7 by guidou@chromium.org, Nov 18 2016

Status: WontFix (was: Assigned)
It looks like flakiness has stopped. Probably due to fixes in GC.

Comment 8 by grt@chromium.org, Dec 12 2016

Labels: -OS-Windows -Pri-2 OS-Android Pri-1
Status: Assigned (was: WontFix)
This is happening again on tryserver.chromium.android linux_android_rel_ng:

[ RUN      ] WebRtcDataChannelTest.DataChannelGC
[WARNING:dns_config_service_posix.cc(316)] Failed to read DnsConfig.
[ERROR:devtools_http_handler.cc(221)] Cannot start http server for devtools. Stop devtools.
[WARNING:simple_synchronous_entry.cc(1054)] Could not open platform files for entry.
[ERROR:shell_android.cc(72)] Not implemented reached in void content::Shell::PlatformSetTitle(const string16&): RTCDataChannel Content Browser Test
[INFO:CONSOLE(53)] "creating offer", source: http://127.0.0.1:48323/media/datachannel_test.html (53)
[INFO:CONSOLE(57)] "creating answer", source: http://127.0.0.1:48323/media/datachannel_test.html (57)
[INFO:CONSOLE(26)] "dc1/open event", source: http://127.0.0.1:48323/media/datachannel_test.html (26)
[INFO:CONSOLE(29)] "dc1/time: probe #0", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(29)] "dc1/time: probe #1", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(29)] "dc1/time: probe #2", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(45)] "pc2/datachannel event", source: http://127.0.0.1:48323/media/datachannel_test.html (45)
[INFO:CONSOLE(29)] "dc1/time: probe #3", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(29)] "dc1/time: probe #4", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(48)] "dc2/message event: "probe #0"", source: http://127.0.0.1:48323/media/datachannel_test.html (48)
[INFO:CONSOLE(48)] "dc2/message event: "probe #1"", source: http://127.0.0.1:48323/media/datachannel_test.html (48)
[INFO:CONSOLE(48)] "dc2/message event: "probe #2"", source: http://127.0.0.1:48323/media/datachannel_test.html (48)
[INFO:CONSOLE(48)] "dc2/message event: "probe #3"", source: http://127.0.0.1:48323/media/datachannel_test.html (48)
[INFO:CONSOLE(29)] "dc1/time: probe #5", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
[INFO:CONSOLE(48)] "dc2/message event: "probe #4"", source: http://127.0.0.1:48323/media/datachannel_test.html (48)
[INFO:CONSOLE(29)] "dc1/time: probe #6", source: http://127.0.0.1:48323/media/datachannel_test.html (29)
From javascript: Error: expected '6', got '5'.
    at failTest (http://127.0.0.1:48323/media/webrtc_test_utilities.js:40:15)
    at assertEquals (http://127.0.0.1:48323/media/webrtc_test_utilities.js:250:5)
    at http://127.0.0.1:48323/media/datachannel_test.html:32:9
When executing 'testDataChannelGC();'
../../content/browser/webrtc/webrtc_content_browsertest_base.cc:90: Failure
Failed
[  FAILED  ] WebRtcDataChannelTest.DataChannelGC, where TypeParam =  and GetParam() =  (2139 ms)

This is blocking the CQ

Comment 9 by grt@chromium.org, Dec 12 2016

Summary: WebRtcDataChannelTest.DataChannelGC flaky (was: WebRtcDataChannelTest.DataChannelGC flaky on Win7 Tests bot)

Comment 10 by grt@chromium.org, Dec 12 2016

Cc: sigbjo...@opera.com
Could https://codereview.chromium.org/2531973002 ("Simple BlinkGC heap compaction.") be related?
I don't know what that build log refers to, but

 https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/196952

shows no trouble with that CL in scope. Current builds are running with that reverted, though.
Status: WontFix (was: Assigned)
I don't see any flakes in the most recent builds.
The only flakes I see are builds with hundreds of failed tests, such as
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/197355
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/196988


The flakiness dashboard doesn't look bad to me. 
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=content_browsertests&tests=WebRtcDataChannelTest.DataChannelGC

Please reopen if this becomes  an issue again.
Status: Started (was: WontFix)
Labels: -M-54 M-60
Labels: -Pri-1 Pri-2
Mergedinto: 611620
Status: Duplicate (was: Started)

Sign in to add a comment