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.
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
[NDTensors] JLArrays Extension #1508
[NDTensors] JLArrays Extension #1508
Changes from 11 commits
fc3ca6c
0c9aae6
506a071
c4dad63
f23d305
822411c
e213bff
7068a63
b8b46a3
fd0866e
2caf2d1
9ad5670
0f1f277
95881d5
0acdaec
a4687bd
cdee270
d0b6a2f
d6e675d
bdacf0e
d2be3b3
9428514
b3a2d87
9165664
1cd131d
6654671
8a32daf
ad02066
8534859
e2aa194
1078405
f47cf11
094c3e3
b751d64
1a14a33
0aee394
4e5c622
1b976d0
6027cb6
12f43cb
638377c
4208487
14922b1
38092d8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 don't think there is a reason to not run the tests for JLArrays since they run on CPU anyway. So I think it should just be added as a normal test dependency, and inserted into the device list by default.
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.
So I am seeing an issue with the GPU tests when I have
JLArrays
is in theProject.toml
. To fix the problem, I movedJLArrays
to[extra]
and I add it to the project ifisempty(ARGS) || "base" in ARGS
. However, this would run into a problem if the test args is["base","metal"]
. Right now we aren't testing in that way, though if you would prefer, I can just includeJLArrays
if no GPUs are being tested, i.e. only allowJLArrays
ifisempty(ARGS)
. Let me know, thanks!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's the issue you see? It would be best to try to address that issue and have
JLArrays
as a dependency inProject.toml
and run by default in the tests as we planned, so I would prefer to try to aim for that rather than work around an issue with a more convoluted solution.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.
The issue is that GPUArrays does not compile during
Pkg.test
However, I think I was able to fix the problem by moving
using JLArrays
to after the GPUusing
statements.