Skip to content
Java CI - Code tests

Use a different connectTimeout for HealthManager #601

Sign in to view logs

Use a different connectTimeout for HealthManager

Use a different connectTimeout for HealthManager #601

Triggered via pull request February 21, 2024 15:01
@hamadodenehamadodene
opened #460
hamadodene:fix/healthmanager-timeout
Status Failure
Total duration 21m 24s
Artifacts 1

pr-validation.yml

on: pull_request
build
21m 14s
build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build
Process completed with exit code 1.
org.carapaceproxy.ApplyConfigurationTest ► testChangeBackendHealthManagerConfiguration: carapace-server/src/test/java/org/carapaceproxy/ApplyConfigurationTest.java#L384
Failed test found in: carapace-server/target/surefire-reports/TEST-org.carapaceproxy.ApplyConfigurationTest.xml Error: java.lang.AssertionError: expected:<9479> but was:<5000>
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
test-results Expired
2.18 MB