You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PyTorch now "supports" higher precision unsigned int dtypes like uint16, uint32, and uint64, but the support is very poor, to the point where every test for a two-argument function will fail.
I propose adding an environment variable ARRAY_API_TESTS_SKIP_DTYPES which could be set to something like uint16,uint32,uint64 to manually skip those dtypes (the same behavior as if they weren't present on the namespace). Skipping required dtypes would still not be supported.
The text was updated successfully, but these errors were encountered:
asmeurer
added a commit
to asmeurer/array-api-tests
that referenced
this issue
May 21, 2024
This requires using dtype strategies from hh instead of xps.
This also fixes some functions in linalg and fft that were incorrectly only
tested against real floating-point dtypes, due to Hypothesis's confusing
nomenclature of "floating_dtypes" being only real floating-point dtypes (and
this also eliminates the use of Hypothesis's confusing "scalar_dtypes").
Fixesdata-apis#265
PyTorch now "supports" higher precision unsigned int dtypes like uint16, uint32, and uint64, but the support is very poor, to the point where every test for a two-argument function will fail.
See data-apis/array-api-compat#138
I propose adding an environment variable
ARRAY_API_TESTS_SKIP_DTYPES
which could be set to something likeuint16,uint32,uint64
to manually skip those dtypes (the same behavior as if they weren't present on the namespace). Skipping required dtypes would still not be supported.The text was updated successfully, but these errors were encountered: