Skip to content
New issue

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

model_dump: Fix memory computation when both constants and data tensors are present #66006

Closed
wants to merge 1 commit into from

Conversation

dreiss
Copy link
Contributor

@dreiss dreiss commented Oct 1, 2021

…rs are present

Previously, this was resulting in a key collision and a crash.

Differential Revision: [D31281092](https://our.internmc.facebook.com/intern/diff/D31281092/)

[ghstack-poisoned]
@pytorch-probot
Copy link

pytorch-probot bot commented Oct 1, 2021

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/pytorch/pytorch/blob/c805a1ab0b1ab864481dd439c758c60c1cbdaf93/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default

Workflows Labels (bold enabled) Status
Triggered Workflows
linux-bionic-py3.6-clang9 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux, ciflow/noarch, ciflow/xla ✅ triggered
linux-xenial-cuda11.3-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/default, ciflow/linux ✅ triggered
linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/default, ciflow/linux ✅ triggered
linux-xenial-py3.6-gcc7-bazel-test ciflow/all, ciflow/bazel, ciflow/cpu, ciflow/default, ciflow/linux ✅ triggered
win-vs2019-cpu-py3 ciflow/all, ciflow/cpu, ciflow/default, ciflow/win ✅ triggered
win-vs2019-cuda11.3-py3 ciflow/all, ciflow/cuda, ciflow/default, ciflow/win ✅ triggered
Skipped Workflows
libtorch-linux-xenial-cuda10.2-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux 🚫 skipped
libtorch-linux-xenial-cuda11.3-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux 🚫 skipped
linux-bionic-cuda10.2-py3.9-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow 🚫 skipped
linux-xenial-cuda10.2-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/slow 🚫 skipped
parallelnative-linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux 🚫 skipped
periodic-libtorch-linux-xenial-cuda11.1-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/libtorch, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-linux-xenial-cuda11.1-py3.6-gcc7 ciflow/all, ciflow/cuda, ciflow/linux, ciflow/scheduled 🚫 skipped
periodic-win-vs2019-cuda11.1-py3 ciflow/all, ciflow/cuda, ciflow/scheduled, ciflow/win 🚫 skipped
puretorch-linux-xenial-py3.6-gcc5.4 ciflow/all, ciflow/cpu, ciflow/linux 🚫 skipped

You can add a comment to the PR and tag @pytorchbot with the following commands:
# ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun

# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow

For more information, please take a look at the CI Flow Wiki.

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Oct 1, 2021

🔗 Helpful links

💊 CI failures summary and remediations

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



🕵️ 4 new failures recognized by patterns

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

See GitHub Actions build linux-bionic-py3.6-clang9 / test (default, 2, 2, linux.2xlarge) (1/4)

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

2021-10-01T17:11:05.8503236Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:05.8105878Z 
2021-10-01T17:11:05.8106784Z Intel MKL ERROR: Parameter 4 was incorrect on entry to SLASCL.
2021-10-01T17:11:05.8155606Z ok (0.039s)
2021-10-01T17:11:05.8319667Z   test_svd_errors_and_warnings_cpu_float64 (__main__.TestLinalgCPU) ... 
2021-10-01T17:11:05.8321168Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:05.8322312Z 
2021-10-01T17:11:05.8323268Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:05.8500194Z 
2021-10-01T17:11:05.8501490Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:05.8502268Z 
2021-10-01T17:11:05.8503236Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:05.8552356Z ok (0.040s)
2021-10-01T17:11:09.1520988Z   test_svd_lowrank_cpu_float64 (__main__.TestLinalgCPU) ... ok (3.297s)
2021-10-01T17:11:09.6017919Z   test_svd_memory_allocation_cpu_complex128 (__main__.TestLinalgCPU) ... test_linalg.py:3019: UserWarning: An output with one or more elements was resized since it had shape [3, 3], which does not match the required output shape [3].This behavior is deprecated, and in a future PyTorch release outputs will not be resized unless they have zero elements. You can explicitly reuse an out tensor t by resizing it, inplace, to zero elements with t.resize_(0). (Triggered internally at  /var/lib/jenkins/workspace/aten/src/ATen/native/Resize.cpp:23.)
2021-10-01T17:11:09.6021086Z   torch.linalg.svdvals(a, out=out0)
2021-10-01T17:11:09.7878746Z test_linalg.py:3020: UserWarning: An output with one or more elements was resized since it had shape [3], which does not match the required output shape [3, 3].This behavior is deprecated, and in a future PyTorch release outputs will not be resized unless they have zero elements. You can explicitly reuse an out tensor t by resizing it, inplace, to zero elements with t.resize_(0). (Triggered internally at  /var/lib/jenkins/workspace/aten/src/ATen/native/Resize.cpp:23.)
2021-10-01T17:11:09.7881779Z   torch.linalg.svd(a, full_matrices=False, out=(out0, out1, out2))
2021-10-01T17:11:09.7914166Z ok (0.639s)
2021-10-01T17:11:10.1239552Z   test_svd_memory_allocation_cpu_complex64 (__main__.TestLinalgCPU) ... ok (0.332s)
2021-10-01T17:11:10.2677487Z   test_svd_memory_allocation_cpu_float32 (__main__.TestLinalgCPU) ... ok (0.144s)
2021-10-01T17:11:10.4753853Z   test_svd_memory_allocation_cpu_float64 (__main__.TestLinalgCPU) ... ok (0.208s)

See GitHub Actions build linux-xenial-py3.6-gcc5.4 / test (distributed, 1, 1, linux.2xlarge) (2/4)

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

2021-10-01T17:13:04.1931190Z test_udf_remote_...yUniqueId(created_on=0, local_id=0) to be created.
2021-10-01T17:12:25.3642273Z frame #12: c10::ThreadPool::main_loop(unsigned long) + 0x2a3 (0x7f66a54f1e93 in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
2021-10-01T17:12:25.3643677Z frame #13: <unknown function> + 0xc92bd (0x7f66a54202bd in /opt/conda/lib/libstdc++.so.6)
2021-10-01T17:12:25.3645139Z frame #14: <unknown function> + 0x76ba (0x7f66ba7ef6ba in /lib/x86_64-linux-gnu/libpthread.so.0)
2021-10-01T17:12:25.3646468Z frame #15: clone + 0x6d (0x7f66ba52551d in /lib/x86_64-linux-gnu/libc.so.6)
2021-10-01T17:12:25.3647045Z 
2021-10-01T17:12:25.5863141Z ok (3.316s)
2021-10-01T17:12:40.4203480Z   test_rpc_builtin_timeout (__main__.FaultyFaultyAgentRpcTest) ... ok (14.834s)
2021-10-01T17:12:49.3456876Z   test_rpc_script_timeout (__main__.FaultyFaultyAgentRpcTest) ... ok (8.925s)
2021-10-01T17:12:52.7622338Z   test_rref_to_here_timeout (__main__.FaultyFaultyAgentRpcTest) ... ok (3.417s)
2021-10-01T17:13:00.0840784Z   test_udf_remote_message_delay_timeout (__main__.FaultyFaultyAgentRpcTest) ... ok (7.322s)
2021-10-01T17:13:04.1931190Z   test_udf_remote_message_delay_timeout_to_self (__main__.FaultyFaultyAgentRpcTest) ... [E request_callback_no_python.cpp:559] Received error while processing request type 261: falseINTERNAL ASSERT FAILED at "/var/lib/jenkins/workspace/torch/csrc/distributed/rpc/rref_context.cpp":387, please report a bug to PyTorch. Expected OwnerRRef with id GloballyUniqueId(created_on=0, local_id=0) to be created.
2021-10-01T17:13:04.1933411Z Exception raised from getOwnerRRef at /var/lib/jenkins/workspace/torch/csrc/distributed/rpc/rref_context.cpp:387 (most recent call first):
2021-10-01T17:13:04.1935911Z frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x69 (0x7fc92c1e3059 in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
2021-10-01T17:13:04.1938397Z frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0xd2 (0x7fc92c1df602 in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
2021-10-01T17:13:04.1941033Z frame #2: c10::detail::torchInternalAssertFail(char const*, char const*, unsigned int, char const*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0x4e (0x7fc92c1e0f9e in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
2021-10-01T17:13:04.1943723Z frame #3: torch::distributed::rpc::RRefContext::getOwnerRRef(torch::distributed::rpc::GloballyUniqueId const&, bool) + 0x4a4 (0x7fc93043e114 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_cpu.so)
2021-10-01T17:13:04.1946645Z frame #4: torch::distributed::rpc::RequestCallbackNoPython::assignOwnerRRef(torch::distributed::rpc::GloballyUniqueId const&, torch::distributed::rpc::GloballyUniqueId const&, c10::intrusive_ptr<c10::ivalue::Future, c10::detail::intrusive_target_default_null_type<c10::ivalue::Future> >) const + 0x71 (0x7fc93042e471 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_cpu.so)
2021-10-01T17:13:04.1949467Z frame #5: torch::distributed::rpc::RequestCallbackImpl::processPythonRemoteCall(torch::distributed::rpc::RpcCommandBase&, std::vector<c10::Stream, std::allocator<c10::Stream> >) const + 0xc8 (0x7fc9388980f8 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)
2021-10-01T17:13:04.1951823Z frame #6: torch::distributed::rpc::RequestCallbackNoPython::processRpc(torch::distributed::rpc::RpcCommandBase&, torch::distributed::rpc::MessageType const&, std::vector<c10::Stream, std::allocator<c10::Stream> >) const + 0x194 (0x7fc930432cc4 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_cpu.so)
2021-10-01T17:13:04.1954255Z frame #7: torch::distributed::rpc::RequestCallbackImpl::processRpcWithErrors(torch::distributed::rpc::RpcCommandBase&, torch::distributed::rpc::MessageType const&, std::vector<c10::Stream, std::allocator<c10::Stream> >) const + 0x65 (0x7fc9388976f5 in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)
2021-10-01T17:13:04.1963548Z frame #8: <unknown function> + 0x401281a (0x7fc93042f81a in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_cpu.so)

See GitHub Actions build linux-bionic-py3.6-clang9 / test (noarch, 1, 1, linux.2xlarge) (3/4)

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

2021-10-01T17:11:13.4924857Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:13.4529185Z 
2021-10-01T17:11:13.4530097Z Intel MKL ERROR: Parameter 4 was incorrect on entry to SLASCL.
2021-10-01T17:11:13.4578775Z ok (0.039s)
2021-10-01T17:11:13.4740451Z   test_svd_errors_and_warnings_cpu_float64 (__main__.TestLinalgCPU) ... 
2021-10-01T17:11:13.4741941Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:13.4742750Z 
2021-10-01T17:11:13.4743915Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:13.4922698Z 
2021-10-01T17:11:13.4923579Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:13.4924163Z 
2021-10-01T17:11:13.4924857Z Intel MKL ERROR: Parameter 4 was incorrect on entry to DLASCL.
2021-10-01T17:11:13.4975035Z ok (0.039s)
2021-10-01T17:11:16.8000077Z   test_svd_lowrank_cpu_float64 (__main__.TestLinalgCPU) ... ok (3.302s)
2021-10-01T17:11:17.2885236Z   test_svd_memory_allocation_cpu_complex128 (__main__.TestLinalgCPU) ... test_linalg.py:3019: UserWarning: An output with one or more elements was resized since it had shape [3, 3], which does not match the required output shape [3].This behavior is deprecated, and in a future PyTorch release outputs will not be resized unless they have zero elements. You can explicitly reuse an out tensor t by resizing it, inplace, to zero elements with t.resize_(0). (Triggered internally at  /var/lib/jenkins/workspace/aten/src/ATen/native/Resize.cpp:23.)
2021-10-01T17:11:17.2888390Z   torch.linalg.svdvals(a, out=out0)
2021-10-01T17:11:17.4680874Z test_linalg.py:3020: UserWarning: An output with one or more elements was resized since it had shape [3], which does not match the required output shape [3, 3].This behavior is deprecated, and in a future PyTorch release outputs will not be resized unless they have zero elements. You can explicitly reuse an out tensor t by resizing it, inplace, to zero elements with t.resize_(0). (Triggered internally at  /var/lib/jenkins/workspace/aten/src/ATen/native/Resize.cpp:23.)
2021-10-01T17:11:17.4683913Z   torch.linalg.svd(a, full_matrices=False, out=(out0, out1, out2))
2021-10-01T17:11:17.4757157Z ok (0.676s)
2021-10-01T17:11:17.8118540Z   test_svd_memory_allocation_cpu_complex64 (__main__.TestLinalgCPU) ... ok (0.336s)
2021-10-01T17:11:17.9661003Z   test_svd_memory_allocation_cpu_float32 (__main__.TestLinalgCPU) ... ok (0.154s)
2021-10-01T17:11:18.1680012Z   test_svd_memory_allocation_cpu_float64 (__main__.TestLinalgCPU) ... ok (0.202s)

See GitHub Actions build linux-xenial-py3.6-gcc7-bazel-test / build-and-test (4/4)

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

2021-10-01T17:01:22.9145120Z ModuleNotFoundError: No module named 'boto3'
2021-10-01T17:01:22.9137113Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/upload_binary_size_to_scuba.py", line 155, in <module>
2021-10-01T17:01:22.9137914Z     register_rds_schema("binary_size", schema_from_sample(sample_data))
2021-10-01T17:01:22.9138824Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/scribe.py", line 94, in register_rds_schema
2021-10-01T17:01:22.9139474Z     invoke_rds(event)
2021-10-01T17:01:22.9140221Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/scribe.py", line 72, in invoke_rds
2021-10-01T17:01:22.9141289Z     return invoke_lambda("rds-proxy", events)
2021-10-01T17:01:22.9142100Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/scribe.py", line 30, in invoke_lambda
2021-10-01T17:01:22.9142920Z     res = aws_lambda().invoke(FunctionName=name, Payload=json.dumps(payload).encode())
2021-10-01T17:01:22.9143863Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/scribe.py", line 21, in aws_lambda
2021-10-01T17:01:22.9144503Z     import boto3  # type: ignore[import]
2021-10-01T17:01:22.9145120Z ModuleNotFoundError: No module named 'boto3'
2021-10-01T17:01:22.9216821Z ##[group]Run # detached container should get cleaned up by teardown_ec2_linux
2021-10-01T17:01:22.9217638Z �[36;1m# detached container should get cleaned up by teardown_ec2_linux�[0m
2021-10-01T17:01:22.9218181Z �[36;1mexport SHARD_NUMBER=0�[0m
2021-10-01T17:01:22.9218678Z �[36;1m# TODO: Stop building test binaries as part of the build phase�[0m
2021-10-01T17:01:22.9219314Z �[36;1m# Make sure we copy test results from bazel-testlogs symlink to�[0m
2021-10-01T17:01:22.9219906Z �[36;1m# a regular directory ./test/test-reports�[0m
2021-10-01T17:01:22.9220669Z �[36;1mcontainer_name=$(docker run \�[0m
2021-10-01T17:01:22.9221108Z �[36;1m  -e BUILD_ENVIRONMENT \�[0m
2021-10-01T17:01:22.9221559Z �[36;1m  -e CUSTOM_TEST_ARTIFACT_BUILD_DIR \�[0m
2021-10-01T17:01:22.9221967Z �[36;1m  -e GITHUB_ACTIONS \�[0m

3 failures not recognized by patterns:

Job Step Action
GitHub Actions linux-bionic-py3.6-clang9 / test (default, 1, 2, linux.2xlarge) Unknown 🔁 rerun
GitHub Actions linux-xenial-py3.6-gcc5.4 / test (default, 1, 2, linux.2xlarge) Unknown 🔁 rerun
GitHub Actions linux-xenial-py3.6-gcc5.4 / test (default, 2, 2, linux.2xlarge) Unknown 🔁 rerun

❄️ 3 failures tentatively classified as flaky

but reruns have not yet been triggered to confirm:

See GitHub Actions build linux-xenial-py3.6-gcc5.4 / build-docs (cpp) (1/3)

Step: "Build cpp docs" (full log | diagnosis details | 🔁 rerun) ❄️

2021-10-01T17:07:19.6888195Z E: Failed to fetch...: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2021-10-01T17:07:19.6472633Z 
2021-10-01T17:07:19.6472967Z Reading package lists... 99%
2021-10-01T17:07:19.6473202Z 
2021-10-01T17:07:19.6660247Z Reading package lists... 99%
2021-10-01T17:07:19.6660615Z 
2021-10-01T17:07:19.6660932Z Reading package lists... Done
2021-10-01T17:07:19.6661179Z 
2021-10-01T17:07:19.6884757Z W: The repository 'https://deb.nodesource.com/node_12.x xenial Release' does not have a Release file.
2021-10-01T17:07:19.6885904Z N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
2021-10-01T17:07:19.6886810Z N: See apt-secure(8) manpage for repository creation and user configuration details.
2021-10-01T17:07:19.6888195Z E: Failed to fetch https://deb.nodesource.com/node_12.x/dists/xenial/main/source/Sources  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2021-10-01T17:07:19.6889291Z E: Some index files failed to download. They have been ignored, or old ones used instead.
2021-10-01T17:07:19.6962271Z 
2021-10-01T17:07:19.7399942Z Reading package lists... 0%
2021-10-01T17:07:19.7400469Z 
2021-10-01T17:07:19.7504951Z Reading package lists... 0%
2021-10-01T17:07:19.7505797Z 
2021-10-01T17:07:19.7955197Z Reading package lists... 1%
2021-10-01T17:07:19.7955519Z 
2021-10-01T17:07:19.7955911Z Reading package lists... 8%
2021-10-01T17:07:19.7956148Z 

See GitHub Actions build linux-xenial-py3.6-gcc5.4 / build-docs (python) (2/3)

Step: "Unknown" (full log | diagnosis details | 🔁 rerun) ❄️

2021-10-01T17:07:20.9876318Z E: Failed to fetch...: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2021-10-01T17:07:20.9446690Z 
2021-10-01T17:07:20.9447032Z Reading package lists... 99%
2021-10-01T17:07:20.9447288Z 
2021-10-01T17:07:20.9640281Z Reading package lists... 99%
2021-10-01T17:07:20.9640603Z 
2021-10-01T17:07:20.9640932Z Reading package lists... Done
2021-10-01T17:07:20.9641190Z 
2021-10-01T17:07:20.9872594Z W: The repository 'https://deb.nodesource.com/node_12.x xenial Release' does not have a Release file.
2021-10-01T17:07:20.9873839Z N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
2021-10-01T17:07:20.9874866Z N: See apt-secure(8) manpage for repository creation and user configuration details.
2021-10-01T17:07:20.9876318Z E: Failed to fetch https://deb.nodesource.com/node_12.x/dists/xenial/main/source/Sources  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
2021-10-01T17:07:20.9877600Z E: Some index files failed to download. They have been ignored, or old ones used instead.
2021-10-01T17:07:20.9951322Z 
2021-10-01T17:07:21.0386744Z Reading package lists... 0%
2021-10-01T17:07:21.0387274Z 
2021-10-01T17:07:21.0491940Z Reading package lists... 0%
2021-10-01T17:07:21.0492461Z 
2021-10-01T17:07:21.0941397Z Reading package lists... 1%
2021-10-01T17:07:21.0941922Z 
2021-10-01T17:07:21.0942474Z Reading package lists... 8%
2021-10-01T17:07:21.0942917Z 

See CircleCI build pytorch_linux_xenial_py3_6_gcc5_4_test (3/3)

Step: "Check for no AVX instruction by default" (full log | diagnosis details | 🔁 rerun) ❄️

E: Failed to fetch https://deb.nodesource.com/n...: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign:11 https://deb.nodesource.com/node_12.x xenial/main Sources
Ign:16 https://deb.nodesource.com/node_12.x xenial/main amd64 Packages
Ign:14 https://deb.nodesource.com/node_12.x xenial/main all Packages
Err:11 https://deb.nodesource.com/node_12.x xenial/main Sources
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Ign:16 https://deb.nodesource.com/node_12.x xenial/main amd64 Packages
Ign:14 https://deb.nodesource.com/node_12.x xenial/main all Packages
Fetched 4466 kB in 4s (1099 kB/s)
Reading package lists...
W: The repository 'https://deb.nodesource.com/node_12.x xenial Release' does not have a Release file.
E: Failed to fetch https://deb.nodesource.com/node_12.x/dists/xenial/main/source/Sources  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
E: Some index files failed to download. They have been ignored, or old ones used instead.


Exited with code exit status 100


🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is older than viable/strict, run these commands:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

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 to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

dreiss added a commit that referenced this pull request Oct 1, 2021
…rs are present

Previously, this was resulting in a key collision and a crash.

Differential Revision: [D31281092](https://our.internmc.facebook.com/intern/diff/D31281092/)

ghstack-source-id: 139342089
Pull Request resolved: #66006
@facebook-github-bot facebook-github-bot deleted the gh/dreiss/112/head branch October 5, 2021 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants