KEMBAR78
Add missing operator and corresponding unittest by cz2h · Pull Request #138309 · pytorch/pytorch · GitHub
Skip to content

Conversation

@cz2h
Copy link
Contributor

@cz2h cz2h commented Oct 18, 2024

Fixes #129690

Add operator.neg and oepartor.pos into _SYM_BOOL_OPS.

Provide simple unit test under export/test_serialize.py that can reproduce the issue.

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 18, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit 20c7365 with merge base 29eb65f (image):
💚 Looks good so far! There are no failures yet. 💚

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

@Skylion007 Skylion007 requested a review from ezyang October 18, 2024 14:30
@janeyx99 janeyx99 added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Oct 18, 2024
@ezyang
Copy link
Contributor

ezyang commented Oct 19, 2024

I am deferring to export team on this

@cz2h cz2h requested a review from angelayi October 21, 2024 22:55
@cz2h

This comment was marked as spam.

@cz2h
Copy link
Contributor Author

cz2h commented Oct 25, 2024

Hi @angelayi, would you help review the changes today? Thanks.

++ @ezyang @janeyx99

@cz2h
Copy link
Contributor Author

cz2h commented Oct 25, 2024

Hi @angelayi, @ezyang . I have fixed the lintrunner-noclang issue. Should we kickup the CI again?

@ezyang
Copy link
Contributor

ezyang commented Oct 27, 2024

@pytorchbot merge -i "unrelated problem"

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 27, 2024

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: unrelated problem

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick,close} ...

Try @pytorchbot --help for more info.

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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: Comment with id 2440228348 not found

Details for Dev Infra team Raised by workflow job

@ezyang
Copy link
Contributor

ezyang commented Oct 28, 2024

@pytorchbot merge -i

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

Merge started

Your change will be merged while ignoring the following 1 checks: pull / linux-focal-cuda11.8-py3.10-gcc9 / test (distributed, 1, 3, lf.linux.g4dn.12xlarge.nvidia.gpu)

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 jobs have failed, first few of them are: linux-binary-libtorch-cxx11-abi / libtorch-cpu-shared-with-deps-cxx11-abi-build / build

Details for Dev Infra team Raised by workflow job

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: pull / linux-focal-cuda11.8-py3.10-gcc9 / test (distributed, 1, 3, lf.linux.g4dn.12xlarge.nvidia.gpu), linux-binary-libtorch-cxx11-abi / libtorch-cpu-shared-with-deps-cxx11-abi-build / 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

@cz2h
Copy link
Contributor Author

cz2h commented Oct 28, 2024

@pytorchbot merge -i

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 28, 2024

-i flag is only allowed for users with write permissions

@pytorchmergebot
Copy link
Collaborator

The merge job 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 see pytorch-bot wiki.

@ezyang
Copy link
Contributor

ezyang commented Oct 29, 2024

@pytorchbot merge -r

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot pytorchmergebot force-pushed the fix-serialize-missing-operator branch from 8f47163 to 6b8a376 Compare October 29, 2024 02:34
@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

@cz2h
Copy link
Contributor Author

cz2h commented Oct 29, 2024

Hi @ezyang , thanks for triggering the merge. For my own knowledge purpose, was the merge CI private and only accessible by meta employees or its an opensource project like pytorch?

@ezyang
Copy link
Contributor

ezyang commented Oct 30, 2024

No, you can view it in Dr. CI hud here. Looks like a test failed though

@ezyang
Copy link
Contributor

ezyang commented Oct 30, 2024

although it's a singleton error, it feels unrelated. let's try again

@ezyang
Copy link
Contributor

ezyang commented Oct 30, 2024

@pytorchbot merge -r

@pytorchmergebot
Copy link
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot pytorchmergebot force-pushed the fix-serialize-missing-operator branch from 6b8a376 to 20c7365 Compare October 30, 2024 21:05
@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

rahulsingh-intel pushed a commit to rahulsingh-intel/pytorch that referenced this pull request Nov 5, 2024
Fixes pytorch#129690

Add operator.neg and oepartor.pos into _SYM_BOOL_OPS.

Provide simple unit test under export/test_serialize.py that can reproduce the issue.
Pull Request resolved: pytorch#138309
Approved by: https://github.com/ezyang, https://github.com/angelayi
@cz2h cz2h deleted the fix-serialize-missing-operator branch February 8, 2025 15:45
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 open source release notes: export triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[torch.export] Simple model fails to export with dynamic shapes

6 participants