Skip to content

Allow SymbolicIntegrationMaxima 0.3 in the qa test environment - #146

Merged
ChrisRackauckas merged 3 commits into
JuliaSymbolics:mainfrom
s-celles:fix/maxima-qa-compat
Oct 14, 2026
Merged

ChrisRackauckas merged 3 commits into
JuliaSymbolics:mainfrom
s-celles:fix/maxima-qa-compat

Conversation

@s-celles

@s-celles s-celles commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

The qa group of the SymbolicIntegrationMaxima workflow fails before it runs a single
check:

ERROR: LoadError: empty intersection between SymbolicIntegrationMaxima@0.3.0 and project compatibility 0.2

lib/SymbolicIntegrationMaxima/test/runtests.jl activates test/qa and Pkg.develops the
local package into it, but test/qa/Project.toml still bounds the package under test at
"0.2" while #143 released it as 0.3.0.

This has failed on main since that release (run 35223647524), and every pull request that
merges current main inherits the two red qa jobs, which is how I ran into it on #136.

Widened to "0.2, 0.3", the same form #144 used for docs/Project.toml. The sibling bound
SymbolicIntegration = "3" is unaffected because it is a major-version bound; consider
whether 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:

Pkg.activate("lib/SymbolicIntegrationMaxima/test/qa")
Pkg.develop([PackageSpec(path = pwd()), PackageSpec(path = "lib/SymbolicIntegrationMaxima")])
  • before: empty intersection between SymbolicIntegrationMaxima@0.3.0 and project compatibility 0.2
  • after: resolves, develop OK

Assisted by: AI

CI

35 checks pass, 0 fail, on a813e81 — including the 11 qa jobs this pull request repairs
and all 11 difficult jobs.

An earlier run of the identical change reported 4 failures: Julia pre - ubuntu easy,
Julia 1 - macos difficult, Julia 1.10 - windows difficult and Julia 1 - ubuntu qa. All
four concluded failure while every one of their steps reported success or skipped, so
no 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 test
environment's Project.toml, which cannot reach a difficult job on macOS. Merging current
main re-ran the matrix on the same one-line change and it came back 35/0.

`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-commenter

codecov-commenter commented Sep 26, 2026 •

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.19%. Comparing base (8647f0d) to head (a813e81).
⚠️ Report is 29 commits behind head on main.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

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.
📢 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.

ChrisRackauckas and others added 2 commits October 7, 2026 10:05
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
@ChrisRackauckas
ChrisRackauckas merged commit 8b07ad4 into JuliaSymbolics:main Oct 14, 2026
35 checks passed
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.

4 participants