Resolve failures in tests while running with numpy 2.0 #2328
Conversation
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
antonwolfy
requested review from
AlexanderKalistratov,
vlad-perevezentsev,
vtavana and
ndgrigorian
as code owners
|
View rendered docs @ https://intelpython.github.io/dpnp/index.html |
vlad-perevezentsev
approved these changes
Feb 19, 2025
|
Array API standard conformance tests for dpnp=0.17.0dev6=py312he4f9c94_21 ran successfully. |
github-actions bot
added a commit
that referenced
this pull request
Feb 19, 2025
The PR proposes to resolve faults in dpnp tests when running towards numpy 2.0. The affected tests assume numpy fixes released in 2.1 version, so the tests logic has to be updated to align with expected numpy behavior depending on the version used. f56a43f
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.
The PR proposes to resolve faults in dpnp tests when running towards numpy 2.0.
The affected tests assume numpy fixes released in 2.1 version, so the tests logic has to be updated to align with expected numpy behavior depending on the version used.