Skip einsum test_out_0d for NumPy older than 2.4.5 - #3029
Closed
antonwolfy wants to merge 1 commit into
Closed
Conversation
The reference numpy.einsum call with a 0-d out array and optimize="optimal" only behaves as expected starting with NumPy 2.4.5, so guard test_out_0d with the corresponding version requirement.
Contributor
Author
|
Superseded by #3030 (branch on the upstream repo instead of a fork). |
Collaborator
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.
This guards
TestEinsum.test_out_0dwith@testing.with_requires("numpy>=2.4.5").The test compares
dpnp.einsumagainst a referencenumpy.einsumcall that uses a 0-doutarray withoptimize="optimal". That reference behavior only matches on NumPy 2.4.5 and newer, so the test is skipped on older NumPy versions to avoid spurious failures.The test was introduced in #2987.