Raise FIRK/MIRK downgrade compat floors - #540
Merged
ChrisRackauckas merged 1 commit intoJul 11, 2026
Merged
Conversation
Contributor
Benchmark Results (Julia v1.11)Time benchmarks
Memory benchmarks
|
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
ChrisRackauckas-Claude
force-pushed
the
fix-sublib-scimlbase-compat-downgrade
branch
from
July 11, 2026 13:56
e4edaad to
e7b6a52
Compare
ChrisRackauckas
marked this pull request as ready for review
July 11, 2026 23:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ignore this PR until reviewed by @ChrisRackauckas.
Summary
SciMLBasecompat inBoundaryValueDiffEqFIRKandBoundaryValueDiffEqMIRKfrom3to3.30so the sublibraries match the in-treeBoundaryValueDiffEqCorefloor.LinearSolve4.2in the same sublibraries; after theSciMLBasefloor is fixed, the downgrade resolver can otherwise hit an empty intersection withLinearSolve v4.2.1.Evidence
SciMLBase v3.0.0while the path dependencyBoundaryValueDiffEqCorerequiresSciMLBase >= 3.30.SciMLBasefloor exposed the next resolver conflict:LinearSolve@4.2.1was incompatible withLinearSolve = "2.36.2, 3".Pkg.test(...; force_latest_compatible_version=false, allow_reresolve=false)instantiated withSciMLBase v3.35.1andLinearSolve v4.2.1, so the resolver failure is gone.Pkg.test(...; force_latest_compatible_version=false, allow_reresolve=false)also got past resolution and reached the known MIRK Dual runtime failures fixed separately in Fix MIRK extrema boundary conditions under AD #542.Local verification
git diff --checkpassed.Pkg.testwith Julia 1.10 andBOUNDARYVALUEDIFFEQ_TEST_GROUP=Coreno longer failed at resolution. It completedFIRK Expanded Basic Tests | 234 pass, 20 broken, 254 totalin81m17.4s, then timed out after 2 hours intest/nested/firk_basic_tests.jlwithout anError During Testmarker before termination. I am not claiming the full FIRK downgraded package test passes locally.Pkg.testwith Julia 1.10 no longer failed at resolution. It reported the expectedFloat64(::ForwardDiff.Dual)failures inmirk.jl:338(Swirling Flow III, big-defect interpolant, max/min solution), which are covered by Fix MIRK extrema boundary conditions under AD #542, then timed out after 1 hour. I am not claiming MIRK passes locally from this PR alone.