Refresh IntervalNonlinearProblem under v7 stack#1583
Conversation
4c87165 to
18724e0
Compare
- Remove stale `# CI retrigger: v7 stack outputs (2026-05-15)` marker left in `Project.toml` from the batch-1 merge (SciML#1558). - Refresh `Manifest.toml` via `Pkg.update()` on Julia 1.11. Bumps: Adapt 4.5.2->4.6.0, ArrayInterface 7.24.0->7.25.0, ConcreteStructs 0.2.3->0.2.4, DifferentiationInterface 0.7.17->0.7.18, JLLWrappers 1.7.1->1.8.0, NonlinearSolveBase 2.25.0->2.26.0, RuntimeGeneratedFunctions 0.5.18->0.5.19, SafeTestsets (+0.1.0), SciMLBase 3.7.1->3.13.0, SciMLLogging 1.9.1->2.0.0, SciMLOperators 1.17.0->1.21.0, SymbolicIndexingInterface 0.3.46->0.3.48, Git_LFS_jll 3.7.0+0->3.7.1+0. - `.jmd` sources scanned: no v7 migration patterns (Bool autodiff/verbose, precs=, sol[i], ensemble prob_func arity) present; no edits needed. - Smoke-tested `weave_file(..., (:script,))` for both `simpleintervalrootfind.jmd` and `suite.jmd` -- both OK. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
18724e0 to
567619f
Compare
The benchmark failed with: ERROR: UndefVarError: `Bisection` not defined in `Main.var"##WeaveSandBox#232"` because Roots.jl, BracketingNonlinearSolve.jl, and SimpleNonlinearSolve.jl all export `Bisection`, making the binding ambiguous after the second chunk loads BracketingNonlinearSolve/SimpleNonlinearSolve alongside the already-loaded Roots. Resolve it with an explicit `using BracketingNonlinearSolve: Bisection`, matching the workaround already used in suite.jmd. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
CI fix pushed in be41aea. Root cause (from job 80471540571, Chunk 1 loads Change: added Verified locally by running the full chunk-1 + chunk-2 code sequence (with reduced N) in the benchmark's vendored Project/Manifest environment on Julia 1.11.8 — The push retriggered the Benchmarks workflow: https://github.com/SciML/SciMLBenchmarks.jl/actions/runs/27267411961 |
Ignore until reviewed by @ChrisRackauckas.
Summary
Single-folder refresh of
benchmarks/IntervalNonlinearProblem/under the v7 stack.# CI retrigger: v7 stack outputs (2026-05-15)comment that batch-1 (Retrigger v7 outputs for 5 cancelled folders (batch 1) #1558) left at the bottom ofProject.toml. No new retrigger markers introduced..jmdsources: scannedsimpleintervalrootfind.jmdandsuite.jmdfor the v7 migration patterns (Boolautodiff/verbose,precs=,sol[i], ensembleprob_funcarity, SymbolicUtils 4.26->4.30.x). None present -- no edits needed.Manifest.toml: refreshed viaPkg.update()on Julia 1.11. Bumps:SciMLBenchmarks.weave_file(..., (:script,))succeeded for bothsimpleintervalrootfind.jmdandsuite.jmd.Test plan
.jmdfiles end-to-end on the v7 stack.🤖 Generated with Claude Code