Skip to content

Commit

Permalink
Add CUDA tests to release pipeline.
Browse files Browse the repository at this point in the history
These run in compatibility-checking mode, meaning that they run tests which
are expected to fail and ensure that these tests still fail. This takes
even longer than when not checking this, so these run only as part of the
release pipeline.

PiperOrigin-RevId: 692355383
  • Loading branch information
EtiennePerot authored and gvisor-bot committed Jan 8, 2025
1 parent 2edcee3 commit 311b257
Showing 1 changed file with 19 additions and 6 deletions.
25 changes: 19 additions & 6 deletions .buildkite/release.yaml
Original file line number Diff line number Diff line change
@@ -1,15 +1,16 @@
agents:
queue: release
_templates:
retry_settings: &retry_settings
automatic:
- exit_status: -1
limit: 10
- exit_status: "*"
limit: 2
common: &common
timeout_in_minutes: 180
retry:
automatic:
- exit_status: -1
limit: 10
- exit_status: "*"
limit: 2

<<: *retry_settings
notify:
- email: "[email protected]"
if: build.state == "failed"
Expand Down Expand Up @@ -75,6 +76,18 @@ steps:
- make gpu-all-tests
agents:
queue: gpu
- label: ":fish: CUDA tests"
# This is its own test rather than being part of the GPU tests,
# because it takes around 30 minutes to run.
parallelism: 32
timeout_in_minutes: 120
retry:
<<: *retry_settings
commands:
- make sudo TARGETS=//tools/gpu:main ARGS="install --latest" || cat /var/log/nvidia-installer.log
- make cuda-tests ARGS="--cuda_verify_compatibility=true"
agents:
queue: gpu
- <<: *common
label: ":screwdriver: All GPU Drivers Test"
parallelism: 8
Expand Down

0 comments on commit 311b257

Please sign in to comment.