Repository navigation
Allow SymbolicIntegrationMaxima 0.3 in the qa test environment - #146
Merged
ChrisRackauckas merged 3 commits intoOct 14, 2026
Merged
Conversation
`lib/SymbolicIntegrationMaxima/test/qa/Project.toml` still bounds the package under test at `"0.2"`, while JuliaSymbolics#143 released it as 0.3.0. The qa group activates that environment and `Pkg.develop`s the local copy, so resolution fails before any check runs: empty intersection between SymbolicIntegrationMaxima@0.3.0 and project compatibility 0.2 The SymbolicIntegrationMaxima workflow has failed on `main` since that release, and every pull request that merges current `main` inherits the two red `qa` jobs. Widened to `"0.2, 0.3"`, matching what JuliaSymbolics#144 did for `docs/Project.toml`. The sibling bound `SymbolicIntegration = "3"` does not have the problem because it is a major-version bound. Assisted-by: AI
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #146 +/- ##
==========================================
+ Coverage 50.98% 51.19% +0.21%
==========================================
Files 23 23
Lines 4309 4213 -96
==========================================
- Hits 2197 2157 -40
+ Misses 2112 2056 -56 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Sep 26, 2026
s-celles-bot
force-pushed
the
fix/maxima-qa-compat
branch
2 times, most recently
from
September 27, 2026 07:19
2e36073 to
3f576ce
Compare
Bring in JuliaSymbolics#147 so the difficult CI baseline matches current main; the qa compat fix itself is unchanged. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Cursor Agent <noreply@cursor.com> Agent-Harness: Cursor Agent CLI Agent-Model: auto
Brings the branch up to date with main through JuliaSymbolics#154, and gets a fresh CI run. On the previous run, four jobs — `Julia pre - ubuntu easy`, `Julia 1 - macos difficult`, `Julia 1.10 - windows difficult` and `Julia 1 - ubuntu qa` — concluded `failure` while every one of their steps reported `success` or `skipped`, i.e. with no failing step at all. That is an infrastructure failure rather than a result: this branch only widens a `[compat]` bound inside a test environment's Project.toml, which cannot affect a `difficult` job on macOS. Assisted-by: AI
Merged
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.
The
qagroup of theSymbolicIntegrationMaximaworkflow fails before it runs a singlecheck:
lib/SymbolicIntegrationMaxima/test/runtests.jlactivatestest/qaandPkg.develops thelocal package into it, but
test/qa/Project.tomlstill bounds the package under test at"0.2"while #143 released it as 0.3.0.This has failed on
mainsince that release (run 35223647524), and every pull request thatmerges current
maininherits the two redqajobs, which is how I ran into it on #136.Widened to
"0.2, 0.3", the same form #144 used fordocs/Project.toml. The sibling boundSymbolicIntegration = "3"is unaffected because it is a major-version bound; considerwhether this one should track major versions too, so it stops breaking on every 0.x release.
Verification
Running the exact sequence from
runtests.jl, on Julia 1.13.0:empty intersection between SymbolicIntegrationMaxima@0.3.0 and project compatibility 0.2developOKAssisted by: AI
CI
35 checks pass, 0 fail, on
a813e81— including the 11qajobs this pull request repairsand all 11
difficultjobs.An earlier run of the identical change reported 4 failures:
Julia pre - ubuntu easy,Julia 1 - macos difficult,Julia 1.10 - windows difficultandJulia 1 - ubuntu qa. Allfour concluded
failurewhile every one of their steps reportedsuccessorskipped, sono step had failed — the signature of an infrastructure failure rather than a result. That is
also what the scatter implied: this branch only widens a
[compat]bound inside a testenvironment's
Project.toml, which cannot reach adifficultjob on macOS. Merging currentmainre-ran the matrix on the same one-line change and it came back 35/0.