New issue
Advanced search Search tips

Issue 665957 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 665686
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

"SSLClientSocketTest.ConnectClientAuthSendNullCert" is flaky

Project Member Reported by chromium...@appspot.gserviceaccount.com, Nov 16 2016

Issue description

"SSLClientSocketTest.ConnectClientAuthSendNullCert" is flaky.

This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label.

We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyPAsSBUZsYWtlIjFTU0xDbGllbnRTb2NrZXRUZXN0LkNvbm5lY3RDbGllbnRBdXRoU2VuZE51bGxDZXJ0DA.

Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
 
 Issue 665827  has been merged into this issue.
Owner: davidben@chromium.org
Status: Assigned (was: Untriaged)
David, I don't see any recent changes that would cause these tests to be flaky but since you're to "blame" for the tests, would you mind taking a look?  Thanks.

Cc: mmenke@chromium.org
Components: -Tests>Flaky Internals>Network>SSL
The first reported failure involves a ton of unrelated-looking tests failing. I'm guessing some swarming job crashed.
https://build.chromium.org/p/tryserver.chromium.android/builders/android_n5x_swarming_rel/builds/68942

The others are failing with:
SSLClientSocketTest.ConnectClientAuthSendNullCert (run #3):
[ RUN      ] SSLClientSocketTest.ConnectClientAuthSendNullCert
[ERROR:spawner_communicator.cc(251)] request failed, error: -324
[ERROR:ssl_client_socket_unittest.cc(780)] Could not start SpawnedTestServer
../../net/socket/ssl_client_socket_unittest.cc:1172: Failure
Value of: StartTestServer(ssl_options)
  Actual: false
Expected: true
[  FAILED  ] SSLClientSocketTest.ConnectClientAuthSendNullCert (722 ms)

So this looks less to do with the test and more SpawnedTestServer's problems. spawner_communicator.cc reports error -324 which is ERR_EMPTY_RESPONSE.

+mmenke, do you know who maintains the SpawnedTestServer glue? Someone from infra I assume?
Cc: jbudorick@chromium.org
+cc jbudorick@chromium.org
Mergedinto: 665686
Status: Duplicate (was: Assigned)

Sign in to add a comment