[Py3.10] Allow floats to be imported as Long#81372
Conversation
🔗 Helpful links
❌ 1 New FailuresAs of commit 0c350c0 (more details on the Dr. CI page): Expand to see more
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages
|
f64ca34 to
7e9cfbb
Compare
7e9cfbb to
dde1ce5
Compare
|
@pytorchbot merge -f |
|
@pytorchbot successfully started a merge job. Check the current status here |
|
@pytorchbot revert -m "Break internal build" -c ghfirst |
|
@pytorchbot successfully started a revert job. Check the current status here |
|
@malfet your PR has been successfully reverted. |
This reverts commit 69d7334. Reverted #81372 on behalf of https://github.com/DanilBaibak due to Break internal build
|
@DanilBaibak you'll need to revert one that enables py-3.10 |
|
What's the new plan on this |
Thus avoiding `TypeError: 'float' object cannot be interpreted as an integer` when trying to create integer tensor from floating point values Use `c10::checked_convert` to detect overflows during tensor construction from scalars. Modify sparse_csr test that violated this rule Fixes #69319 Tested in #81233 Pull Request resolved: #81372 Approved by: https://github.com/ezyang, https://github.com/ngimel (cherry picked from commit 69d7334)
@ezyang I'm going to reland the change with range checks disabled for pre-3.10 and then work on internal regressions in separate PR |
@DanilBaibak wrong diff number, isn't it? |
This is a re-land of #81372 and #81233 with the exception that it does not force the range-checks on older Python runtime versions and as such should not affect the internal workloads, which were the reason for revert, see #81372 (comment) - [Py3.10] Allow floats to be imported as Long (#81372) - [CI] Move CUDA-11.6 to Python-3.10 configuration (#81233) - Don't do anything about range checks for pre-py3.10 Pull Request resolved: #82329 Approved by: https://github.com/kit1980
Summary: This is a re-land of #81372 and #81233 with the exception that it does not force the range-checks on older Python runtime versions and as such should not affect the internal workloads, which were the reason for revert, see #81372 (comment) - [Py3.10] Allow floats to be imported as Long (#81372) - [CI] Move CUDA-11.6 to Python-3.10 configuration (#81233) - Don't do anything about range checks for pre-py3.10 Pull Request resolved: #82329 Approved by: https://github.com/kit1980 Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/d80fe49de09399e77a384bd9573c7bb69887dd20 Reviewed By: osalpekar Differential Revision: D38234293 Pulled By: malfet fbshipit-source-id: 3f7ffe729ab2a3ef692bc95f5398dfdf395b2397
Thus avoiding
TypeError: 'float' object cannot be interpreted as an integerwhen trying to create integer tensor from floating point valuesUse
c10::checked_convertto detect overflows during tensor construction from scalars. Modify sparse_csr test that violated this ruleFixes #69319
Tested in #81233