Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 49
ENH: ndonnx device() support; TST: better ndonnx test coverage#232
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
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -3,11 +3,12 @@ | ||
| import pytest | ||
| wrapped_libraries = ["numpy", "cupy", "torch", "dask.array"] | ||
| all_libraries = wrapped_libraries + ["array_api_strict", "jax.numpy", "sparse"] | ||
| all_libraries = wrapped_libraries + [ | ||
| "array_api_strict", "jax.numpy", "ndonnx", "sparse" | ||
Member There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This too. Why are we testing here libraries which we don't wrap? ContributorAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because | ||
| ] | ||
| def import_(library, wrapper=False): | ||
| if library == 'cupy': | ||
| if library in ('cupy', 'ndonnx'): | ||
| pytest.importorskip(library) | ||
| if wrapper: | ||
| if 'jax' in library: | ||
| @@ -20,3 +21,14 @@ def import_(library, wrapper=False): | ||
| library = 'array_api_compat.' + library | ||
| return import_module(library) | ||
| def xfail(request: pytest.FixtureRequest, reason: str) -> None: | ||
| """ | ||
| XFAIL the currently running test. | ||
| Unlike ``pytest.xfail``, allow rest of test to execute instead of immediately | ||
| halting it, so that it may result in a XPASS. | ||
| xref https://github.com/pandas-dev/pandas/issues/38902 | ||
| """ | ||
| request.node.add_marker(pytest.mark.xfail(reason=reason)) | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I don't quite understand is this: https://github.com/data-apis/array-api-compat/pull/232/files#diff-d5d8fa69860e03769cc235a54027efad4376a8c48eeab71aaa11365ea308123bR141 states that the array API support is internal to
ndonnx, which seems to imply there's no need to special-case it here?The note reads "Similar to JAX,
ndonnxArray API support is contained directly inndonnx." --- and indeed, there are no workarounds for jax in the codebase.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because they support the standard imperfectly. The array-api-tests for
.deviceand.to_deviceare XFAILed:https://github.com/Quantco/ndonnx/actions/workflows/array-api.yml
Adding
.deviceand.to_devicewon't break any library's backwards compatibility, so it would be best if each library just fixed it on their side. And yet here we have a function that works around the quirks of every library - last but not least to support least-than-newest versions of it.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will address this upstream. I should say that it might be deceptive to allow this to work with "cpu".
A serialized ONNX graph from ndonnx could later be executed on many different hardware targets or runtimes. ONNX is one level removed from the execution target by design.
Based on a quick read of the device page of the specification, we may do something similar to what you're doing with Dask.