Add new checks in CI system to verify the built linux pip wheel with cpu-cxx11-abi by zhuhong61 · Pull Request #79409 · pytorch/pytorch

zhuhong61 · 2022-06-13T09:33:25Z

We added the linux pip wheel with cpu-cxx11-abi in pytorch/builder, see: pytorch/builder#990 and pytorch/builder#1023

The purpose of this PR is to add new checks in pytorch CI system to verify the linux pip wheel with cpu-cxx11-abi.

Co-authored-by: Zhu Hong hong.zhu@intel.com
Co-authored-by: Guo Yejun yejun.guo@intel.com

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10

facebook-github-bot · 2022-06-13T09:33:31Z

🔗 Helpful links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/79409
✖️ Python docs build was skipped
✖️ C++ docs build was skipped
❓Need help or want to give feedback on the CI? Visit our office hours

❌ 5 New Failures, 3 Pending

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

Expand to see more

5/5 failures introduced in this PR

🕵️ 5 new failures recognized by patterns

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

linux-binary-manywheel / manywheel-py3_9-cpu-cxx11-abi-build / build (1/5)

Step: "Pull Docker image" (full log | diagnosis details)

2022-08-03T07:18:42.2969822Z ##[error]Process completed with exit code 1.

2022-08-03T07:18:39.0555269Z   BINARY_ENV_FILE: /tmp/env
2022-08-03T07:18:39.0555498Z   BUILD_ENVIRONMENT: linux-binary-manywheel
2022-08-03T07:18:39.0555814Z   GITHUB_TOKEN: ***
2022-08-03T07:18:39.0556036Z   PR_NUMBER: 
2022-08-03T07:18:39.0556221Z   PYTORCH_FINAL_PACKAGE_DIR: /artifacts
2022-08-03T07:18:39.0556457Z   SHA1: 30c8a2eb32dc38ff0d39612bf4ea58a2aa4ce3d9
2022-08-03T07:18:39.0556663Z ##[endgroup]
2022-08-03T07:18:39.1372806Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:40.2182808Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:42.2951051Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:42.2969822Z ##[error]Process completed with exit code 1.
2022-08-03T07:18:42.2991644Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-08-03T07:18:42.2991963Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-08-03T07:18:42.2992307Z �[36;1mdocker run --rm -v "${RUNNER_TEMP}/artifacts:/v" -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-03T07:18:42.3004109Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-03T07:18:42.3004327Z env:
2022-08-03T07:18:42.3004487Z   PYTORCH_ROOT: /pytorch
2022-08-03T07:18:42.3004679Z   BUILDER_ROOT: /builder
2022-08-03T07:18:42.3004866Z   PACKAGE_TYPE: manywheel
2022-08-03T07:18:42.3005054Z   DESIRED_CUDA: cpu-cxx11-abi
2022-08-03T07:18:42.3005247Z   GPU_ARCH_VERSION:

linux-binary-manywheel / manywheel-py3_11-cpu-cxx11-abi-build / build (2/5)

Step: "Pull Docker image" (full log | diagnosis details)

2022-08-03T07:17:36.7247985Z ##[error]Process completed with exit code 1.

2022-08-03T07:17:33.4754768Z   BINARY_ENV_FILE: /tmp/env
2022-08-03T07:17:33.4754989Z   BUILD_ENVIRONMENT: linux-binary-manywheel
2022-08-03T07:17:33.4755311Z   GITHUB_TOKEN: ***
2022-08-03T07:17:33.4755471Z   PR_NUMBER: 
2022-08-03T07:17:33.4755669Z   PYTORCH_FINAL_PACKAGE_DIR: /artifacts
2022-08-03T07:17:33.4756000Z   SHA1: 30c8a2eb32dc38ff0d39612bf4ea58a2aa4ce3d9
2022-08-03T07:17:33.4756197Z ##[endgroup]
2022-08-03T07:17:33.5529475Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:17:34.6390631Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:17:36.7228259Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:17:36.7247985Z ##[error]Process completed with exit code 1.
2022-08-03T07:17:36.7270222Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-08-03T07:17:36.7270566Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-08-03T07:17:36.7270919Z �[36;1mdocker run --rm -v "${RUNNER_TEMP}/artifacts:/v" -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-03T07:17:36.7282134Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-03T07:17:36.7282340Z env:
2022-08-03T07:17:36.7282516Z   PYTORCH_ROOT: /pytorch
2022-08-03T07:17:36.7282709Z   BUILDER_ROOT: /builder
2022-08-03T07:17:36.7282886Z   PACKAGE_TYPE: manywheel
2022-08-03T07:17:36.7283082Z   DESIRED_CUDA: cpu-cxx11-abi
2022-08-03T07:17:36.7283273Z   GPU_ARCH_VERSION:

linux-binary-manywheel / manywheel-py3_10-cpu-cxx11-abi-build / build (3/5)

Step: "Pull Docker image" (full log | diagnosis details)

2022-08-03T07:18:40.9796446Z ##[error]Process completed with exit code 1.

2022-08-03T07:18:37.7369138Z   BINARY_ENV_FILE: /tmp/env
2022-08-03T07:18:37.7369362Z   BUILD_ENVIRONMENT: linux-binary-manywheel
2022-08-03T07:18:37.7369688Z   GITHUB_TOKEN: ***
2022-08-03T07:18:37.7369862Z   PR_NUMBER: 
2022-08-03T07:18:37.7370045Z   PYTORCH_FINAL_PACKAGE_DIR: /artifacts
2022-08-03T07:18:37.7370284Z   SHA1: 30c8a2eb32dc38ff0d39612bf4ea58a2aa4ce3d9
2022-08-03T07:18:37.7370491Z ##[endgroup]
2022-08-03T07:18:37.8194856Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:38.8992536Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:40.9778105Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:40.9796446Z ##[error]Process completed with exit code 1.
2022-08-03T07:18:40.9817904Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-08-03T07:18:40.9818226Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-08-03T07:18:40.9818565Z �[36;1mdocker run --rm -v "${RUNNER_TEMP}/artifacts:/v" -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-03T07:18:40.9830062Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-03T07:18:40.9830278Z env:
2022-08-03T07:18:40.9830439Z   PYTORCH_ROOT: /pytorch
2022-08-03T07:18:40.9830630Z   BUILDER_ROOT: /builder
2022-08-03T07:18:40.9830818Z   PACKAGE_TYPE: manywheel
2022-08-03T07:18:40.9831003Z   DESIRED_CUDA: cpu-cxx11-abi
2022-08-03T07:18:40.9831196Z   GPU_ARCH_VERSION:

linux-binary-manywheel / manywheel-py3_8-cpu-cxx11-abi-build / build (4/5)

Step: "Pull Docker image" (full log | diagnosis details)

2022-08-03T07:18:41.7782626Z ##[error]Process completed with exit code 1.

2022-08-03T07:18:38.5282940Z   BINARY_ENV_FILE: /tmp/env
2022-08-03T07:18:38.5283164Z   BUILD_ENVIRONMENT: linux-binary-manywheel
2022-08-03T07:18:38.5283490Z   GITHUB_TOKEN: ***
2022-08-03T07:18:38.5283664Z   PR_NUMBER: 
2022-08-03T07:18:38.5283847Z   PYTORCH_FINAL_PACKAGE_DIR: /artifacts
2022-08-03T07:18:38.5284085Z   SHA1: 30c8a2eb32dc38ff0d39612bf4ea58a2aa4ce3d9
2022-08-03T07:18:38.5284293Z ##[endgroup]
2022-08-03T07:18:38.6111575Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:39.6910806Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:41.7764227Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:41.7782626Z ##[error]Process completed with exit code 1.
2022-08-03T07:18:41.7804509Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-08-03T07:18:41.7804831Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-08-03T07:18:41.7805168Z �[36;1mdocker run --rm -v "${RUNNER_TEMP}/artifacts:/v" -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-03T07:18:41.7816330Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-03T07:18:41.7816550Z env:
2022-08-03T07:18:41.7816723Z   PYTORCH_ROOT: /pytorch
2022-08-03T07:18:41.7816899Z   BUILDER_ROOT: /builder
2022-08-03T07:18:41.7817086Z   PACKAGE_TYPE: manywheel
2022-08-03T07:18:41.7817281Z   DESIRED_CUDA: cpu-cxx11-abi
2022-08-03T07:18:41.7817459Z   GPU_ARCH_VERSION:

linux-binary-manywheel / manywheel-py3_7-cpu-cxx11-abi-build / build (5/5)

Step: "Pull Docker image" (full log | diagnosis details)

2022-08-03T07:18:25.7730280Z ##[error]Process completed with exit code 1.

2022-08-03T07:18:22.5161680Z   BINARY_ENV_FILE: /tmp/env
2022-08-03T07:18:22.5161899Z   BUILD_ENVIRONMENT: linux-binary-manywheel
2022-08-03T07:18:22.5162216Z   GITHUB_TOKEN: ***
2022-08-03T07:18:22.5162388Z   PR_NUMBER: 
2022-08-03T07:18:22.5162570Z   PYTORCH_FINAL_PACKAGE_DIR: /artifacts
2022-08-03T07:18:22.5162805Z   SHA1: 30c8a2eb32dc38ff0d39612bf4ea58a2aa4ce3d9
2022-08-03T07:18:22.5163011Z ##[endgroup]
2022-08-03T07:18:22.6105656Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:23.6921453Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:25.7711156Z Error response from daemon: pull access denied for pytorch/manylinuxcxx11-abi-builder, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
2022-08-03T07:18:25.7730280Z ##[error]Process completed with exit code 1.
2022-08-03T07:18:25.7751634Z ##[group]Run # Ensure the working directory gets chowned back to the current user
2022-08-03T07:18:25.7751959Z �[36;1m# Ensure the working directory gets chowned back to the current user�[0m
2022-08-03T07:18:25.7752302Z �[36;1mdocker run --rm -v "${RUNNER_TEMP}/artifacts:/v" -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .�[0m
2022-08-03T07:18:25.7763746Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-03T07:18:25.7763966Z env:
2022-08-03T07:18:25.7764147Z   PYTORCH_ROOT: /pytorch
2022-08-03T07:18:25.7764328Z   BUILDER_ROOT: /builder
2022-08-03T07:18:25.7764522Z   PACKAGE_TYPE: manywheel
2022-08-03T07:18:25.7764726Z   DESIRED_CUDA: cpu-cxx11-abi
2022-08-03T07:18:25.7764908Z   GPU_ARCH_VERSION:

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.

zhuhong61 · 2022-06-28T07:47:26Z

Hi @malfet, any comment for this? This PR is for pytorch/builder#990 (comment), thanks!

gujinghui · 2022-07-04T04:45:38Z

Hi @malfet
Could you help review? Thanks.

malfet · 2022-07-13T23:17:18Z

@zhuhong61 please rebase, otherwise looks good to me

zhuhong61 · 2022-07-14T12:40:09Z

@malfet Rebase finished. Thanks!

malfet

It could not go until pytorch/builder#1062 is re-landed, is it?

zhuhong61 · 2022-07-29T07:44:23Z

It could not go until pytorch/builder#1062 is re-landed, is it?

Thanks @malfet
#79409 and pytorch/builder#1062 are independent of each ohter.
This PR #79409 is to support the ci system for pip wheel (merged now, please see pytorch/builder#990 and pytorch/builder#1023) , and pytorch/builder#1062 is for building the conda wheel.

When conda wheel pytorch/builder#1062 is ready, I will add checks in ci system for it separately.

gujinghui · 2022-08-03T09:32:05Z

It could not go until pytorch/builder#1062 is re-landed, is it?

@malfet This one is ready to merge. Pls help review.

malfet · 2022-08-10T22:37:08Z

Can we validate that it is compatible with manylinux_2_28?

zhuhong61 · 2022-08-11T03:27:50Z

Can we validate that it is compatible with manylinux_2_28?

@malfet ,Thanks for your reply. We have validated the pip wheel built with cpu-cxx11-abi in manylinux_2_28 (x86_64 image: quay.io/pypa/manylinux_2_28_x86_64 https://github.com/pypa/manylinux), and it is compatible with manylinux_2_28.
Here is the steps of validation:

Build a pip wheel with cpu-cxx11-abi:
Ref: pytorch/builder#990 and pytorch/builder#1023
we will get the torch-1.13.0.dev20220811+cpu.cxx11.abi-cp37-cp37m-linux_x86_64.whl
Pull docker image of manylinux_2_28_x86_64
docker image pull quay.io/pypa/manylinux_2_28_x86_64
Run the docker:
docker run -it quay.io/pypa/manylinux_2_28_x86_64:latest
Copy the built pip wheel into docker and create an environment to install it:
docker cp torch-1.13.0.dev20220811+cpu.cxx11.abi-cp37-cp37m-linux_x86_64.whl e2b558af129d:/
(e2b558af129d is the container id of manylinux_2_28_x86_64 docker image)
(install conda ...)

conda create -n py_37 python=3.7
conda activate py_37
pip install torch-1.13.0.dev20220811+cpu.cxx11.abi-cp37-cp37m-linux_x86_64.whl

Validate:

(py_37) [root@e2b558af129d /]# python
>>> import torch
>>> print(torch._C._GLIBCXX_USE_CXX11_ABI)
True
>>> torch.randn(3,4)
tensor([[-2.0821, -0.6565,  0.4604, -1.3281],
        [-0.0822,  0.4391,  0.7771, -0.1675],
        [ 0.6157,  1.7519, -1.0979,  0.1158]])

zhuhong61 · 2022-09-07T02:41:51Z

Hi @malfet Any comments? Thanks!

gujinghui · 2022-09-16T16:33:36Z

@malfet
The PR is ready to land. Could you help review again? Thanks.

facebook-github-bot · 2022-10-04T01:02:01Z

/easycla

As part of the transition to the PyTorch Foundation, this project now requires contributions be covered under the new CLA. See #85559 for additional details.

This comment will trigger a new check of this PR. If you are already covered, you will simply see a new "EasyCLA" check that passes. If you are not covered, a bot will leave a new comment with a link to sign.

linux-foundation-easycla · 2022-10-04T01:02:04Z

The committers listed above are authorized under a signed CLA.

✅ login: zhuhong61 (0516df1)

pytorch-bot · 2022-11-02T02:09:28Z

🔗 Helpful Links

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

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

✅ No Failures

As of commit 6c72bcb:
💚 Looks good so far! There are no failures yet. 💚

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

gujinghui · 2023-02-07T14:01:51Z

Hi @malfet @atalman We are targeting this PT2.0 release. The PRs for this nightly build is for verifying we can build this new wheel successfully without blocking pytorch's current builds. But our final purpose is release. Could you please provide the methods for release?

Correct me if I'm wrong, but we've discussed this a few times. This change makes the package interoperable with the rest of the ecosystem(i.e. torch vision build for manylinux2014 would not be able to use cxx11-abi package, would it) Also, switching CXX11 ABI does not bring any performance gains, does it? Moreover, I'm not sure if this package will be compatible with say manylinux_2_28_x86_64?

If one's goal is to distributed custom build PyTorch with some additional extensions, then In my opinion best delivery mechanism is a Linux container, for example, docker.

@malfet Thanks for reply.
This build should be not for performance. Its aim should be to provide an option to ecosystem, to make full coverage of PyTorch use case. As @fzhao3 mentioned above, PyTorch users in community do have the ask to ABI=1 build for a long time. So do we.
To cover ABI=1 use case in ecosystem, we have to start from PyTorch, because PyTorch is the foundation of the whole ecosystem. Although torchvison already has build option for ABI=1, without corresponding PyTorch package, torchvision users are in same situation, to build torchvision with ABI=1 by themselves. So do other torch infrastructures.

To solve or bypass the ABI issue, I think we have 3 options as below.

Wrap PyTorch C++ APIs in which has std::string or std::list, to support both ABI=1 and ABI=0
Applications has glue layer to covert ABI=1 std::string to ABI=1 std::string when talking with PyTorch
Provide PyTorch release package with ABI=1

For #1, it should be a perfect solution, but with PyTorch API changes, which will pollute ecosystem, as well?
For #2, PyTorch APIs with std::string are widely used in our application/extension. It's too difficult to completely hook each invocation, and introduce huge maintain efforts, as PyTorch is evolving fast. Anyway, we will still try to figure out whether it's a doable solution for our requirement.

For #3, @fzhao3 proposed a great idea, that, only provide a release build package on download server in a separate folder, instead of official release path? Could you consider this option? Thanks.

atalman · 2023-02-07T14:50:55Z

@fzhao3 @gujinghui some concerns regarding publishing new binary:

If we decide to publish this binary, we would need to have not only the binary itself but all the associated smoke tests and validation workflows implemented in order to ensure the quality of the build and that the build does not break from one release to another. Please refer to: https://github.com/pytorch/test-infra/wiki/Validation-Framework#using-validation-framework-for-nightly-and-release-validation
Publishing it in separate folder, is problematic since our releng team would need to support new workflow specially for publishing and testing this package.
Is there a way instead of publishing new binary to provide a users with a flag/variable such that people can compile this binary just by setting this flag ?

malfet · 2023-02-09T00:05:46Z

@pytorchbot rebase

pytorchmergebot · 2023-02-09T00:07:43Z

@pytorchbot successfully started a rebase job. Check the current status here

pytorchmergebot · 2023-02-09T00:07:49Z

Successfully rebased zh/abi_ci onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout zh/abi_ci && git pull --rebase)

gujinghui · 2023-02-10T13:47:12Z

@malfet @atalman

To fix the failure in xla build as below, we reverted the change in CMakeLists.txt.
Same as previous, only set "-fabi-version=11" for ABI=0 build.

+ python -c 'import torch; exit(0 if torch._C._PYBIND11_BUILD_ABI == '\''_cxxabi1011'\'' else 1)'
Error: Process completed with exit code 1.

Could you please review and merge the PR pytorch/builder#1303 ?
Then, this PR should be able to land.

atalman · 2023-02-10T16:31:40Z

@pytorchbot rebase

pytorchmergebot · 2023-02-10T16:33:37Z

@pytorchbot successfully started a rebase job. Check the current status here

pytorchmergebot · 2023-02-10T16:33:44Z

Successfully rebased zh/abi_ci onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout zh/abi_ci && git pull --rebase)

zhuhong61 · 2023-02-14T02:09:06Z

@pytorchbot merge

pytorchmergebot · 2023-02-14T02:11:02Z

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

Advanced Debugging

Check the merge workflow status
here

zhuhong61 · 2023-02-14T05:44:36Z

@pytorchbot rebase

pytorchmergebot · 2023-02-14T05:46:36Z

@pytorchbot successfully started a rebase job. Check the current status here

pytorchmergebot · 2023-02-14T05:46:42Z

Successfully rebased zh/abi_ci onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout zh/abi_ci && git pull --rebase)

pytorchmergebot · 2023-02-14T05:49:53Z

Merge failed

Reason: New commits were pushed while merging. Please rerun the merge command.

Details for Dev Infra team

Raised by workflow job

…cpu-cxx11-abi Co-authored-by: Zhu Hong <hong.zhu@intel.com> Co-authored-by: Guo Yejun <yejun.guo@intel.com>

zhuhong61 · 2023-02-14T12:56:57Z

@pytorchbot merge

pytorchmergebot · 2023-02-14T12:58:55Z

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

Advanced Debugging

Check the merge workflow status
here

zhuhong61 requested a review from a team as a code owner June 13, 2022 09:33

facebook-github-bot added the cla signed label Jun 13, 2022

pytorchbot added the open source label Jun 13, 2022

mikaylagawarecki added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 15, 2022

zhuhong61 force-pushed the zh/abi_ci branch from ea1c3c7 to 4a958dc Compare June 15, 2022 06:54

yanbing-j added the intel This tag is for PR from Intel label Jul 4, 2022

zhuhong61 mentioned this pull request Jul 5, 2022

conda: add _GLIBCXX_USE_CXX11_ABI=1 support for linux cpu wheel pytorch/builder#1062

Merged

yanbing-j added the intel priority matters to intel architecture from performance wise label Jul 13, 2022

malfet approved these changes Jul 13, 2022

View reviewed changes

malfet added the ciflow/binaries_wheel Trigger binary build and upload jobs for wheel on the PR label Jul 13, 2022

zhuhong61 force-pushed the zh/abi_ci branch from 4a958dc to 2800ced Compare July 14, 2022 12:22

jgong5 requested a review from malfet July 27, 2022 23:12

malfet requested changes Jul 27, 2022

View reviewed changes

zhuhong61 force-pushed the zh/abi_ci branch from 2800ced to 30c8a2e Compare August 3, 2022 07:11

yanbing-j requested a review from malfet August 3, 2022 10:14

zhuhong61 force-pushed the zh/abi_ci branch from 30c8a2e to 0516df1 Compare November 2, 2022 02:09

pytorchmergebot force-pushed the zh/abi_ci branch from d3bc80e to 25a7b7a Compare February 9, 2023 00:07

zhuhong61 force-pushed the zh/abi_ci branch from 25a7b7a to 7952422 Compare February 9, 2023 06:10

zhuhong61 mentioned this pull request Feb 10, 2023

Set torch._C._PYBIND11_BUILD_ABI version check only for GLIBCXX_USE_CXX11_ABI=0 pytorch/builder#1303

Merged

pytorchmergebot force-pushed the zh/abi_ci branch from 7952422 to d2264e0 Compare February 10, 2023 16:33

zhuhong61 force-pushed the zh/abi_ci branch from d2264e0 to 2637ff7 Compare February 13, 2023 15:42

pytorch-bot bot added ciflow/trunk Trigger trunk jobs on your pull request topic: not user facing topic category labels Feb 14, 2023

pytorchmergebot force-pushed the zh/abi_ci branch from 2637ff7 to e0d408c Compare February 14, 2023 05:46

Add new checks in CI system to verify the built linux pip wheel with …

6c72bcb

…cpu-cxx11-abi Co-authored-by: Zhu Hong <hong.zhu@intel.com> Co-authored-by: Guo Yejun <yejun.guo@intel.com>

zhuhong61 force-pushed the zh/abi_ci branch from e0d408c to 6c72bcb Compare February 14, 2023 08:26

pytorchmergebot added the Merged label Feb 14, 2023

pytorchmergebot closed this in 73ee496 Feb 14, 2023

Conversation

zhuhong61 commented Jun 13, 2022 • edited by pytorch-bot bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

facebook-github-bot commented Jun 13, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful links

❌ 5 New Failures, 3 Pending

🕵️ 5 new failures recognized by patterns

linux-binary-manywheel / manywheel-py3_9-cpu-cxx11-abi-build / build (1/5)

linux-binary-manywheel / manywheel-py3_11-cpu-cxx11-abi-build / build (2/5)

linux-binary-manywheel / manywheel-py3_10-cpu-cxx11-abi-build / build (3/5)

linux-binary-manywheel / manywheel-py3_8-cpu-cxx11-abi-build / build (4/5)

linux-binary-manywheel / manywheel-py3_7-cpu-cxx11-abi-build / build (5/5)

Uh oh!

zhuhong61 commented Jun 28, 2022

Uh oh!

gujinghui commented Jul 4, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

malfet commented Jul 13, 2022

Uh oh!

zhuhong61 commented Jul 14, 2022

Uh oh!

malfet left a comment

Choose a reason for hiding this comment

Uh oh!

zhuhong61 commented Jul 29, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gujinghui commented Aug 3, 2022

Uh oh!

malfet commented Aug 10, 2022

Uh oh!

zhuhong61 commented Aug 11, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zhuhong61 commented Sep 7, 2022

Uh oh!

gujinghui commented Sep 16, 2022

Uh oh!

facebook-github-bot commented Oct 4, 2022

Uh oh!

linux-foundation-easycla bot commented Oct 4, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-bot bot commented Nov 2, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

✅ No Failures

Uh oh!

gujinghui commented Feb 7, 2023

Uh oh!

atalman commented Feb 7, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

malfet commented Feb 9, 2023

Uh oh!

pytorchmergebot commented Feb 9, 2023

Uh oh!

pytorchmergebot commented Feb 9, 2023

Uh oh!

gujinghui commented Feb 10, 2023

Uh oh!

atalman commented Feb 10, 2023

Uh oh!

pytorchmergebot commented Feb 10, 2023

Uh oh!

pytorchmergebot commented Feb 10, 2023

Uh oh!

zhuhong61 commented Feb 14, 2023

Uh oh!

pytorchmergebot commented Feb 14, 2023

Merge started

Uh oh!

zhuhong61 commented Feb 14, 2023

Uh oh!

pytorchmergebot commented Feb 14, 2023

Uh oh!

zhuhong61 commented Jun 13, 2022 •

edited by pytorch-bot bot

Loading

facebook-github-bot commented Jun 13, 2022 •

edited

Loading

gujinghui commented Jul 4, 2022 •

edited

Loading

zhuhong61 commented Jul 29, 2022 •

edited

Loading

zhuhong61 commented Aug 11, 2022 •

edited

Loading

linux-foundation-easycla bot commented Oct 4, 2022 •

edited

Loading

pytorch-bot bot commented Nov 2, 2022 •

edited

Loading

atalman commented Feb 7, 2023 •

edited

Loading