Skip to content
cf

Fix pytorch memory curve estimation for rmm backed allocator #350

Sign in to view logs

Fix pytorch memory curve estimation for rmm backed allocator

Fix pytorch memory curve estimation for rmm backed allocator #350

Triggered via pull request October 3, 2024 23:40
@VibhuJawaVibhuJawa
synchronize #94
VibhuJawa:vjawa/fix_memory_profiling_with_rmm
Status Success
Total duration 49s
Artifacts –

base.yml

on: pull_request
Matrix: tests
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
tests (3.8)
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/
tests (3.10)
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/
tests (3.9)
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/