Description
The nightly-numba-cuda-mlir install path currently adds numpy<2.5 in ci/tools/run-tests. The ci-nightly.yml jobs select that install path through the nightly-numba-cuda-mlir test mode.
The constraint was introduced in #2283 as a workaround for NVIDIA/numba-cuda-mlir#154: numba-cuda-mlir 0.3.0 and 0.4.0 tried to register np.row_stack, which NumPy 2.5 removed. NVIDIA/numba-cuda-mlir#146 fixed the version guard, and the fix shipped in numba-cuda-mlir v0.4.1.
The nightly install does not pin numba-cuda-mlir to 0.4.0; it installs a compatible release and then checks out the matching release tag to run its tests. We should try removing the NumPy cap so this nightly lane exercises current NumPy releases again.
xref: this was discovered in while working on nvbug 6665297
Proposed change
- Remove only the
"numpy<2.5" argument and its associated workaround comment from the nightly-numba-cuda-mlir branch in ci/tools/run-tests.
- Leave the separate
nightly-numba-cuda path and all other dependency constraints, skips, and test commands unchanged. This change does not assert NumPy 2.5 compatibility for the legacy numba-cuda package.
Validation
- Run all currently configured
nightly-numba-cuda-mlir jobs: Python 3.12 on Linux and Windows with CUDA 12.9.1 and 13.3.0.
- Confirm the existing package listing shows NumPy 2.5 or newer and
numba-cuda-mlir 0.4.1 or newer.
- Compare with the current nightly baseline and confirm there is no
np.row_stack error or other new NumPy-related failure; this experiment need not resolve unrelated existing failures.
- If a job exposes a real remaining incompatibility, record the resolved package versions and failure, then add back only the narrowest justified constraint with an upstream reference.
Description
The
nightly-numba-cuda-mlirinstall path currently addsnumpy<2.5inci/tools/run-tests. Theci-nightly.ymljobs select that install path through thenightly-numba-cuda-mlirtest mode.The constraint was introduced in #2283 as a workaround for NVIDIA/numba-cuda-mlir#154:
numba-cuda-mlir0.3.0 and 0.4.0 tried to registernp.row_stack, which NumPy 2.5 removed. NVIDIA/numba-cuda-mlir#146 fixed the version guard, and the fix shipped innumba-cuda-mlirv0.4.1.The nightly install does not pin
numba-cuda-mlirto 0.4.0; it installs a compatible release and then checks out the matching release tag to run its tests. We should try removing the NumPy cap so this nightly lane exercises current NumPy releases again.xref: this was discovered in while working on nvbug 6665297
Proposed change
"numpy<2.5"argument and its associated workaround comment from thenightly-numba-cuda-mlirbranch inci/tools/run-tests.nightly-numba-cudapath and all other dependency constraints, skips, and test commands unchanged. This change does not assert NumPy 2.5 compatibility for the legacynumba-cudapackage.Validation
nightly-numba-cuda-mlirjobs: Python 3.12 on Linux and Windows with CUDA 12.9.1 and 13.3.0.numba-cuda-mlir0.4.1 or newer.np.row_stackerror or other new NumPy-related failure; this experiment need not resolve unrelated existing failures.