New issue
Advanced search Search tips

Issue 608117 link

Starred by 3 users
Status: Fixed
Owner:
guidou@chromium.org
Closed: May 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

WebRtcDataChannelTest.DataChannelGC test failure on DrMemory bot

Project Member Reported by osh...@chromium.org, Apr 30 2016 
looks like it's been failing for a while.

The oldest one I could find:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%20Browser%20%28DrMemory%20full%29%20%284%29/builds/7689

The following looks culprit:

https://chromium.googlesource.com/chromium/src/+/fc3a3ed89dd1fac2becb60615ccf6e78a24bbbb5

guidou@, can yo look into this?

log:
[1780:2700:0429/153314:5639326:INFO:CONSOLE(53)] "creating offer", source: http://127.0.0.1:49972/media/datachannel_test.html (53)
[1780:2700:0429/153329:5653647:INFO:CONSOLE(57)] "creating answer", source: http://127.0.0.1:49972/media/datachannel_test.html (57)
[1780:2436:0429/153330:5655223:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153331:5656190:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2700:0429/153335:5659591:INFO:CONSOLE(26)] "dc1/open event", source: http://127.0.0.1:49972/media/datachannel_test.html (26)
[1780:2700:0429/153335:5659934:INFO:CONSOLE(29)] "dc1/time: probe #0", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2436:0429/153335:5660121:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153335:5660137:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2700:0429/153335:5660277:INFO:CONSOLE(29)] "dc1/time: probe #1", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2700:0429/153336:5660465:INFO:CONSOLE(29)] "dc1/time: probe #2", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2700:0429/153336:5660667:INFO:CONSOLE(29)] "dc1/time: probe #3", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2436:0429/153337:5662243:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153337:5662259:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153339:5664318:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153339:5664333:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2700:0429/153340:5665269:INFO:CONSOLE(45)] "pc2/datachannel event", source: http://127.0.0.1:49972/media/datachannel_test.html (45)
[1780:2700:0429/153341:5665550:INFO:CONSOLE(48)] "dc2/message event: "probe #0"", source: http://127.0.0.1:49972/media/datachannel_test.html (48)
[1780:2700:0429/153341:5665597:INFO:CONSOLE(48)] "dc2/message event: "probe #1"", source: http://127.0.0.1:49972/media/datachannel_test.html (48)
[1780:2700:0429/153341:5665628:INFO:CONSOLE(29)] "dc1/time: probe #4", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2700:0429/153341:5665675:INFO:CONSOLE(48)] "dc2/message event: "probe #2"", source: http://127.0.0.1:49972/media/datachannel_test.html (48)
[1780:2700:0429/153341:5665675:INFO:CONSOLE(48)] "dc2/message event: "probe #3"", source: http://127.0.0.1:49972/media/datachannel_test.html (48)
[1780:2700:0429/153341:5665675:INFO:CONSOLE(29)] "dc1/time: probe #5", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2700:0429/153341:5665691:INFO:CONSOLE(29)] "dc1/time: probe #6", source: http://127.0.0.1:49972/media/datachannel_test.html (29)
[1780:2436:0429/153341:5666408:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
[1780:2436:0429/153342:5666533:INFO:socket_host_udp.cc(360)] sendto() has failed twice returning a  transient error net::ERR_ADDRESS_INVALID. Dropping the packet.
From javascript: Error: expected '6', got '4'.
at failTest (http://127.0.0.1:49972/media/webrtc_test_utilities.js:39:15)
at assertEquals (http://127.0.0.1:49972/media/webrtc_test_utilities.js:239:5)
at http://127.0.0.1:49972/media/datachannel_test.html:32:9
When executing 'testDataChannelGC();'
c:\b\build\slave\drm-cr\build\src\content\test\webrtc_content_browsertest_base.cc(94): error: Failed
Project Member

Comment 1 by bugdroid1@chromium.org, Apr 30 2016 

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

commit 70a633536626d0a6d0a661c3e019f48d98b76272
Author: oshima <oshima@chromium.org>
Date: Sat Apr 30 01:10:48 2016

Exclude WebRtcDataChannelTest.DataChannelGC on DrMemory bot

BUG= 608117 
TBR=guidou@chromium.org

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

[modify] https://crrev.com/70a633536626d0a6d0a661c3e019f48d98b76272/tools/valgrind/gtest_exclude/content_browsertests.gtest-drmemory.txt

Comment 2 by guidou@chromium.org, May 11 2016

Status: Fixed (was: Assigned)
This failure looks very specific to drmemory. I think the exclusion landed by oshima@ is enough.

Comment 3 by thestig@chromium.org, Aug 3 2016 

guidou: Yes, but simply excluding the test and calling it done is like sweeping dirt under the rug. Is the test actually sensitive to timing issues? If so, would such timing issues occasionally happen without DrMemory as well, thus leaving to test flakiness?
►

Sign in to add a comment