Skip to content

The WebSocket client pool should not starve on connect error. #1321

The WebSocket client pool should not starve on connect error.

The WebSocket client pool should not starve on connect error. #1321

Triggered via pull request January 9, 2025 14:39
Status Failure
Total duration 6h 0m 28s
Artifacts

ci-4.x.yml

on: pull_request
Matrix: Run tests
Deploy to OSSRH
0s
Deploy to OSSRH
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Run tests (windows-latest, 8)
The job running on runner GitHub Actions 16 has exceeded the maximum execution time of 360 minutes.
Run tests (windows-latest, 8)
The operation was canceled.
Run tests (ubuntu-latest, 8)
The job running on runner GitHub Actions 285 has exceeded the maximum execution time of 360 minutes.
Run tests (ubuntu-latest, 8)
The operation was canceled.
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
The job running on runner GitHub Actions 102 has exceeded the maximum execution time of 360 minutes.
Run tests (ubuntu-latest, 8, -PtestDomainSockets)
The operation was canceled.
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
The job running on runner GitHub Actions 97 has exceeded the maximum execution time of 360 minutes.
Run tests (ubuntu-latest, 8, -PtestNativeTransport)
The operation was canceled.
Run tests (ubuntu-latest, 21)
The job running on runner GitHub Actions 331 has exceeded the maximum execution time of 360 minutes.
Run tests (ubuntu-latest, 21)
The operation was canceled.