From 0a336ea123fc5c6365b21572d1a1324edf946367 Mon Sep 17 00:00:00 2001 From: "Ralf W. Grosse-Kunstleve" Date: Wed, 23 Sep 2026 21:35:31 -0700 Subject: [PATCH] test: tolerate unsupported NVML clock offsets on new GPUs NVML can reject offsets for a clock domain such as memory on GB300 even when the GPU architecture is recent. Treat that capability as optional in test_clock. Addresses nvbug 6814458. --- cuda_core/tests/system/test_system_device.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/cuda_core/tests/system/test_system_device.py b/cuda_core/tests/system/test_system_device.py index 278719b3a1b..56e6aede2f3 100644 --- a/cuda_core/tests/system/test_system_device.py +++ b/cuda_core/tests/system/test_system_device.py @@ -671,9 +671,9 @@ def test_clock(subtests): assert isinstance(current_mhz, int) assert current_mhz >= 0 - # Docs say this should work on PASCAL or newer, but experimentally, - # is also unsupported on other hardware. - with unsupported_before(device, DeviceArch.MAXWELL): + # Clock offsets can be unsupported for individual clock domains + # even on newer devices (for example, memory clocks on GB300). + with unsupported_before(device, None): try: offsets = clock.get_offsets(pstate) except (system.InvalidArgumentError, system.NotFoundError):