Skip to content

Conversation

datumbox
Copy link
Contributor

Adding the missing _log_api_usage_once() call on generalized_box_iou_loss()

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Mar 28, 2022

💊 CI failures summary and remediations

As of commit 1285dcc (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 CircleCI build unittest_macos_cpu_py3.9 (1/4)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
Installing PyTorch with cpuonly
Collecting package metadata (current_repodata.json): - ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��failed

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch-nightly/noarch/repodata.json>
Elapsed: 00:06.620751
CF-RAY: 6f2ff54589452c05-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 build_docs (2/4)

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

A 500-type error (e.g. 500, 501, 502, 503, etc.) indicates the server failed to
Installing PyTorch with cpuonly
Collecting package metadata (current_repodata.json): - ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��\ ��| ��/ ��- ��failed

CondaHTTPError: HTTP 500 INTERNAL SERVER ERROR for url <https://conda.anaconda.org/pytorch-nightly/noarch/repodata.json>
Elapsed: 00:06.270026
CF-RAY: 6f2ff7496b645ca1-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_cu115 (3/4)

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.237758
CF-RAY: 6f2ff54bddbb5ca1-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.9_cu115 (4/4)

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/noarch/repodata.json>
Elapsed: 00:06.217231
CF-RAY: 6f2ff5333b3d5740-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


7 failures not recognized by patterns:

Job Step Action
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 cmake_windows_cpu set -ex
source packaging/windows/internal/vc_install_helper.sh
packaging/build_cmake.sh
🔁 rerun
CircleCI binary_linux_conda_py3.8_cpu packaging/build_conda.sh 🔁 rerun
CircleCI binary_linux_conda_py3.10_cu113 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
CircleCI binary_linux_conda_py3.10_cu102 packaging/build_conda.sh 🔁 rerun
CircleCI binary_macos_conda_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
conda install -yq conda-build
packaging/build_conda.sh
🔁 rerun

🚧 3 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.

@datumbox datumbox merged commit 818dc22 into pytorch:main Mar 28, 2022
@datumbox datumbox deleted the log_call_giou branch March 28, 2022 11:14
facebook-github-bot pushed a commit that referenced this pull request Apr 5, 2022
Summary: (Note: this ignores all push blocking failures!)

Reviewed By: datumbox

Differential Revision: D35216798

fbshipit-source-id: 79a1faff5717e74a91a779340107cc752a04b5b4
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.

3 participants