-
Notifications
You must be signed in to change notification settings - Fork 91
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
[WIP] Add RAPIDS Nightly to GPU CI #436
Draft
praateekmahajan
wants to merge
5
commits into
NVIDIA:main
Choose a base branch
from
praateekmahajan:praateek/add-gpu-ci-nightly
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,8 +2,7 @@ name: "GPU CI/CD" | |
|
||
on: | ||
push: | ||
branches: | ||
- main | ||
branches: [main] | ||
pull_request: | ||
branches: | ||
# We can run gpuCI on any PR targeting these branches | ||
|
@@ -12,28 +11,36 @@ on: | |
- '[rv][0-9].[0-9].[0-9]rc[0-9]' | ||
# PR has to be labeled with "gpuCI" label | ||
# If new commits are added, the "gpuCI" label has to be removed and re-added to rerun gpuCI | ||
types: [ labeled ] | ||
types: [labeled] | ||
|
||
concurrency: | ||
group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }} | ||
cancel-in-progress: true | ||
|
||
# Reusable job templates | ||
jobs: | ||
# First, we build and push a NeMo-Curator container | ||
build-container: | ||
# "build-container" job is run if the "gpuci" label is added to the PR | ||
if: ${{ github.event.label.name == 'gpuci' || github.ref == 'refs/heads/main' }} | ||
strategy: | ||
matrix: | ||
include: | ||
- type: stable | ||
image-suffix: "" | ||
- type: nightly | ||
image-suffix: "_nightly" | ||
uses: NVIDIA/NeMo-FW-CI-templates/.github/workflows/[email protected] | ||
with: | ||
image-name: nemo_curator_container | ||
image-name: nemo_curator_container${{ matrix.image-suffix }} | ||
dockerfile: Dockerfile | ||
image-label: nemo-curator | ||
image-label: nemo-curator${{ matrix.image-suffix }} | ||
build-args: | | ||
IMAGE_LABEL=nemo-curator | ||
IMAGE_LABEL=nemo-curator${{ matrix.image-suffix }} | ||
REPO_URL=https://github.com/${{ github.repository }}.git | ||
CURATOR_COMMIT=${{ github.sha }} | ||
BUILD_TYPE=${{ matrix.type }} | ||
prune-filter-timerange: 24h | ||
|
||
# Then, we run our PyTests in the container we just built | ||
run-gpu-tests: | ||
needs: build-container | ||
|
@@ -42,48 +49,59 @@ jobs: | |
runs-on: self-hosted-azure | ||
# "run-gpu-tests" job is run if the "gpuci" label is added to the PR | ||
if: ${{ github.event.label.name == 'gpuci' || github.ref == 'refs/heads/main' }} | ||
strategy: | ||
matrix: | ||
include: | ||
- type: stable | ||
image-suffix: "" | ||
- type: nightly | ||
image-suffix: "_nightly" | ||
|
||
env: | ||
CONTAINER_NAME: nemo-curator-container${{ matrix.image-suffix }} | ||
IMAGE_NAME: nemoci.azurecr.io/nemo_curator_container${{ matrix.image-suffix }}:${{ github.run_id }} | ||
|
||
steps: | ||
# If something went wrong during the last cleanup, this step ensures any existing container is removed | ||
- name: Remove existing container if it exists | ||
run: | | ||
if [ "$(docker ps -aq -f name=nemo-curator-container)" ]; then | ||
docker rm -f nemo-curator-container | ||
if [ "$(docker ps -aq -f name=${{ env.CONTAINER_NAME }})" ]; then | ||
docker rm -f ${{ env.CONTAINER_NAME }} | ||
fi | ||
|
||
# This runs the container which was pushed by build-container, which we call "nemo-curator-container" | ||
# `--gpus all` ensures that all of the GPUs from our self-hosted-azure runner are available in the container | ||
# We use "github.run_id" to identify the PR with the commits we want to run the PyTests with | ||
# `bash -c "sleep infinity"` keeps the container running indefinitely without exiting | ||
# This runs the container which was pushed by build-container, which we call "nemo-curator-container" | ||
# `--gpus all` ensures that all of the GPUs from our self-hosted-azure runner are available in the container | ||
# We use "github.run_id" to identify the PR with the commits we want to run the PyTests with | ||
# `bash -c "sleep infinity"` keeps the container running indefinitely without exiting | ||
- name: Run Docker container | ||
run: | | ||
docker run --gpus all --name nemo-curator-container -d nemoci.azurecr.io/nemo_curator_container:${{ github.run_id }} bash -c "sleep infinity" | ||
|
||
# Expect `whoami` to be "azureuser" | ||
# Expect `nvidia-smi` to show our 2 A100 GPUs | ||
- name: Check GPUs | ||
run: | | ||
whoami | ||
docker exec nemo-curator-container nvidia-smi | ||
docker run --gpus all --name ${{ env.CONTAINER_NAME }} \ | ||
-d ${{ env.IMAGE_NAME }} \ | ||
bash -c "sleep infinity" | ||
|
||
# In the virtual environment (called "curator") we created in the container, | ||
# list all of our packages. Useful for debugging | ||
- name: Verify installations | ||
# In the virtual environment (called "curator") we created in the container, | ||
# list all of our packages. Useful for debugging | ||
# Expect `whoami` to be "azureuser" | ||
# Expect `nvidia-smi` to show our 2 A100 GPUs | ||
- name: Check GPUs + Verify installations | ||
run: | | ||
docker exec nemo-curator-container pip list | ||
|
||
# In the virtual environment (called "curator") we created in the container, | ||
# run our PyTests marked with `@pytest.mark.gpu` | ||
# We specify the `rootdir` to help locate the "pyproject.toml" file (which is in the root directory of the repository), | ||
# and then the directory where the PyTests are located | ||
echo "Checking system user:" | ||
whoami | ||
docker exec ${{ env.CONTAINER_NAME }} whoami | ||
echo "Checking GPU availability:" | ||
docker exec ${{ env.CONTAINER_NAME }} nvidia-smi | ||
echo "Checking installed packages:" | ||
docker exec ${{ env.CONTAINER_NAME }} pip list | ||
# In the virtual environment (called "curator") we created in the container, | ||
# run our PyTests marked with `@pytest.mark.gpu` | ||
# We specify the `rootdir` to help locate the "pyproject.toml" file (which is in the root directory of the repository), | ||
# and then the directory where the PyTests are located | ||
- name: Run PyTests with GPU mark | ||
run: | | ||
docker exec nemo-curator-container pytest -m gpu --rootdir /opt/NeMo-Curator /opt/NeMo-Curator/tests | ||
|
||
docker exec ${{ env.CONTAINER_NAME }} pytest -m gpu --rootdir /opt/NeMo-Curator /opt/NeMo-Curator/tests | ||
# After running `docker stop`, the container remains in an exited state | ||
# It is still present on our system and could be restarted with `docker start` | ||
# Thus, we use `docker rm` to permanently removed it from the system | ||
- name: Cleanup | ||
if: always() | ||
run: | | ||
docker stop nemo-curator-container && docker rm nemo-curator-container | ||
run: docker stop ${{ env.CONTAINER_NAME }} && docker rm ${{ env.CONTAINER_NAME }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
We might need to check if the nightly can use the same caching logic as stable, or if nightly should just always build a fresh non-cached container.
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.
+1, wanted to flag this explicitly as we do some curator-update optimization above, and I want to ensure if branching doesn't mess with it.
cc @ko3n1g
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.
Do these optimizations come from the base-image?
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 mean, if they do even if the base-image tag is unchanged b/c they overwrite it we should extend this build-workflow so that we can force pull the base image. In all other cases we don't need to be worried about caching i believe