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

Fix pipeline failure by handling strict mode exceptions for null values. #2628

Merged
merged 2 commits into from
Mar 5, 2025

Updated test cases

7e36f54
Select commit
Loading
Failed to load commit list.
Merged

Fix pipeline failure by handling strict mode exceptions for null values. #2628

Updated test cases
7e36f54
Select commit
Loading
Failed to load commit list.
Azure Pipelines / public-mssql-jdbc.windows succeeded Mar 5, 2025 in 30m 37s

Build #20250305.2 had test failures

1 errors / 17 warnings

Details

Tests

  • Failed: 1 (0.01%)
  • Passed: 16,469 (99.03%)
  • Other: 161 (0.97%)
  • Total: 16,631

Annotations

Check failure on line 42456 in Build log

See this annotation in the file changed.

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

Build log #L42456 

Build failed.

Check failure on line 1 in testUpdateCountAfterRaiseError

See this annotation in the file changed.

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

testUpdateCountAfterRaiseError 

Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Raw output 
com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
	at com.microsoft.sqlserver.jdbc.unit.statement.StatementTest$TCUpdateCountAfterRaiseError.testUpdateCountAfterRaiseError(StatementTest.java:2488)
View more details on Azure Pipelines