Skip to content

Release 0.9.2 - #616

Merged
michel2323 merged 5 commits into
masterfrom
release-0.9.2
May 20, 2026
Merged

Release 0.9.2#616
michel2323 merged 5 commits into
masterfrom
release-0.9.2

Conversation

@michel2323

@michel2323 michel2323 commented May 19, 2026

Copy link
Copy Markdown
Collaborator

I had to bump MadNLPGPU from 0.8.0 to 0.9.0 because of a CUDA dependency change 9 (-> weak deps).

Release notes draft:

MadNLP v0.9.2

Highlights: new SchurComplementKKTSystem for two-stage stochastic programs (CPU + GPU), an API cleanup so solver and wrapper internals are accessed through getter functions, and a MUMPS 5.8.x fix.

New features

  • Add SchurComplementKKTSystem for exploiting the block-arrowhead structure of two-stage stochastic programs. Reduces each Newton step to a dense nd × nd design-variable system via per-scenario eliminations. CPU variant uses Umfpack for the per-scenario blocks by default; GPU variant lives in the MadNLPGPU CUDA extension and uses batched cuDSS + strided-batched CUBLAS. (Add SchurComplementKKTSystem for two-stage stochastic programs #598)

API changes

Fixes

Documentation


MadNLPGPU v0.9.0

Highlights: CUDA/CUDSS and AMDGPU are now weak dependencies, and the new Schur-complement KKT system has a GPU backend.

Known issue — V100 / Volta (sm_70):
CUDA Toolkit 13 dropped support for Volta GPUs. Starting at CUDA.jl v5.10 (March 2026), Pkg may resolve to a CUDA.jl that auto-selects the CUDA 13 runtime, which then fails on V100. MadNLPGPU's compat allows this. Until JuliaGPU/CUDA.jl#3134 ships in a tagged release, V100 users should pin to a CUDA 12.x toolkit by running once per environment:

using CUDA
CUDA.set_runtime_version!(v"12.9")    # any 12.x works

Alternatively, pin CUDA = "~5.9" in your project's Project.toml.


MadNLPTests v0.6.1

@codecov

codecov Bot commented May 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.63%. Comparing base (f99a4ad) to head (5298883).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #616   +/-   ##
=======================================
  Coverage   85.63%   85.63%           
=======================================
  Files          52       52           
  Lines        4880     4881    +1     
=======================================
+ Hits         4179     4180    +1     
  Misses        701      701           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

CUDA Toolkit 13 dropped sm_70 (Volta), so without pinning,
CUDA_Runtime_jll may auto-select a runtime that fails on the
self-hosted V100 runner. Remove this once JuliaGPU/CUDA.jl#3134
ships in a tagged release.
@michel2323
michel2323 merged commit fc788cb into master May 20, 2026
18 of 19 checks passed
@KSepetanc

KSepetanc commented May 21, 2026

Copy link
Copy Markdown
Contributor

Can you check, something is wrong for MadNLPGPU. Installation fails on clean 1.12 env (simple add MadNLPGPU#master). Is it related to changes here?

Failed to precompile MadNLPGPU [d72a61cc-809d-412f-99be-fd81f4b8a598] to "C:\\Users\\karlo\\.julia\\compiled\\v1.12\\MadNLPGPU\\jl_AC1F.tmp".
WARNING: Imported binding MadNLP.populate_RR_nn! was undeclared at import time during import to MadNLPGPU.
WARNING: Imported binding MadNLP.count_lu_bounds was undeclared at import time during import to MadNLPGPU.
ERROR: LoadError: invalid method definition in MadNLPGPU: exported function MadNLP.count_lu_bounds does not exist

Edit: MadNLPGPU 0.9 was not in registry and 0.10 produces the above error.

@KSepetanc

Copy link
Copy Markdown
Contributor

I see releases go in tandem thus above error.

Please put MadNLPGPU 0.9 in registry (bot did not do it).

@frapac
frapac deleted the release-0.9.2 branch July 23, 2026 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants