Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Exporttorch::utils::tensor_to_numpy#154178

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
shink wants to merge5 commits intopytorch:mainfromshink:fix/tensor_to_numpy

Conversation

@shink
Copy link
Contributor

@shinkshink commentedMay 23, 2025•
edited
Loading

@pytorch-bot
Copy link

pytorch-botbot commentedMay 23, 2025•
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results athud.pytorch.org/pr/154178

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

✅ You can merge normally! (1 Unrelated Failure)

As of commitec0ab31 with merge based8e4c1c (image):

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

@shink
Copy link
ContributorAuthor

@pytorchbot label "topic: not user facing"

pytorch-bot[bot] reacted with thumbs up emoji

@pytorch-botpytorch-botbot added the topic: not user facingtopic category labelMay 23, 2025
@shink
Copy link
ContributorAuthor

I got this in this case:

ninja: no work to do.[[1. 2.] [3. 4.]]<class 'numpy.ndarray'>

Copy link
Collaborator

@albanDalbanD left a comment

Choose a reason for hiding this comment

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

SGTM!
Do you need tensor_from_numpy() as well?

@Skylion007
Copy link
Collaborator

@pytorchbot merge

pytorch-bot[bot] reacted with thumbs up emoji

@pytorch-botpytorch-botbot added the ciflow/trunkTrigger trunk jobs on your pull request labelMay 25, 2025
@Skylion007Skylion007 added release notes: cpprelease notes category release notes: python_frontendpython frontend release notes category and removed ciflow/trunkTrigger trunk jobs on your pull request topic: not user facingtopic category labelsMay 25, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

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

Learn more about merging in thewiki.

Questions? Feedback? Please reach out to thePyTorch 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 byviewing the failures on hud

Details for Dev Infra teamRaised byworkflow job

Failing merge rule: Core Maintainers

Copy link
Collaborator

@youkaichaoyoukaichao left a comment

Choose a reason for hiding this comment

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

do we need to addTORCH_API for the functions below? likeis_numpy_scalar,is_numpy_bool,is_numpy_int,is_numpy_available etc.

shink reacted with thumbs up emojiSkylion007 reacted with eyes emoji
@shink
Copy link
ContributorAuthor

@pytorchbot rebase -b main

pytorch-bot[bot] reacted with thumbs up emoji

@shink
Copy link
ContributorAuthor

Sorry for the late. Have updated.

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job ontorefs/remotes/origin/main. Check the current statushere

@pytorchmergebot
Copy link
Collaborator

Successfully rebasedfix/tensor_to_numpy ontorefs/remotes/origin/main, please pull locally before adding more changes (for example, viagit checkout fix/tensor_to_numpy && git pull --rebase)

@shink
Copy link
ContributorAuthor

@pytorchbot merge

@pytorch-bot
Copy link

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@shink
Copy link
ContributorAuthor

@pytorchbot merge

@pytorch-bot
Copy link

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@youkaichao
Copy link
Collaborator

@albanD how to help merge this PR?

shink reacted with thumbs up emoji

@shink
Copy link
ContributorAuthor

@pytorchbot merge

@pytorch-bot
Copy link

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@albanD
Copy link
Collaborator

@pytorchbot merge

@pytorch-bot
Copy link

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

@albanD
Copy link
Collaborator

@shink would you be able to rebase on latest trunk to properly trigger CI please? Then we should be able to merge!

shink reacted with thumbs up emoji

@shink
Copy link
ContributorAuthor

@pytorchbot rebase -b main

pytorch-bot[bot] reacted with thumbs up emoji

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job ontorefs/remotes/origin/main. Check the current statushere

@pytorchmergebot
Copy link
Collaborator

Successfully rebasedfix/tensor_to_numpy ontorefs/remotes/origin/main, please pull locally before adding more changes (for example, viagit checkout fix/tensor_to_numpy && git pull --rebase)

@shink
Copy link
ContributorAuthor

@pytorchbot merge

pytorch-bot[bot] reacted with thumbs up emoji

@pytorch-botpytorch-botbot added the ciflow/trunkTrigger trunk jobs on your pull request labelJun 4, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

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

Learn more about merging in thewiki.

Questions? Feedback? Please reach out to thePyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@cyyever
Copy link
Collaborator

@pytorchbot merge -i

pytorch-bot[bot] and shink reacted with thumbs up emoji

@pytorchmergebot
Copy link
Collaborator

The mergejob was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information seepytorch-bot wiki.

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks:pull / linux-jammy-py3-clang12-executorch / build

Learn more about merging in thewiki.

Questions? Feedback? Please reach out to thePyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@Skylion007Skylion007Skylion007 approved these changes

@albanDalbanDalbanD approved these changes

@youkaichaoyoukaichaoyoukaichao approved these changes

Assignees

No one assigned

Labels

ciflow/trunkTrigger trunk jobs on your pull requestMergedopen sourcerelease notes: cpprelease notes categoryrelease notes: python_frontendpython frontend release notes category

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

tensor_to_numpy symbol not exported in libtorch_python.so in pytorch 2.7

7 participants

@shink@Skylion007@pytorchmergebot@youkaichao@albanD@cyyever@pytorchbot
[8]ページ先頭
©2009-2025 Movatter.jp