Skip to content

Make gRPC service report backups as FAILED if lose their callback future #2505

Make gRPC service report backups as FAILED if lose their callback future

Make gRPC service report backups as FAILED if lose their callback future #2505

Triggered via pull request October 17, 2024 11:51
Status Failure
Total duration 4m 57s
Artifacts

ci.yml

on: pull_request
Matrix: build
Matrix: debian-build
Matrix: integration-tests
Matrix: k8ssandra-e2e-tests
Matrix: publish-debian
publish-docker-master
0s
publish-docker-master
publish-docker
0s
publish-docker
publish-pypi
0s
publish-pypi
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
build (3.11)
Process completed with exit code 1.
build (3.10)
The job was canceled because "_3_11" failed.
build (3.10)
The operation was canceled.
build (3.8)
The job was canceled because "_3_11" failed.
build (3.8)
The operation was canceled.
build (3.9)
The job was canceled because "_3_11" failed.
build (3.9)
The operation was canceled.
build (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
debian-build (focal)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/