🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/103061

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ 3 Unrelated Failures

As of commit 73f11dd:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@BowenBao PTAL

@pytorchbot merge

Merge failed

Reason: HTTP Error 403: rate limit exceeded

@pytorchbot merge

Merge failed

Reason: HTTP Error 403: rate limit exceeded

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

• pull / linux-bionic-cuda12.1-py3.10-gcc9 / test (deploy, 1, 1, linux.4xlarge.nvidia.gpu)

Dig deeper by viewing the failures on hud

@BowenBao @justinchuby Do you guys know why CI fails? I have rebased couple times, but it seems this PR makes the test fail...

Looks like some sort of pip install issue with

2023-06-13T23:38:03.9703008Z no such option: --install-option

I wonder if it's related to onnx-script version bump.

Looks like a pip issue needed to be fixed on CI machine:

Previous PRs CI log:

WARNING: Implying --no-binary=:all: due to the presence of --build-option / --global-option / --install-option. Consider using --config-settings for more flexibility.
DEPRECATION: --install-option is deprecated because it forces pip to use the 'setup.py install' command which is itself deprecated. pip 23.1 will enforce this behaviour change. A possible replacement is to use --config-settings. Discussion can be found at https://github.com/pypa/pip/issues/11358
DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453

@huydhn Could you help look into this CI failure?
It seems that the pip version doesn't allow --install-option on CI machine.

pip install -e . --install-option="--cudatests"

in .ci/pytorch/common_utils.sh

Same observation, strange though, I thought pip version should be consistent as it is controlled by the docker image.

Triggered a rerun of the failed test.

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

• pull / linux-focal-py3.9-clang7-asan / build

Dig deeper by viewing the failures on hud

@huydhn Could you help look into this CI failure? It seems that the pip version doesn't allow --install-option on CI machine.

pip install -e . --install-option="--cudatests"

in .ci/pytorch/common_utils.sh

Sorry that I missed your message. I also stumped upon this issue yesterday and had created an issue for that on multipy pytorch/multipy#322. In the meantime, I have mark this job as unstable #103654, so you can safely ignore the failure and merge the change as usual.

The ASAN docker build failure looks flaky, so I will retry it.

@huydhn Could you help look into this CI failure? It seems that the pip version doesn't allow --install-option on CI machine.

pip install -e . --install-option="--cudatests"

in .ci/pytorch/common_utils.sh

Sorry that I missed your message. I also stumped upon this issue yesterday and had created an issue for that on multipy pytorch/multipy#322. In the meantime, I have mark this job as unstable #103654, so you can safely ignore the failure and merge the change as usual.

The ASAN docker build failure looks flaky, so I will retry it.

Thanks!!

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team