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
add nightly builds/tests, remove some cugraph references #61
add nightly builds/tests, remove some cugraph references #61
Changes from 2 commits
fdeb6e4
3ac4731
805062d
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.
Just checking - do we know why all these packages skip ARM tests? Should we comment about that?
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 have no idea.
@BradReesWork added that for
wholegraph
over a year ago: rapidsai/wholegraph#24@tingyu66 added that constraint for
cugraph-dgl
andcugraph-pyg
about 9 months ago: rapidsai/cugraph#4133Maybe they or @alexbarghi-nv could share why it's like that.
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.
There are no packages available on arm64 for pytorch that support CUDA.
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 tried re-enabling those tests and they all failed again because it pulled the pytorch CPU package.
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.
As far as I know, most ARM64 users of pytorch are going through DLFW or some other means.
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.
alright thank you. I do see
aarch64
CUDA builds ofpytorch
2.4.1 (the latest version) at https://anaconda.org/conda-forge/pytorch/files, so maybe in the future there's an opportunity to turn these tests back on.I'll leave it as-is for the purpose of this PR yet, to get more CI up and running so we can move development over here from the
cugraph
repo.