Skip to content

Localized file check-in by OneLocBuild Task: Build definition ID 5196…

5651e34
Select commit
Loading
Failed to load commit list.
Closed

Localized file check-in by OneLocBuild Task: Build definition ID 51965: Build ID 205515539 #668

Localized file check-in by OneLocBuild Task: Build definition ID 5196…
5651e34
Select commit
Loading
Failed to load commit list.
Azure Pipelines / microsoft.go-sqlcmd failed Jan 29, 2026 in 3m 57s

Build #20260129.43 had test failures

Details

Tests

  • Failed: 14 (2.06%, 14 new, 0 recurring)
  • Passed: 643 (94.70%)
  • Other: 22 (3.24%)
  • Total: 679
Code coverage

  • 2870 of 3536 line covered (81.17%)

Annotations

Check failure on line 19 in Build log

See this annotation in the file changed.

@azure-pipelines 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_PipedInput_LiveConnection

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.go-sqlcmd

TestE2E_PipedInput_LiveConnection

Failed
Raw output
=== RUN   TestE2E_PipedInput_LiveConnection
    e2e_test.go:179: Using ActiveDirectoryAzurePipelines authentication
    e2e_test.go:187: 
        	Error Trace:	/home/vsts/work/1/s/cmd/modern/e2e_test.go:187
        	Error:      	Received unexpected error:
        	            	exit status 1
        	Test:       	TestE2E_PipedInput_LiveConnection
        	Messages:   	piped query should succeed with live connection: mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	            	mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
--- FAIL: TestE2E_PipedInput_LiveConnection (0.56s)

Check failure on line 1 in TestE2E_QueryFlag_LiveConnection

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.go-sqlcmd

TestE2E_QueryFlag_LiveConnection

Failed
Raw output
=== RUN   TestE2E_QueryFlag_LiveConnection
    e2e_test.go:245: Using ActiveDirectoryAzurePipelines authentication
    e2e_test.go:252: 
        	Error Trace:	/home/vsts/work/1/s/cmd/modern/e2e_test.go:252
        	Error:      	Received unexpected error:
        	            	exit status 1
        	Test:       	TestE2E_QueryFlag_LiveConnection
        	Messages:   	-Q query should succeed: mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	            	mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
--- FAIL: TestE2E_QueryFlag_LiveConnection (0.47s)

Check failure on line 1 in TestE2E_InputFile_LiveConnection

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.go-sqlcmd

TestE2E_InputFile_LiveConnection

Failed
Raw output
=== RUN   TestE2E_InputFile_LiveConnection
    e2e_test.go:284: Using ActiveDirectoryAzurePipelines authentication
    e2e_test.go:291: 
        	Error Trace:	/home/vsts/work/1/s/cmd/modern/e2e_test.go:291
        	Error:      	Received unexpected error:
        	            	exit status 1
        	Test:       	TestE2E_InputFile_LiveConnection
        	Messages:   	-i input file should succeed: mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	            	mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
--- FAIL: TestE2E_InputFile_LiveConnection (0.40s)

Check failure on line 1 in TestRunInputFiles

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.go-sqlcmd

TestRunInputFiles

Failed
Raw output
=== RUN   TestRunInputFiles
    sqlcmd_test.go:264: 
        	Error Trace:	/home/vsts/work/1/s/cmd/sqlcmd/sqlcmd_test.go:264
        	Error:      	Received unexpected error:
        	            	mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	Test:       	TestRunInputFiles
        	Messages:   	run
    sqlcmd_test.go:265: 
        	Error Trace:	/home/vsts/work/1/s/cmd/sqlcmd/sqlcmd_test.go:265
        	Error:      	Not equal: 
        	            	expected: 0
        	            	actual  : 1
        	Test:       	TestRunInputFiles
        	Messages:   	exitCode
    sqlcmd_test.go:268: 
        	Error Trace:	/home/vsts/work/1/s/cmd/sqlcmd/sqlcmd_test.go:268
        	Error:      	Not equal: 
        	            	expected: "100\n\n(1 row affected)\n100\n\n(1 row affected)\n"
        	            	actual  : "mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.\nmssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.\n"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1,7 +1,3 @@
        	            	-100
        	            	+mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	            	+mssql: login error: Cannot open server 'ssmstests' requested by the login. Client with IP address '172.175.64.245' is not allowed to access the server.  To enable access, use the Azure Management Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range.  It may take up to five minutes for this change to take effect.
        	            	 
        	            	-(1 row affected)
        	            	-100
        	            	-
        	            	-(1 row affected)
        	            	-
        	Test:       	TestRunInputFiles
        	Messages:   	Incorrect output from run
--- FAIL: TestRunInputFiles (0.43s)