V15 QA added a fix for flaky integration tests run on SQL Server Linux #18965
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
And a check for docker
…gratio n tests on each PR
…tion-tests-handshake-pipeline-issue
…tion-tests-handshake-pipeline-issue # Conflicts: # build/nightly-E2E-test-pipelines.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the issue we have seen on the pipeline for SQL Server Integration tests running on Linux. It adds a check to ensure the SQL Server Docker Image is ready.
The issue was :
Error Message: Microsoft.Data.SqlClient.SqlException : A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - Success)It only happens sometimes, which is why I suspect the reason for this happening is that we do not wait till the SQL Server Docker Image is ready.