CI: Block cupnumeric versionrange to have passing CI for now

Presumably rc2 (or the release) will have a fix, but I need to start merging some things and CI passing so... Signed-off-by: Sebastian Berg <[email protected]>
rapidsai · Jan 29, 2025 · c4f551f · c4f551f
1 parent 0ed6d65
commit c4f551f
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 2 deletions.
diff --git a/conda/recipes/legate-dataframe/conda_build_config.yaml b/conda/recipes/legate-dataframe/conda_build_config.yaml
@@ -22,5 +22,10 @@ cuda11_compiler:
 legate_version:
   - "=25.01.*,>=0.0.0.dev0"
 
+# TODO: The != temporary blocklist cupynumeric versions
+# using cupynumeric, because it is fewer versions to block.
+cupynumeric_version:
+  - "=25.01.*,>=0.0.0.dev0,!=62,!=61,!=60,!=rc1"
+
 rapids_version:
   - =24.12.*
diff --git a/conda/recipes/legate-dataframe/meta.yaml b/conda/recipes/legate-dataframe/meta.yaml
@@ -1,4 +1,4 @@
-# Copyright (c) 2024, NVIDIA CORPORATION.
+# Copyright (c) 2024-2025, NVIDIA CORPORATION.
 
 {% set pyproject_data = load_file_data("python/pyproject.toml") %}
 {% set version = environ['LEGATEDATAFRAME_PACKAGE_VERSION'] %}
@@ -60,7 +60,7 @@ requirements:
     # Only to ensure a nightly legate version we pick up
     # is compatible with an existing cupynumeric version.
     # (may also stabilize not using debug/sanitizer builds)
-    - cupynumeric
+    - cupynumeric {{ cupynumeric_version }}
     - python
     - pip
     - cython >=3.0.3