Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fixed bulkcopy metadata query to make use of cached data if available #2231

Merged
merged 2 commits into from
Oct 11, 2023

Brackets around if statements

2084e80
Select commit
Loading
Failed to load commit list.
Merged

Fixed bulkcopy metadata query to make use of cached data if available #2231

Brackets around if statements
2084e80
Select commit
Loading
Failed to load commit list.
Azure Pipelines / public-mssql-jdbc.linux succeeded Oct 11, 2023 in 51m 52s

Build #20231011.1 had test failures

4 errors / 4 warnings

Details

Tests

  • Failed: 10 (0.18%)
  • Passed: 5,424 (99.71%)
  • Other: 6 (0.11%)
  • Total: 5,440

Annotations

Check failure on line 16615 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L16615 

Build failed.

Check failure on line 16600 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L16600 

Build failed.

Check failure on line 16969 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L16969 

Build failed.

Check failure on line 17325 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L17325 

Build failed.

Check failure on line 1 in testConnectCountInLoginAndCorrectRetryCount

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testConnectCountInLoginAndCorrectRetryCount 

Execution took too long. ==> expected: <true> but was: <false>
Raw output 
org.opentest4j.AssertionFailedError: Execution took too long. ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.SQLServerConnectionTest.testConnectCountInLoginAndCorrectRetryCount(SQLServerConnectionTest.java:477)

Check failure on line 1 in testConnectCountInLoginAndCorrectRetryCount

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testConnectCountInLoginAndCorrectRetryCount 

Execution took too long. ==> expected: <true> but was: <false>
Raw output 
org.opentest4j.AssertionFailedError: Execution took too long. ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.SQLServerConnectionTest.testConnectCountInLoginAndCorrectRetryCount(SQLServerConnectionTest.java:477)

Check failure on line 1 in testAdaptiveBuffering

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testAdaptiveBuffering 

Invalid object name 'resilencyTestTable'.
Raw output 
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'resilencyTestTable'.
	at com.microsoft.sqlserver.jdbc.resiliency.ResultSetsWithResiliencyTest.verifyResultSetResponseBuffering(ResultSetsWithResiliencyTest.java:468)
	at com.microsoft.sqlserver.jdbc.resiliency.ResultSetsWithResiliencyTest.testAdaptiveBuffering(ResultSetsWithResiliencyTest.java:91)

Check failure on line 1 in testAdaptiveBufferingWithPartiallyBufferedResultSet

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testAdaptiveBufferingWithPartiallyBufferedResultSet 

Invalid object name 'resilencyTestTable'. ==> expected: <true> but was: <false>
Raw output 
org.opentest4j.AssertionFailedError: Invalid object name 'resilencyTestTable'. ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.resiliency.ResultSetsWithResiliencyTest.testAdaptiveBufferingWithPartiallyBufferedResultSet(ResultSetsWithResiliencyTest.java:160)
View more details on Azure Pipelines