Skip to content

fix: add ROCm compatiblity to storages #3803

fix: add ROCm compatiblity to storages

fix: add ROCm compatiblity to storages #3803

Triggered via pull request September 24, 2024 14:49
Status Success
Total duration 23m 54s
Artifacts

test-next.yml

on: pull_request
Matrix: test-next
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test-next (3.11, atlas, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-next (3.10, atlas, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-next (3.11, nomesh, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test-next (3.10, nomesh, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/