projects / platform / upstream / dotnet / runtime.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ad4daf7) | patch
Updating timeout in `SslStream_SameCertUsedForClientAndServer_Ok` to match the rest...
authorVladimir Sadov <vsadov@microsoft.com>
Sun, 17 Feb 2019 00:10:44 +0000 (16:10 -0800)
committerVladimir Sadov <vsadov@microsoft.com>
Sun, 17 Feb 2019 00:10:44 +0000 (16:10 -0800)
commit8016f5dea9e83d6fe1f024629a16868ff5b736e1
treee14b24a0f4e4f24fcbb3b9cce4196f6f2af327f1tree | snapshot
parentad4daf74f90754c1c151852f88cea2cc26116a53commit | diff
Updating timeout in `SslStream_SameCertUsedForClientAndServer_Ok` to match the rest of the tests in the area.
All other passing tests standardise on `TestConfiguration.PassingTestTimeoutMilliseconds`

There seems to be no reasons for SslStream_SameCertUsedForClientAndServer_Ok` to use a hardcoded timeout.
Also the hardcoded timeout is significantly shorter and occasionally leads to failures on low-spec test VMs.

Commit migrated from https://github.com/dotnet/corefx/commit/8919cbdd960f41ba2f87c210d5f85d0d8a3c1276
src/libraries/System.Net.Security/tests/FunctionalTests/SslStreamCredentialCacheTest.cs diff | blob | history
Domain: Dotnet / Core;