You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: isolate root QA into canonical test/qa sub-environment
Move the root package's Quality Assurance tests (Aqua + JET) into an
isolated test/qa/ Project so the QA tooling dependencies no longer enter
the main test target's resolve, matching the canonical OrdinaryDiffEq
lib/<Name>/test/qa/ structure.
- Add test/qa/Project.toml: deps Aqua, JET, Optimization, Test;
[sources] Optimization = {path = "../.."}; [compat] for each + julia 1.10.
- Move test/qa.jl -> test/qa/qa.jl (Aqua + JET tests preserved verbatim;
add `using Test` so the file is self-contained in the isolated env).
- runtests.jl: add activate_qa_env() (Pkg.activate(test/qa) + instantiate,
plus develop-by-path on Julia < 1.11 where [sources] is ignored). The QA
safetestset now runs last in the Core group after activating the qa env,
so the main-environment tests above are unaffected. CI dispatches only
GROUP=Core, so QA continues to run exactly as before.
- Remove Aqua and JET from the main Project.toml [extras], [targets].test,
and [compat]; they now live solely in the qa environment.
Verified on Julia 1.11 in an isolated depot: the qa env instantiates and
resolves (Aqua 0.8.16, JET 0.9.20, Optimization 5.6.1 via ../.., Test
1.11.0); the Aqua testset runs green (10/10 pass). No sublibrary runs QA
today (the three that list Aqua in [extras] never call it), so per the
preserve-existing-behavior rule none were given a qa env.
Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments