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
Numpy recently merged support for the 2023.12 revision of the Array API:
numpy/numpy#26724
This breaks two of our tests and I've chosen to skip those tests for
now:
1. The first breakage was caused by differences in how numpy and JAX
cast negative floats to `uint8`. Specifically
`np.float32(-1).astype(np.uint8)` returns `np.uint8(255)` whereas
`jnp.float32(-1).astype(jnp.uint8)` produces `Array(0, dtype=uint8)`.
We don't make any promises about consistency with casting floats to
ints, noting that this can even be backend dependent. I don't believe
this failure is identifying any unexpected behavior, and we test many
other dtypes properly so I'm not concerned about skipping this test.
2. The second failure was caused by the fact that the approach we took
in jax-ml#20550 to support backwards compatibility and the Array API for
`clip` differs from the one used in numpy/numpy#26724. Again, the
behavior is consistent, but it produces a different signature. I've
skipped checking `clip`'s signature, but we should revisit it once
the `a_min` and `a_max` parameters have been removed from JAX.
Fixesjax-ml#22251
Workflow Run URL
Summary of Failures
The text was updated successfully, but these errors were encountered: