Skip to content

Fix NCCL initialization when i6pn runc containers are scheduled on the same machine #5135

Fix NCCL initialization when i6pn runc containers are scheduled on the same machine

Fix NCCL initialization when i6pn runc containers are scheduled on the same machine #5135

Triggered via pull request October 9, 2024 10:40
Status Success
Total duration 36s
Artifacts

docs.yml

on: pull_request
Doc generation tests
23s
Doc generation tests
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Doc generation tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/