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(iot-dev): fix bug where client opening with retry isn't cancelled by close #1760

Merged
merged 1 commit into from
Nov 2, 2023

fix(iot-dev): fix bug where client opening with retry isn't cancelled…

0fea8ec
Select commit
Loading
Failed to load commit list.
Merged

fix(iot-dev): fix bug where client opening with retry isn't cancelled by close #1760

fix(iot-dev): fix bug where client opening with retry isn't cancelled…
0fea8ec
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Java Prod failed Nov 2, 2023 in 3m 44s

Build #140528_Java Prod_merge_20231102.1 had test failures

1 errors / 16 warnings

Details

Tests

  • Failed: 984 (8.55%)
  • Passed: 9,888 (85.94%)
  • Other: 634 (5.51%)
  • Total: 11,506

Annotations

Check failure on line 4519 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Java Prod

Build log #L4519 

PowerShell exited with code '1'.

Check failure on line 1 in closeSucceeds

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Java Prod

closeSucceeds 

JMockit wasn't properly initialized; please ensure that jmockit precedes junit in the runtime classpath, or use @RunWith(JMockit.class)
Raw output 
java.lang.IllegalStateException: JMockit wasn't properly initialized; please ensure that jmockit precedes junit in the runtime classpath, or use @RunWith(JMockit.class)
	at com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClientTest.closeSucceeds(ProvisioningDeviceClientTest.java:175)

Check failure on line 1 in constructorSucceeds

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Java Prod

constructorSucceeds 

Security provider cannot be null
Raw output 
java.lang.IllegalArgumentException: Security provider cannot be null
	at com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClientTest.constructorSucceeds(ProvisioningDeviceClientTest.java:70)

Check failure on line 1 in registerSucceeds

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Java Prod

registerSucceeds 

Security provider cannot be null
Raw output 
java.lang.IllegalArgumentException: Security provider cannot be null
	at com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClientTest.registerSucceeds(ProvisioningDeviceClientTest.java:144)

Check failure on line 1 in closeTerminatedSucceeds

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Java Prod

closeTerminatedSucceeds 

JMockit wasn't properly initialized; please ensure that jmockit precedes junit in the runtime classpath, or use @RunWith(JMockit.class)
Raw output 
java.lang.IllegalStateException: JMockit wasn't properly initialized; please ensure that jmockit precedes junit in the runtime classpath, or use @RunWith(JMockit.class)
	at com.microsoft.azure.sdk.iot.provisioning.device.ProvisioningDeviceClientTest.closeTerminatedSucceeds(ProvisioningDeviceClientTest.java:200)
View more details on Azure Pipelines