[BUG] cuOpt 26.8.0 CU13 build aborts on MIP solves while CU12 solves the same instance

Describe the bug

Attempting to solve an lp file MIP instance results in a bug with CU13 while it solves as expected with the CU12 version, using an NVIDIA RTX PRO 500 Blackwell Generation Laptop GPU.

CUDA Error: /__w/cuopt/cuopt/cpp/src/barrier/sparse_cholesky.cuh:185:one or more resources are insufficient or non-applicable for the operation
CUDA Error: /__w/cuopt/cuopt/cpp/src/barrier/sparse_cholesky.cuh:205:one or more resources passed in are not valid resource types for the operation

Steps/Code to reproduce bug

Download a toy problem instance and decompress the file (also attached): https://github.com/ZIB-AOPT/QOBLIB/blob/main/05-sports/instances/Small/Addition_000_Small.xml.gz

Install cuopt-CU12:

pip install --extra-index-url=https://pypi.nvidia.com 'libcuopt-cu12==26.8.*'

Install cuopt-CU13:

pip install --extra-index-url=https://pypi.nvidia.com 'libcuopt-cu13==26.8.*'

Invoke the bug under version CU13 (see attachments for mps file):

cuopt_cli /home/david/Downloads/Addition_000_Small.lp

Expected behavior
CU13 build should solve the instance, without resulting in the CUDA error described above.

Environment details (please complete the following information):

• Environment location: Bare-metal
• Method of cuOpt install: pip (NVIDIA package index)
  • cuopt-cu13==26.8.0, libcuopt-cu13==26.8.0 (also nvidia-cudss-cu13==0.7.1.6), version 26.8.0, git hash 400863c1, reports CUDA 13.3
  • OS: Ubuntu 24.04.4, x86_64, Python 3.12.3
  • CPU: Intel Core Ultra 7 366H, 16 threads, 30.91 GiB RAM
  • GPU: NVIDIA RTX PRO 500 Blackwell Generation Laptop GPU, compute capability 12.0 (sm_120), driver 580.173.02 (CUDA 13.0 driver), 6113 MiB VRAM (5.54 GiB usable per cuOpt)

Additional context
The MIP root seems to ignore --method (it always runs concurrent), so --method 1/--method 3 do not avoid the crash for MIPs. Perhaps a flag to disable concurrent solve could be added?

Addition_000_Small.xml.gz