Use ADTypes in tests #1122
Merged
Use ADTypes in tests #1122
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
devmotion
force-pushed
the
dw/adtypes_tests
branch
from
f3ffba4 to
9dba5a4
Compare
ChrisRackauckas
approved these changes
Mar 4, 2025
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.
I noticed test failures in SciML/OrdinaryDiffEq.jl#2617 due to incorrectly specified
diff_typein the GPU tests -Val{:central}should beVal(:central)etc. This also showed up in recent buildkite runs on the DiffEqBase master branch: https://buildkite.com/julialang/diffeqbase-dot-jl/builds/1952#019513f2-5ba8-4380-bcb7-b047e9198da3/324-1050Instead of fixing the
diff_types, I assumed it would be more future-proof to switch the tests to ADTypes (and hence only specifyautodiff).