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

Upgrade submodule pybind to 2.12.0 #122899

Closed
wants to merge 1 commit into from
Closed

Conversation

albanD
Copy link
Collaborator

@albanD albanD commented Mar 28, 2024

To fix #122056

Building with NP 2.0 allows me to run locally with both NP 2.0 and 1.26.
Any other test we should run @rgommers ?

FYI @Skylion007 @atalman

Copy link

pytorch-bot bot commented Mar 28, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit 5960c56 with merge base abe4a0e (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Mar 28, 2024
@rgommers
Copy link
Collaborator

Building with NP 2.0 allows me to run locally with both NP 2.0 and 1.26. Any other test we should run @rgommers ?

The test suite is pretty comprehensive, so no need to run anything else I'd say. Also, the pybind11 fix went through Google-internal testing, and that probably included PyTorch (and certainly a bunch of more esoteric usage of NumPy's C API than what PyTorch uses) - and that all passed.

@Skylion007
Copy link
Collaborator

@rgommers Can confirm internal tests covered PyTorch through Google's import suite.

@albanD
Copy link
Collaborator Author

albanD commented Mar 29, 2024

@pytorchbot merge -i

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 29, 2024
@pytorchmergebot
Copy link
Collaborator

This PR updates submodules third_party/pybind11

If those updates are intentional, please add "submodule" keyword to PR title/description.

@Skylion007 Skylion007 changed the title Upgrade pybind to 2.12.0 Upgrade submodule pybind to 2.12.0 Mar 29, 2024
@Skylion007
Copy link
Collaborator

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

Merge failed

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

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@cyyever
Copy link
Collaborator

cyyever commented Mar 31, 2024

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: pull / linux-focal-rocm6.0-py3.8 / build

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

@malfet
Copy link
Contributor

malfet commented Apr 2, 2024

@albanD please note, that we've already been running the full test suite against numpy-2.0 after #122157 so I believe PyBind update wasn't strictly speaking necessary (as PyTorch does not integrate with NumPy via pybind)

@atalman
Copy link
Contributor

atalman commented Apr 4, 2024

@pytorchbot cherry-pick --onto release/2.3 -c critical

pytorchbot pushed a commit that referenced this pull request Apr 4, 2024
To fix #122056

Building with NP 2.0 allows me to run locally with both NP 2.0 and 1.26.
Any other test we should run @rgommers  ?

FYI @Skylion007 @atalman
Pull Request resolved: #122899
Approved by: https://github.com/Skylion007

(cherry picked from commit 6c2f36c)
@pytorchbot
Copy link
Collaborator

Cherry picking #122899

The cherry pick PR is at #123355 and it is recommended to link a critical cherry pick PR with an issue

Details for Dev Infra team Raised by workflow job

atalman pushed a commit that referenced this pull request Apr 4, 2024
To fix #122056

Building with NP 2.0 allows me to run locally with both NP 2.0 and 1.26.
Any other test we should run @rgommers  ?

FYI @Skylion007 @atalman
Pull Request resolved: #122899
Approved by: https://github.com/Skylion007

(cherry picked from commit 6c2f36c)

Co-authored-by: albanD <desmaison.alban@gmail.com>
sanketpurandare pushed a commit to sanketpurandare/pytorch that referenced this pull request Apr 22, 2024
To fix pytorch#122056

Building with NP 2.0 allows me to run locally with both NP 2.0 and 1.26.
Any other test we should run @rgommers  ?

FYI @Skylion007 @atalman
Pull Request resolved: pytorch#122899
Approved by: https://github.com/Skylion007
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error "module compiled against ABI version" when using a device on MacBook Pro M2 with MacOS Sonoma 14.4
8 participants