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
work around precision error in constraint solver #101607
Conversation
In #101307 we tried to fix #101093 using `nsimplify` to convert floats into rationals, but the fix is not reliable: it is possible for `nsimplify` to pick constants that don't work. Currently, constraint solving is only used by `export`, but constraints are added in all modes. This means that we can hit this issue even in non-`export` modes. This diff works around this issue for such modes by delaying raising such failures until constraint solving. Differential Revision: [D45922797](https://our.internmc.facebook.com/intern/diff/D45922797/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/101607
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit 0839d5c: NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
In #101307 we tried to fix #101093 using `nsimplify` to convert floats into rationals, but the fix is not reliable: it is possible for `nsimplify` to pick constants that don't work. Currently, constraint solving is only used by `export`, but constraints are added in all modes. This means that we can hit this issue even in non-`export` modes. This diff works around this issue for such modes by delaying raising such failures until constraint solving. Differential Revision: [D45922797](https://our.internmc.facebook.com/intern/diff/D45922797/) ghstack-source-id: 189321831 Pull Request resolved: #101607
@pytorchbot merge |
Merge startedYour 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 failedReason: 1 jobs have failed, first few of them are: trunk / linux-focal-rocm5.4.2-py3.8 / test (default, 2, 3, linux.rocm.gpu) Details for Dev Infra teamRaised by workflow job |
@pytorchbot merge -f "unrelated failure: BrokenProcessPool" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
In #101307 we tried to fix #101093 using `nsimplify` to convert floats into rationals, but the fix is not reliable: it is possible for `nsimplify` to pick constants that don't work. Currently, constraint solving is only used by `export`, but constraints are added in all modes. This means that we can hit this issue even in non-`export` modes. This diff works around this issue for such modes by delaying raising such failures until constraint solving. Differential Revision: [D45922797](https://our.internmc.facebook.com/intern/diff/D45922797/) Pull Request resolved: #101607 Approved by: https://github.com/ezyang
Stack from ghstack (oldest at bottom):
In #101307 we tried to fix #101093 using
nsimplify
to convert floats into rationals, but the fix is not reliable: it is possible fornsimplify
to pick constants that don't work.Currently, constraint solving is only used by
export
, but constraints are added in all modes. This means that we can hit this issue even in non-export
modes. This diff works around this issue for such modes by delaying raising such failures until constraint solving.Differential Revision: D45922797