Skip to content
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

Merged
merged 3 commits into from
Oct 31, 2024

Conversation

jameslamb
Copy link
Member

Continues the work of setting up CI here (breaking more changes off of #53).

Proposes adding nightly builds / tests, but not publishing to the nightly PyPI index / rapidsai-nightly conda channel. Those publishing jobs should be added here only once cugraph folks are ready to fully move development of these libraries to this repo. ref: #58 (comment)

This also removes some minor lingering cugraph references that look like they don't belong in this repo.

@jameslamb jameslamb added improvement Improves an existing functionality non-breaking Introduces a non-breaking change labels Oct 30, 2024
@jameslamb jameslamb requested a review from a team as a code owner October 30, 2024 13:23
@jameslamb jameslamb requested a review from bdice October 30, 2024 13:23
.github/workflows/build.yaml Outdated Show resolved Hide resolved
.github/workflows/build.yaml Outdated Show resolved Hide resolved
@jameslamb jameslamb requested a review from bdice October 30, 2024 14:19
.github/workflows/build.yaml Outdated Show resolved Hide resolved
date: ${{ inputs.date }}
sha: ${{ inputs.sha }}
script: ci/test_wheel_pylibwholegraph.sh
matrix_filter: map(select(.ARCH == "amd64"))
Copy link
Contributor

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?

Copy link
Member Author

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 and cugraph-pyg about 9 months ago: rapidsai/cugraph#4133

Maybe they or @alexbarghi-nv could share why it's like that.

Copy link
Member

@alexbarghi-nv alexbarghi-nv Oct 31, 2024

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.

Copy link
Member

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.

Copy link
Member

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.

Copy link
Member Author

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 of pytorch 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.

@jameslamb
Copy link
Member Author

/merge

@rapids-bot rapids-bot bot merged commit f7ab898 into rapidsai:branch-24.12 Oct 31, 2024
78 checks passed
@jameslamb jameslamb deleted the nightly-builds branch October 31, 2024 20:39
rapids-bot bot pushed a commit that referenced this pull request Dec 2, 2024
All of this repo's `conda-python-tests` jobs have conditions in them like "skip on ARM":

https://github.com/rapidsai/cugraph-gnn/blob/2dd300122dfd6fdea70c9d20c276a3c5946b7613/ci/test_python.sh#L100

https://github.com/rapidsai/cugraph-gnn/blob/2dd300122dfd6fdea70c9d20c276a3c5946b7613/ci/test_python.sh#L141

https://github.com/rapidsai/cugraph-gnn/blob/2dd300122dfd6fdea70c9d20c276a3c5946b7613/ci/test_python.sh#L183

As a result, right now the arm64 `conda-python-tests` jobs are just wasting CI resources... they're spending ~40+~ 5-10 minutes occupying a GPU runner just to download some datasets and then exit ([example build link](https://github.com/rapidsai/cugraph-gnn/actions/runs/11858773988/job/33056063652?pr=69)).

This proposes never even starting those jobs, to make CI here less expensive.

## Notes for Reviewers

### But why are we skipping arm at all?

Lack of pytorch packages. See #61 (comment)

Authors:
  - James Lamb (https://github.com/jameslamb)

Approvers:
  - Alex Barghi (https://github.com/alexbarghi-nv)
  - Jake Awe (https://github.com/AyodeAwe)

URL: #70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improves an existing functionality non-breaking Introduces a non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants