We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bash start_test.sh torch_allreduce_test.py --backend ucc
Wrong results, segfault at exit
bash start_test.sh torch_allreduce_test.py --backend gloo --use-cuda
Wrong results
If I change the torch_ucc_test_setup.py like this
torch_ucc_test_setup.py
- dist.init_process_group('ucc', rank=comm_rank, world_size=comm_size) + dist.init_process_group('gloo', rank=comm_rank, world_size=comm_size)
and run
bash start_test.sh torch_allreduce_test.py --backend ucc # on CPU
I will get
Traceback (most recent call last): File "/home/gaoxiang/torch_ucc/test/torch_allreduce_test.py", line 24, in <module> dist.all_reduce(tensor_ucc) File "/home/gaoxiang/.local/lib/python3.9/site-packages/torch/distributed/distributed_c10d.py", line 1269, in all_reduce work.wait() RuntimeError: [../third_party/gloo/gloo/transport/tcp/pair.cc:598] Connection closed by peer [fe80::3697:f6ff:fe32:8d08]:21658
- dist.init_process_group('ucc', rank=comm_rank, world_size=comm_size) + dist.init_process_group('nccl', rank=comm_rank, world_size=comm_size)
bash start_test.sh torch_allreduce_test.py --backend ucc --use-cuda
I will get wrong results:
Allreduce test count result failed on rank 0 failed on rank 1 1 Failed
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Failure 1
Wrong results, segfault at exit
Failure 2
Wrong results
Failure 3
If I change the
torch_ucc_test_setup.py
like thisand run
bash start_test.sh torch_allreduce_test.py --backend ucc # on CPU
I will get
Failure 4
If I change the
torch_ucc_test_setup.py
like thisand run
I will get wrong results:
The text was updated successfully, but these errors were encountered: