Skip to content

Conversation

NicolasHug
Copy link
Member

This will let GitHub's blame know that it should ignore some pure-formatting PRs, thus reducing the noise in the blame.

See https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view for details

@NicolasHug NicolasHug added module: ci other if you have no clue or if you will manually handle the PR in the release notes labels Mar 28, 2022
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 28, 2022

💊 CI failures summary and remediations

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



🕵️ 9 new failures recognized by patterns

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

See CircleCI build unittest_linux_gpu_py3.8 (1/9)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
Using CUDA 10.2 as determined by CU_VERSION

Installing PyTorch with nvidia::cudatoolkit=10.2

Collecting package metadata (current_repodata.json): - ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��failed



CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch-nightly/linux-64/repodata.json>

Elapsed: 00:06.520081

CF-RAY: 6f30ea7e7cf086de-ORD



A remote server error occurred when trying to retrieve this URL.



A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to

fulfill a valid request.  The problem may be spurious, and will resolve itself if you

try your request again.  If the problem persists, consider notifying the maintainer

of the remote server.







Exited with code exit status 1

See CircleCI build binary_linux_conda_py3.10_cpu (2/9)

Step: "packaging/build_conda.sh" (full log | diagnosis details | 🔁 rerun)

raise error
    cmd(state, arg)
  File "/opt/conda/lib/python3.9/site-packages/conda/instructions.py", line 73, in UNLINKLINKTRANSACTION_CMD
    unlink_link_transaction.execute()
  File "/opt/conda/lib/python3.9/site-packages/conda/core/link.py", line 277, in execute
    self.verify()
  File "/opt/conda/lib/python3.9/site-packages/conda/common/io.py", line 88, in decorated
    return f(*args, **kwds)
  File "/opt/conda/lib/python3.9/site-packages/conda/core/link.py", line 241, in verify
    maybe_raise(CondaMultiError(exceptions), context)
  File "/opt/conda/lib/python3.9/site-packages/conda/exceptions.py", line 1022, in maybe_raise
    raise error
conda.CondaMultiError: The package for python located at /opt/conda/pkgs/python-3.10.3-h12debd9_5
appears to be corrupted. The path 'lib/python3.1'
specified in the package manifest cannot be found.




Exited with code exit status 1

See CircleCI build binary_linux_conda_py3.8_cpu (3/9)

