Skip to content

Cluster N node Chaos Test #809

Cluster N node Chaos Test

Cluster N node Chaos Test #809

Triggered via schedule January 11, 2024 19:30
Status Failure
Total duration 45m 10s
Artifacts
Matrix: test-cluster-n-node-chaos
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 8 warnings
test-cluster-n-node-chaos (pod_kill, proxy)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
test-cluster-n-node-chaos (pod_kill, proxy)
The operation was canceled.
test-cluster-n-node-chaos (pod_kill, proxy)
Process completed with exit code 143.
test-cluster-n-node-chaos (pod_failure, datanode)
The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_kill, datanode)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_failure, proxy)
The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_failure, indexnode)
The job running on runner GitHub Actions 4 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_failure, indexnode)
Process completed with exit code 1.
test-cluster-n-node-chaos (pod_failure, indexnode)
The operation was canceled.
test-cluster-n-node-chaos (pod_failure, indexnode)
Process completed with exit code 1.
test-cluster-n-node-chaos (pod_failure, querynode)
The job running on runner GitHub Actions 6 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_kill, querynode)
The job running on runner GitHub Actions 9 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_kill, querynode)
Process completed with exit code 1.
test-cluster-n-node-chaos (pod_kill, indexnode)
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 40 minutes.
test-cluster-n-node-chaos (pod_kill, indexnode)
The operation was canceled.
test-cluster-n-node-chaos (pod_kill, indexnode)
Process completed with exit code 1.
test-cluster-n-node-chaos (pod_kill, indexnode)
Process completed with exit code 1.
test-cluster-n-node-chaos (pod_kill, proxy)
The following actions uses node12 which is deprecated and will be forced to run on node16: helm/[email protected], actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-cluster-n-node-chaos (pod_failure, datanode)
Runner GitHub Actions 2 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_kill, datanode)
Runner GitHub Actions 5 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_failure, proxy)
Runner GitHub Actions 3 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_failure, indexnode)
Runner GitHub Actions 4 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_failure, querynode)
Runner GitHub Actions 6 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_kill, querynode)
Runner GitHub Actions 9 did not respond to a cancelation request with 00:05:00.
test-cluster-n-node-chaos (pod_kill, indexnode)
Runner GitHub Actions 7 did not respond to a cancelation request with 00:05:00.