Closed ryanbrandenburg closed 6 years ago
PublishAndRun_Test failed again.
This is the same basic problem as aspnet/EntityFrameworkCore#12706.
PublishAndRun_Test failed again.
PublishAndRun_Test failed again.
PublishAndRun_Test failed again.
OpenIdConnectTestSuite failed again.
NtlmAuthenticationTest failed again.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
I can handle the IIS test failures.
This is more than just a flaky tests. It fails consistently.
System.AggregateException: One or more errors occurred. (Keyword not supported: 'PoolBlockingPeriod'.) ---> System.ArgumentException: Keyword not supported: 'PoolBlockingPeriod'.
at System.Data.SqlClient.SqlConnectionStringBuilder.Reset(Keywords index)
at System.Data.SqlClient.SqlConnectionStringBuilder.Clear()
at System.Data.Common.DbConnectionStringBuilder.set_ConnectionString(String value)
at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerConnection.CreateMasterConnection()
This looks like more fallout from https://github.com/dotnet/corefx/issues/30720
cc @smitpatel any idea if this has flowed into a corefx build yet?
I think the rest of tests are fine now based on the latest test run. Only inproc tests are failing.
I see. I'm seeing a bunch of failures on VSTS too, btw. https://dotnet.visualstudio.com/public/_build/results?buildId=8453&view=ms.vss-test-web.test-result-details
My preliminary testing shows that the fix is available in SqlClient package version 4.6.0-preview1-26725-04
Let's see result of https://github.com/aspnet/EntityFrameworkCore/pull/12829
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Confirmed that latest version of dependencies resolves the issue with PoolBlockingPeriod.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed with about the same error. PublishAndRun_Test failed with about the same error. PublishAndRun_Test failed with about the same error. PublishAndRun_Test failed with about the same error. PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
https://github.com/aspnet/MusicStore/pull/862 should fix this issue. 2.1 shouldn't have been run with IIS in-proc.
This test fails occasionally with the following error: