Skip to content

fix(runtime): target SolverForge 0.26.0 and build Furnace tests with debug info - #7

Merged
blackopsrepl merged 2 commits into
mainfrom
fix/target-solverforge-0.26.0
Nov 10, 2026
Merged

blackopsrepl merged 2 commits into
mainfrom
fix/target-solverforge-0.26.0

Conversation

@blackopsrepl

Copy link
Copy Markdown
Contributor

Closes #6. Two commits: bundle retarget to 0.26.0 (only SolverForge packages move in each lockfile), then Furnace's no-debug dev profile removed. Gates on this tree against the published 0.26.0: make ci-local EXIT 0; make pre-release EXIT 0 for all eight apps (Furnace's tests ran with debug info: 78+3 passed, slow feasible solve passed).

SolverForge 0.26.0 changes only solverforge-scoring's replica-director
construction, which no app names, and keeps debug-info type names
proportional to the constraint set. Every app now requests and locks the
0.26.0 crates, and its app metadata, README and WIREFRAME name the new
runtime target.
The no-debug dev profile existed because debug info for the test binary
spelled every generic instantiation over the full constraint-set type:
2.82 GB of strings with line tables only and an 8 MB longest name, beyond a
DWARF32 link. SolverForge 0.26.0 keeps those names proportional to the
model (0.37 GB, 1.0 MB longest; with full debug info the test binary links
and passes), so the default dev profile applies again.

Closes #6
@blackopsrepl
blackopsrepl merged commit e93572d into main Nov 10, 2026
2 checks passed
@blackopsrepl
blackopsrepl deleted the fix/target-solverforge-0.26.0 branch November 10, 2026 11:43
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.

fix(runtime): target SolverForge 0.26.0 and drop Furnace's no-debug test profile

1 participant