Skip to content

Valgrind

Valgrind #545

Manually triggered November 21, 2024 18:23
Status Failure
Total duration 1h 3m 53s
Artifacts 1

valgrind.yml

on: workflow_dispatch
look-for-wheel-in-jfrog
10s
look-for-wheel-in-jfrog
build-manylinux-wheel  /  get-runner-os
0s
build-manylinux-wheel / get-runner-os
Matrix: build-manylinux-wheel / cibuildwheel
Matrix: build-manylinux-wheel / test-self-hosted
upload-built-wheel-to-jfrog  /  Upload artifacts to JFrog
9s
upload-built-wheel-to-jfrog / Upload artifacts to JFrog
delete-artifacts  /  delete-artifacts
2s
delete-artifacts / delete-artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
valgrind
Process completed with exit code 1.
upload-built-wheel-to-jfrog / Upload artifacts to JFrog
The following actions use a deprecated Node.js version and will be forced to run on node20: jfrog/setup-jfrog-cli@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
valgrind
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
valgrind
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
aerospike~aerospike-client-python~DEK1SB.dockerbuild
32.3 KB