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.

Sign up for GitHub

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

Jump to bottom

Add new runners to nightly matrix. #2077

Closed
wants to merge 1 commit into from
Closed

Add new runners to nightly matrix. #2077

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion ci/matrix.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
workflows:

Check notice on line 1 in ci/matrix.yaml

View workflow job for this annotation

GitHub Actions / Build workflow from matrix 

Merging consumers for duplicate producer '[C++17 GCC13] Build(amd64)' in 'CUB CTK12.6 nvcc GCC'

Check notice on line 1 in ci/matrix.yaml

View workflow job for this annotation

GitHub Actions / Build workflow from matrix 

Original consumers: [C++17 GCC13] TestGPU(amd64, V100), [C++17 GCC13] DeviceLaunch(amd64, V100), [C++17 GCC13] GraphCapture(amd64, V100), [C++17 GCC13] HostLaunch(amd64, V100)

Check notice on line 1 in ci/matrix.yaml

View workflow job for this annotation

GitHub Actions / Build workflow from matrix 

Duplicate consumers: [C++17 GCC13] SmallGMem(amd64, V100)

Check notice on line 1 in ci/matrix.yaml

View workflow job for this annotation

GitHub Actions / Build workflow from matrix 

Merged consumers: [C++17 GCC13] TestGPU(amd64, V100), [C++17 GCC13] DeviceLaunch(amd64, V100), [C++17 GCC13] GraphCapture(amd64, V100), [C++17 GCC13] HostLaunch(amd64, V100), [C++17 GCC13] SmallGMem(amd64, V100)
# If any jobs appear here, they will be executed instead of `pull_request' for PRs.
# This is useful for limiting resource usage when a full matrix is not needed.
# The branch protection checks will fail when using this override workflow.
Expand Down Expand Up @@ -51,7 +51,8 @@
- {jobs: ['test'], ctk: '11.1', gpu: 'v100', sm: 'gpu', cxx: 'gcc6', std: [11]}
- {jobs: ['test'], ctk: '11.1', gpu: 't4', sm: 'gpu', cxx: 'clang9', std: [17]}
- {jobs: ['test'], ctk: '11.8', gpu: 'rtx2080', sm: 'gpu', cxx: 'gcc11', std: [17]}
- {jobs: ['test'], ctk: 'curr', gpu: 'rtxa6000', sm: 'gpu', cxx: 'gcc7', std: [14]}
- {jobs: ['test'], ctk: 'curr', gpu: 'a100', sm: 'gpu', cxx: 'gcc7', std: [11], cpu: 'arm64'}
- {jobs: ['test'], ctk: 'curr', gpu: 'rtxa6000', sm: 'gpu', cxx: 'gcc9', std: [14]}
Comment on lines +54 to +55
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we test lowest gcc and C++11?

Id rather have gcc11 and [all]

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The goal with these builds is to test on different hardware, not different dialects. I don't want to do all to keep the number of jobs under control, instead the stds are rotated across the cards.

- {jobs: ['test'], ctk: 'curr', gpu: 'l4', sm: 'gpu', cxx: 'gcc13', std: 'all'}
- {jobs: ['test'], ctk: 'curr', gpu: 'rtx4090', sm: 'gpu', cxx: 'clang9', std: [11]}
# H100 runners are currently flakey, only build since those use CPU-only runners:
Expand Down Expand Up @@ -224,6 +225,7 @@
v100: { sm: 70 } # 32 GB, 40 runners
t4: { sm: 75, testing: true } # 16 GB, 8 runners
rtx2080: { sm: 75, testing: true } # 8 GB, 8 runners
a100: { sm: 80, testing: true } # ? GB, 4 runners, arm64 only
rtxa6000: { sm: 86, testing: true } # 48 GB, 12 runners
l4: { sm: 89, testing: true } # 24 GB, 48 runners
rtx4090: { sm: 89, testing: true } # 24 GB, 10 runners
Expand Down
Loading