-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.Data.SqlClient.Tests (eg ExecuteScalarAsyncTest) test break CI with "The server was not found or was not accessible" #22028
Comments
@saurabh500 @corivera as discussed this is the one that needs logging added. It keeps getting hit in CI - note some of the hits are tracked in https://github.com/dotnet/corefx/issues/17925 (although that may cover other issuses.. logging should untangle all this) |
@danmosemsft ack. Looking into the logging. |
Here's another test failure showing a server connection failure .. hopefully the logging will help all tests that hit this.
System.Data.SqlClient.Tests.SqlConnectionBasicTests.ConnectionTest |
@saurabh500 here's a hit with your new logging
https://mc.dot.net/#/user/danmosemsft/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/f8b7bd8f5e58354e4e659ad01a49ae7a622f7c27/workItem/System.Data.SqlClient.Tests/wilogs Thoughts? |
Uh - actually by the timestamps this logging may correspond to the subsequent, successful test... |
The logs pasted don't have anything interesting. They do point to a failure. They don't have the logs from my changes. Also the link has all successful executions. Can you point me to the error logs for the failure above? |
@saurabh500 go to https://mc.dot.net/#/user/danmosemsft/pr~2Fjenkins~2Fdotnet~2Fcorefx~2Fmaster~2F/test~2Ffunctional~2Fcli~2F/f8b7bd8f5e58354e4e659ad01a49ae7a622f7c27/workItem/System.Data.SqlClient.Tests/wilogs and open the sectoin marked Ubuntu.1404.Amd64.Open:Release-x64. In there is the console output with the output above. |
@saurabh500 if we don't think we can figure this out imminently it might be worth changing some of these to outer loop so they don't keep breaking CI. |
@danmosemsft The link above has my logs. It seems like the TcpListener.Start() call may have succeeded for the server, but the socket may not by open. |
@saurabh500 it broke again in CI -- attached above. Can you please take a look? Hopefully we can knock this one on the head. |
@saurabh500 here's a failure on ExecuteScalarTest, with logging. Ubuntu1404. Can you please look?
|
@saurabh500 here's another, different test, on Centos
|
|
@corivera this continues to fail sporadically. Do the logs help? |
This is fixed with https://github.com/dotnet/corefx/issues/25620 and the tests have been re-enabled for sometime. The tests are passing |
https://ci.dot.net/job/dotnet_corefx/job/release_2.0.0/job/ubuntu14.04_release_prtest/185/consoleText
The text was updated successfully, but these errors were encountered: