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.

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

Allow constructing a microsoft.sql.DateTimeOffset instance from a java.time.OffsetDateTime value #2340

Permit constructing a microsoft.sql.DateTimeOffset instance from a ja…

46bbb6d
Select commit
Loading
Failed to load commit list.
Merged

Allow constructing a microsoft.sql.DateTimeOffset instance from a java.time.OffsetDateTime value #2340

Permit constructing a microsoft.sql.DateTimeOffset instance from a ja…
46bbb6d
Select commit
Loading
Failed to load commit list.
Azure Pipelines / CI-MacOS succeeded Feb 27, 2024 in 23m 35s

Build #20240227.6 had test failures

Details

Tests

  • Failed: 7 (0.15%)
  • Passed: 4,563 (99.74%)
  • Other: 5 (0.11%)
  • Total: 4,575

Annotations

Check failure on line 16416 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI-MacOS

Build log #L16416

Build failed.

Check failure on line 1 in testConnectCountInLoginAndCorrectRetryCount

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI-MacOS

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:488)

Check failure on line 1 in testConnectCountInLoginAndCorrectRetryCount

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI-MacOS

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:488)

Check failure on line 1 in testClientConnectionId

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI-MacOS

testClientConnectionId

Unexpected: ClientConnectionId is not in exception message due to wrong DB: The TCP/IP connection to the host msjdbctest.database.windows.net, port 1433 has failed. Error: "Connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.". ==> expected: <true> but was: <false>
Raw output
org.opentest4j.AssertionFailedError: Unexpected: ClientConnectionId is not in exception message due to wrong DB: The TCP/IP connection to the host msjdbctest.database.windows.net, port 1433 has failed. Error: "Connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.". ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.SQLServerConnectionTest.testClientConnectionId(SQLServerConnectionTest.java:713)

Check failure on line 1 in testDefaultLoginTimeout

See this annotation in the file changed.

@azure-pipelines azure-pipelines / CI-MacOS

testDefaultLoginTimeout

timeout: 15000 timediff: 30005 ==> expected: <true> but was: <false>
Raw output
org.opentest4j.AssertionFailedError: timeout: 15000 timediff: 30005 ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.connection.TimeoutTest.verifyTimeout(TimeoutTest.java:362)
	at com.microsoft.sqlserver.jdbc.connection.TimeoutTest.testDefaultLoginTimeout(TimeoutTest.java:70)