Step: "packaging/build_conda.sh" (full log | diagnosis details | 🔁 rerun)

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
  File "/opt/conda/lib/python3.9/site-packages/conda/core/subdir_data.py", line 375, in _load
    raw_repodata_str = fetch_repodata_remote_request(
  File "/opt/conda/lib/python3.9/site-packages/conda/core/subdir_data.py", line 806, in fetch_repodata_remote_request
    raise CondaHTTPError(help_message,
conda.exceptions.CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch/linux-64/repodata.json>
Elapsed: 00:06.222560
CF-RAY: 6f30e2af8b2a8215-IAD

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.



Exited with code exit status 1

See CircleCI build binary_linux_conda_py3.10_cu102 (4/9)

Step: "packaging/build_conda.sh" (full log | diagnosis details | 🔁 rerun)

raise error
    cmd(state, arg)
  File "/opt/conda/lib/python3.9/site-packages/conda/instructions.py", line 73, in UNLINKLINKTRANSACTION_CMD
    unlink_link_transaction.execute()
  File "/opt/conda/lib/python3.9/site-packages/conda/core/link.py", line 277, in execute
    self.verify()
  File "/opt/conda/lib/python3.9/site-packages/conda/common/io.py", line 88, in decorated
    return f(*args, **kwds)
  File "/opt/conda/lib/python3.9/site-packages/conda/core/link.py", line 241, in verify
    maybe_raise(CondaMultiError(exceptions), context)
  File "/opt/conda/lib/python3.9/site-packages/conda/exceptions.py", line 1022, in maybe_raise
    raise error
conda.CondaMultiError: The package for python located at /opt/conda/pkgs/python-3.10.3-h12debd9_5
appears to be corrupted. The path 'lib/python3.1'
specified in the package manifest cannot be found.




Exited with code exit status 1

See CircleCI build cmake_linux_cpu (5/9)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to

* Installing dependencies (except PyTorch)
Collecting package metadata (current_repodata.json): - ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��failed

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch/noarch/repodata.json>
Elapsed: 00:06.330967
CF-RAY: 6f30e3068ef85dc8-IAD

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.




Exited with code exit status 1

See CircleCI build unittest_windows_cpu_py3.8 (6/9)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
+ export PATH
+ /c/Users/circleci/project/conda/Scripts/conda.exe install -y -c pytorch-nightly -c nvidia 'pytorch-nightly::pytorch[build=*cpu*]' cpuonly pytest
Collecting package metadata (current_repodata.json): ...working... failed

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch-nightly/noarch/repodata.json>
Elapsed: 00:06.556264
CF-RAY: 6f30e70ac9422d3d-ORD

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.


+ return


Exited with code exit status 1

See CircleCI build unittest_windows_cpu_py3.9 (7/9)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
+ export PATH
+ /c/Users/circleci/project/conda/Scripts/conda.exe install -y -c pytorch-nightly -c nvidia 'pytorch-nightly::pytorch[build=*cpu*]' cpuonly pytest
Collecting package metadata (current_repodata.json): ...working... failed

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/nvidia/noarch/repodata.json>
Elapsed: 00:06.878762
CF-RAY: 6f30e3d2ab40297a-ORD

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.


+ return


Exited with code exit status 1

See CircleCI build binary_macos_conda_py3.10_cpu (8/9)

Step: "curl -o conda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
sh conda.sh -b
source $HOME/miniconda3/bin/activate
conda install -yq conda-build
packaging/build_conda.sh
" (full log | diagnosis details | 🔁 rerun)

raise error
    cmd(state, arg)
  File "/Users/distiller/miniconda3/lib/python3.9/site-packages/conda/instructions.py", line 73, in UNLINKLINKTRANSACTION_CMD
    unlink_link_transaction.execute()
  File "/Users/distiller/miniconda3/lib/python3.9/site-packages/conda/core/link.py", line 277, in execute
    self.verify()
  File "/Users/distiller/miniconda3/lib/python3.9/site-packages/conda/common/io.py", line 88, in decorated
    return f(*args, **kwds)
  File "/Users/distiller/miniconda3/lib/python3.9/site-packages/conda/core/link.py", line 241, in verify
    maybe_raise(CondaMultiError(exceptions), context)
  File "/Users/distiller/miniconda3/lib/python3.9/site-packages/conda/exceptions.py", line 1022, in maybe_raise
    raise error
conda.CondaMultiError: The package for python located at /Users/distiller/miniconda3/pkgs/python-3.10.3-hdfd78df_5
appears to be corrupted. The path 'lib/python3.1'
specified in the package manifest cannot be found.




Exited with code exit status 1

See CircleCI build binary_linux_conda_py3.10_cu113 (9/9)

Step: "packaging/build_conda.sh" (full log | diagnosis details | 🔁 rerun)

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
  File "/opt/conda/lib/python3.9/site-packages/conda/core/subdir_data.py", line 375, in _load
    raw_repodata_str = fetch_repodata_remote_request(
  File "/opt/conda/lib/python3.9/site-packages/conda/core/subdir_data.py", line 806, in fetch_repodata_remote_request
    raise CondaHTTPError(help_message,
conda.exceptions.CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/nvidia/noarch/repodata.json>
Elapsed: 00:06.282863
CF-RAY: 6f30e3f67f785a8e-IAD

A remote server error occurred when trying to retrieve this URL.

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
fulfill a valid request.  The problem may be spurious, and will resolve itself if you
try your request again.  If the problem persists, consider notifying the maintainer
of the remote server.



Exited with code exit status 1


11 failures not recognized by patterns:

Job Step Action
CircleCI binary_macos_wheel_py3.10_cpu curl -o conda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
sh conda.sh -b
source $HOME/miniconda3/bin/activate
packaging/build_wheel.sh
🔁 rerun
CircleCI binary_macos_conda_py3.9_cpu curl -o conda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
sh conda.sh -b
source $HOME/miniconda3/bin/activate
conda install -yq conda-build
packaging/build_conda.sh
🔁 rerun
CircleCI binary_linux_conda_py3.7_cu102 packaging/build_conda.sh 🔁 rerun
CircleCI binary_linux_conda_py3.9_cu113 packaging/build_conda.sh 🔁 rerun
CircleCI unittest_macos_cpu_py3.10 Setup 🔁 rerun
CircleCI cmake_windows_cpu set -ex
source packaging/windows/internal/vc_install_helper.sh
packaging/build_cmake.sh
🔁 rerun
CircleCI cmake_macos_cpu curl -o conda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
sh conda.sh -b
source $HOME/miniconda3/bin/activate
conda install -yq conda-build cmake
packaging/build_cmake.sh
🔁 rerun
CircleCI binary_linux_conda_py3.7_cu113 packaging/build_conda.sh 🔁 rerun
CircleCI unittest_linux_cpu_py3.10 Setup 🔁 rerun
CircleCI binary_linux_conda_py3.9_cpu packaging/build_conda.sh 🔁 rerun
CircleCI binary_macos_conda_py3.7_cpu curl -o conda.sh https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh
sh conda.sh -b
source $HOME/miniconda3/bin/activate
conda install -yq conda-build
packaging/build_conda.sh
🔁 rerun

🚧 6 ongoing upstream failures:

These were probably caused by upstream breakages that are not fixed yet.

🚧 2 fixed upstream failures:

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).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

Copy link
Collaborator

@pmeier pmeier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks a lot @NicolasHug! If we ever get to it, the commit created from #5106 also needs to into this list.

@NicolasHug NicolasHug merged commit b031e91 into pytorch:main Mar 28, 2022
facebook-github-bot pushed a commit that referenced this pull request Apr 5, 2022
… blame (#5696)

Summary: (Note: this ignores all push blocking failures!)

Reviewed By: YosuaMichael

Differential Revision: D35216785

fbshipit-source-id: f1c2fcd69090b427dfc560cc4a5eccbca6095cf6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla signed module: ci other if you have no clue or if you will manually handle the PR in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants