Fix sqlcmd hanging for ~10 minutes after query timeout on Linux #682
Azure Pipelines / microsoft.go-sqlcmd
failed
Feb 6, 2026 in 3m 58s
Build #20260206.2 had test failures
Details
- Failed: 2 (0.27%, 0 new, 2 recurring)
- Passed: 702 (96.43%)
- Other: 24 (3.30%)
- Total: 728
- 2866 of 3537 lines covered (81.03%)
Annotations
Check failure on line 19 in Build log
azure-pipelines / microsoft.go-sqlcmd
Build log #L19
There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.
Check failure on line 1 in TestE2E_QueryTimeout_LiveConnection
azure-pipelines / microsoft.go-sqlcmd
TestE2E_QueryTimeout_LiveConnection
Failed
Raw output
=== RUN TestE2E_QueryTimeout_LiveConnection
e2e_test.go:336:
Error Trace: /home/vsts/work/1/s/cmd/modern/e2e_test.go:336
Error: An error is expected but got nil.
Test: TestE2E_QueryTimeout_LiveConnection
Messages: query should timeout and return an error
e2e_test.go:348: Query timed out correctly in 1.027188497s: Timeout expired
--- FAIL: TestE2E_QueryTimeout_LiveConnection (1.03s)
Check failure on line 1 in TestE2E_QueryTimeout_LiveConnection
azure-pipelines / microsoft.go-sqlcmd
TestE2E_QueryTimeout_LiveConnection
Failed
Raw output
=== RUN TestE2E_QueryTimeout_LiveConnection
e2e_test.go:336:
Error Trace: /home/vsts/work/1/s/cmd/modern/e2e_test.go:336
Error: An error is expected but got nil.
Test: TestE2E_QueryTimeout_LiveConnection
Messages: query should timeout and return an error
e2e_test.go:348: Query timed out correctly in 1.026740665s: Timeout expired
--- FAIL: TestE2E_QueryTimeout_LiveConnection (1.03s)
Loading