Skip to content
Azure Pipelines / public-mssql-jdbc.windows succeeded Feb 2, 2025 in 34m 7s

Build #20250202.1 had test failures

Details

Tests

  • Failed: 1 (0.01%)
  • Passed: 16,417 (99.01%)
  • Other: 163 (0.98%)
  • Total: 16,581

Annotations

Check failure on line 1420 in Build log

See this annotation in the file changed.

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

Build log #L1420

Build failed.

Check failure on line 1 in testGetFunctionColumns

See this annotation in the file changed.

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

testGetFunctionColumns

Unexpected error message occurred!An error occurred during the current command (Done status 0). Transaction (Process ID 83) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Raw output
org.opentest4j.AssertionFailedError: Unexpected error message occurred!An error occurred during the current command (Done status 0). Transaction (Process ID 83) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
	at com.microsoft.sqlserver.jdbc.databasemetadata.DatabaseMetaDataTest.testGetFunctionColumns(DatabaseMetaDataTest.java:710)