Increase connection timeout in DW/MSSQL test pipelines#3132
Merged
Aniruddh25 merged 2 commits intomainfrom Feb 15, 2026
Merged
Conversation
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR increases SQL Server connection timeout values from 5 to 30 seconds in CI pipeline configurations to address connection timeout failures during pre-login handshake, particularly when LocalDB instances are warming up in CI environments.
Changes:
- Updated connection timeout from 5 to 30 seconds in MSSQL pipeline configuration (both Linux and Windows jobs)
- Updated connection timeout from 5 to 30 seconds in DWSQL pipeline configuration (both Linux and Windows jobs)
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.pipelines/mssql-pipelines.yml |
Increased connection timeout to 30 seconds for both Linux (line 79) and Windows (line 164) job connection strings |
.pipelines/dwsql-pipelines.yml |
Increased connection timeout to 30 seconds for both Linux (line 78) and Windows (line 160) job connection strings |
Contributor
|
@Aniruddh25 I've opened a new pull request, #3133, to work on those changes. Once the pull request is ready, I'll request review from you. |
2 tasks
…3133) ## Why make this change? Addresses review feedback from #3132 requesting consistency between pipeline and test configuration connection timeout values. Pipeline configs were updated to use 30-second timeouts, but test configs still used 5 seconds. ## What is this change? Updated `Connection Timeout` parameter from 5 to 30 seconds in three test configuration files: - `src/Service.Tests/dab-config.MsSql.json` - `src/Service.Tests/dab-config.DwSql.json` - `src/Service.Tests/Multidab-config.MsSql.json` This aligns test configurations with pipeline configurations (`.pipelines/mssql-pipelines.yml`, `.pipelines/dwsql-pipelines.yml`) to ensure consistent timeout behavior across test and CI environments. ## How was this tested? - [ ] Integration Tests - [ ] Unit Tests Configuration changes only - no functional code changes requiring new tests. ## Sample Request(s) N/A - Configuration changes only. <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/Azure/data-api-builder/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: Aniruddh25 <3513779+Aniruddh25@users.noreply.github.com>
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
anushakolan
approved these changes
Feb 15, 2026
souvikghosh04
approved these changes
Feb 15, 2026
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
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.
Why make this change?
Recent test failures show connection timeouts. The logs showed ~6-second pre-login initialization timeout, a 5-second timeout is quite aggressive — especially for a CI pipeline where the LocalDB instance may still be warming up. Hence, increasing it (e.g., Connection Timeout=30) to give the server more time to respond.
Sample error:
What is the change?
Increase connection timeout value from 5 to 30 seconds for both DWSQL and MSSQL pipelines.