-
Notifications
You must be signed in to change notification settings - Fork 32
Fix tests for py3.11 #1172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix tests for py3.11 #1172
Conversation
If the input Python object is out of range for the type being created, a warning is issued, e.g. `np.int16(512*1024)`. This commit implements the suggested work-around.
|
View rendered docs @ https://intelpython.github.io/dpctl/pulls/1172/index.html |
|
Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_112 ran successfully. |
|
Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_113 ran successfully. |
1. Use Python 3.11 2. Use Google Test 1.13.0
cb5098d to
b8e2890
Compare
|
Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_113 ran successfully. |
|
The second commit in this PR updates |
|
Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞 |
|
Array API standard conformance tests for dpctl=0.14.3dev0=py310h76be34b_113 ran successfully. |
This PR addresses deprecation warning reported when
dpt.arange(512*1024, 0, step=-1, dtype="i2")is evaluated issued by NumPy 1.24.This PR also fixes
test_sycl_queue_manager.py:: test_device_context_activates_nested_contextwhich fails with Python 3.11 dueto the change the exception type raised when attempting to nest contexts using object which does not implement context protocol.