Fix wrong SafeTestsets UUID in [extras]#74
Merged
ChrisRackauckas merged 2 commits intoJun 16, 2026
Conversation
The [extras] entry for SafeTestsets used the UUID 1e83bf80-4336-4d27-bf5d-d5a4f845583c, which is actually StaticArraysCore's UUID. As a result Pkg mapped the name SafeTestsets to StaticArraysCore and applied the [compat] bound "0.0.1, 0.1" to StaticArraysCore (whose registered versions are 1.0.0 - 1.4.4), making the test environment unsatisfiable. This broke every test job (Core/NoPre across julia 1/lts/pre) and the Downgrade job on master. Use SafeTestsets' actual registered UUID 1bc83da4-3b8d-516f-aca4-4fe02f6d838f. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The NoPre group env pinned SafeTestsets to UUID 1e83bf80-... whose only registered versions are 1.0.0-1.4.4, which conflict with the `0.0.1, 0.1` compat bound, causing an Unsatisfiable resolve. The registered SafeTestsets UUID is 1bc83da4-..., matching the root test env (which passes). Verified locally: NoPre env now resolves and picks SafeTestsets v0.1.0. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Fix wrong
SafeTestsetsUUID in[extras]Master CI is red on every test job (Core julia 1/lts/pre, NoPre julia 1/lts) and on Downgrade with the same root cause:
Root cause
PR #73 ("Use SciMLTesting v1.2 folder-based run_tests") added
SafeTestsetsto[extras]with the wrong UUID:1e83bf80-4336-4d27-bf5d-d5a4f845583cis the UUID of StaticArraysCore, not SafeTestsets. Because the nameSafeTestsetswas mapped to StaticArraysCore's UUID, Pkg applied the[compat]boundSafeTestsets = "0.0.1, 0.1"to StaticArraysCore, whose only registered versions are1.0.0 - 1.4.4, making the test environment unsatisfiable.Fix
Use SafeTestsets' actual registered UUID:
Verification
Locally on Julia 1.10 (the package's compat floor),
Pkg.test()withGROUP=Corenow resolves the test environment and runs the suite (previously it failed instantly at resolution).Please ignore until reviewed by @ChrisRackauckas.