New issue
Advanced search Search tips

Issue 600739 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 552053
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

StreamSocket_TransportClientSocketTest.FullDuplex_WriteFirst_0 flaky on Win 10

Project Member Reported by wfh@chromium.org, Apr 5 2016

Issue description

Version: 7b80b19458c278f67243663a6adf29e39b98a6cf
OS: Windows 10.0.14295 

It seems since upgrading the Windows 10 FYI bot to "fast ring" 10.0.14295

https://blogs.windows.com/windowsexperience/2016/03/25/announcing-windows-10-insider-preview-build-14295-for-pc-and-mobile/

the net_unittests

StreamSocket_TransportClientSocketTest.FullDuplex_WriteFirst_0

has been flaking a bit. From what I can tell it only started happening after upgrade...
 

Comment 1 by wfh@chromium.org, Apr 5 2016

Cc: davidben@chromium.org
Owner: mmenke@chromium.org
Status: Assigned (was: Untriaged)
Summary: StreamSocket_TransportClientSocketTest.FullDuplex_WriteFirst_0 flaky on Win 10 (was: StreamSocket_TransportClientSocketTest.FullDuplex_WriteFirst_0 flaky on Win 10.0.14295 )
Actually, this is happening on 10.0.10586 as well

https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=net_unittests&tests=StreamSocket%2FTransportClientSocketTest.FullDuplex_WriteFirst%2F0
Failing output:

[ RUN      ] StreamSocket/TransportClientSocketTest.FullDuplex_WriteFirst/0
e:\b\build\slave\chromium_win_10\build\src\net\socket\transport_client_socket_unittest.cc(468): error: Expected: (rv) >= (0), actual: -101 vs 0
[  FAILED  ] StreamSocket/TransportClientSocketTest.FullDuplex_WriteFirst/0, where GetParam() = 0 (2 ms)

-101 is ERR_CONNECTION_RESET.  Maybe we're closing the socket while it still had pending data?  Anyhow, I think there's a fairly high chance of this falling off my radar before I get to looking into it.
Mergedinto: 552053
Status: Duplicate (was: Assigned)

Sign in to add a comment