Skip to content

fix: 4.x can't connect to the cluster when first node is non responsive #719

fix: 4.x can't connect to the cluster when first node is non responsive

fix: 4.x can't connect to the cluster when first node is non responsive #719

Triggered via pull request October 7, 2024 22:32
Status Failure
Total duration 1h 30m 37s
Artifacts 1

[email protected]

on: pull_request
Setup ITs
6s
Setup ITs
Matrix: Build
Matrix: Unit tests
Matrix: Full verify
Matrix: Cassandra ITs
Matrix: Scylla ITs
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 4 warnings
Full verify (8)
Process completed with exit code 1.
Cassandra ITs (RELEASE-3.X, 8)
The job running on runner GitHub Actions 48 has exceeded the maximum execution time of 90 minutes.
Cassandra ITs (RELEASE-3.X, 8)
The operation was canceled.
Scylla ITs (OSS-RELEASE, 8)
The job running on runner GitHub Actions 43 has exceeded the maximum execution time of 90 minutes.
Scylla ITs (OSS-RELEASE, 8)
The operation was canceled.
Scylla ITs (OSS-PRIOR-RELEASE, 8)
The job running on runner GitHub Actions 14 has exceeded the maximum execution time of 90 minutes.
Scylla ITs (OSS-PRIOR-RELEASE, 8)
The operation was canceled.
Cassandra ITs (RELEASE-4.X, 8)
The job running on runner GitHub Actions 29 has exceeded the maximum execution time of 90 minutes.
Cassandra ITs (RELEASE-4.X, 8)
The operation was canceled.
Scylla ITs (ENTERPRISE-RELEASE, 8)
Cache save failed.
Scylla ITs (ENTERPRISE-PRIOR-RELEASE, 8)
Cache save failed.
Scylla ITs (OSS-RELEASE, 8)
Cache save failed.
Scylla ITs (OSS-PRIOR-RELEASE, 8)
Cache save failed.

Artifacts

Produced during runtime
Name Size
test-results
2.53 MB