Repository navigation
Sync third-party tests with recent upstream changes - #3092
antonwolfy wants to merge 4 commits into
Conversation
Add new tests for ufunc, reduction, elementwise kernel, copyto and concatenate argument handling. Tests relying on unsupported features (ufunc interface, CUDA array interface, ReductionKernel, ElementwiseKernel) are skipped; expected error messages are adapted to dpnp where only the wording differs.
Skip the argmax/argmin int32 overflow tests when the large array cannot be allocated, rework the huge FFT allocation test to check free memory upfront and clean up afterwards, and raise the timeout for the jitify tests.
Add the thread_unsafe_on_windows helper and keep its use on test_conversion_device_to_cpu commented out, since the thread_unsafe marker is not registered in dpnp and the test is already skipped.
|
View rendered docs @ https://intelpython.github.io/dpnp/pull/3092/index.html |
|
Array API standard conformance tests for dpnp=0.21.0dev13=np2py314h8d9cdd5_6 ran successfully. |
| from __future__ import annotations | ||
|
|
||
| import ctypes | ||
| import sys |
There was a problem hiding this comment.
test_take_negative_index_at_int32_size_boundary in dpnp/tests/third_party/cupy/core_tests/test_ndarray_adv_indexing.py is missing
https://github.com/cupy/cupy/blob/main/tests/cupy_tests/core_tests/test_ndarray_adv_indexing.py#L725
| ] | ||
| jitify_markers = [ | ||
| testing.slow(), | ||
| pytest.mark.timeout(1200), # Cold header initialization can take minutes. |
There was a problem hiding this comment.
dpnp does not include pytest-timeout in its test dependencies
This should be commented for the future
| ] | ||
|
|
||
|
|
||
| def thread_unsafe_on_windows(func): |
There was a problem hiding this comment.
This function is not used
Does it make sense to comment it out?
There was a problem hiding this comment.
That would increase the diff, while keeping it has no drawback.
This PR syncs the third-party tests with recent upstream test changes. Only test files are changed.