[NCCL][Test Only] extra group

[mingzhe09088]

Stack from ghstack:

• [NCCL][Test Only] extra group #45363 [NCCL][Test Only] extra group
• [NCCL][Test Only] test send/recv on OSS #45140 [NCCL][Test Only] test send/recv on OSS
• [NCCL] create NCCL communicator for send/recv on demand #44922 [NCCL] create NCCL communicator for send/recv on demand
• [NCCL] Support NCCL Send/Recv #44921 [NCCL] Support NCCL Send/Recv

Differential Revision: D23943473

[dr-ci]

💊 CI failures summary and remediations

As of commit 40e9a63 (more details on the Dr. CI page):

---

• 5/5 failures possibly* introduced in this PR
  • 1/5 non-CircleCI failure(s)

---

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages:

pytorch_macos_10_13_py3_test (1/1)

Step: "Test" (full log | diagnosis details | 🔁 rerun)

Sep 26 02:02:25 [E request_callback_no_python.cpp:618] Received error while processing request type 2: RuntimeError: Can not pickle torch.futures.Future

Sep 26 02:02:25 At: 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(94): serialize 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(146): serialize 
Sep 26 02:02:25  
Sep 26 02:02:25 [E request_callback_no_python.cpp:618] Received error while processing request type 2: RuntimeError: Can not pickle torch.futures.Future 
Sep 26 02:02:25  
Sep 26 02:02:25 At: 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(94): serialize 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(146): serialize 
Sep 26 02:02:25  
Sep 26 02:02:25 [E request_callback_no_python.cpp:618] Received error while processing request type 2: RuntimeError: Can not pickle torch.futures.Future 
Sep 26 02:02:25  
Sep 26 02:02:25 At: 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(94): serialize 
Sep 26 02:02:25   /Users/distiller/workspace/miniconda3/lib/python3.7/site-packages/torch/distributed/rpc/internal.py(146): serialize 
Sep 26 02:02:25  
Sep 26 02:02:26 ok (1.448s) 
Sep 26 02:02:27   test_return_future_remote (__main__.ProcessGroupRpcTestWithSpawn) ... RPC was initialized with the PROCESS_GROUP backend which is deprecated and slated to be removed and superseded by the TENSORPIPE backend. It is recommended to migrate to the TENSORPIPE backend. 
Sep 26 02:02:27 RPC was initialized with the PROCESS_GROUP backend which is deprecated and slated to be removed and superseded by the TENSORPIPE backend. It is recommended to migrate to the TENSORPIPE backend. 
Sep 26 02:02:27 RPC was initialized with the PROCESS_GROUP backend which is deprecated and slated to be removed and superseded by the TENSORPIPE backend. It is recommended to migrate to the TENSORPIPE backend. 
Sep 26 02:02:27 RPC was initialized with the PROCESS_GROUP backend which is deprecated and slated to be removed and superseded by the TENSORPIPE backend. It is recommended to migrate to the TENSORPIPE backend. 

---

3 jobs timed out:

• pytorch_linux_xenial_cuda10_2_cudnn7_py3_ge_config_legacy_test
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_ge_config_profiling_test
• pytorch_linux_xenial_cuda10_2_cudnn7_py3_gcc7_test

---

Extra GitHub checks: 1 failed

• Failed: GitHub Actions - flake8-py3

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group.

See how this bot performed.

This comment has been revised 7 times.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.