Repository navigation
TST: skip api_version=2024.12 on dpnp - #488
Merged
Merged
Conversation
dpnp 0.21.0 supports only the 2025.12 version of the array API standard.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dpnp 0.21.0, released on Oct 28, moved to the 2025.12 version of the array API standard. Its
__array_namespace__accepts only the version it implements, sotest_array_namespacenow fails on every dpnp job:This adds
"2024.12"to the dpnp xfail list, as was done forjax.numpyin #456 and is already the case formparray.Follow-up to #486 (comment).