Skip to content
cf.backends

Fix pytorch memory curve estimation for rmm backed allocator (#94) #362

Sign in to view logs

Fix pytorch memory curve estimation for rmm backed allocator (#94)

Fix pytorch memory curve estimation for rmm backed allocator (#94) #362

Triggered via push October 10, 2024 21:55
@VibhuJawaVibhuJawa
pushed a043f45
main
Status Success
Total duration 2m 33s
Artifacts –

cf_backends.yml

on: push
Matrix: pytorch
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
pytorch (3.8, ubuntu-latest, ~=1.12.0)
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/
pytorch (3.8, ubuntu-latest, ~=1.13.0)
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/
pytorch (3.8, ubuntu-latest, ~=1.11.0)
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/