Adapt to Symbolics v6.1; allow SetProg v0.4 in tests #3637
Merged
Conversation
This file contains 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
schillic
force-pushed
the
schillic/setprog
branch
from
e397c7e
to
465bd92
Compare
schillic
changed the title
schillic
force-pushed
the
schillic/setprog
branch
from
465bd92
to
65eb3ed
Compare
schillic
changed the title
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.
Closes #3634.
Closes #3635.
Closes #3636.
Somehow, the dependency resolver is broken.Still odd, but not relevant anymore.Symbolicsv5.30.4 is not compatible withSymbolicUtilsv2.1, but for some reason, these versions are still installed together on the test run. Looks like a bug inPkgto me...The documentation run is broken because the new package versions are not yet visible to it (old problem). The run passed locally.