-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add stats
/ destats
field to everything
#391
Conversation
Codecov Report
@@ Coverage Diff @@
## master #391 +/- ##
==========================================
- Coverage 52.25% 47.62% -4.63%
==========================================
Files 46 46
Lines 3554 3582 +28
==========================================
- Hits 1857 1706 -151
- Misses 1697 1876 +179
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
can we just do this to all now? |
Done |
stats
field to NonlinearSolutionstats
/ destats
field to everything
The DelayDiffEq failure seems unrelated |
@YingboMa should we just destats -> stats with a deprecation path in the getproperty? |
@YingboMa bump |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still need the destats -> stats depreciation
I bumped it to confirm if we wanted the deprecation. Will do that. |
The |
Let's make sure the ArrayInterface stuff is more done before breaking some tests again with this 😅 . Other than that, I think this is good to go. |
Is downstream all set? |
Let's not merge it yet. I will run some of the final tests today and
confirm.
…On Thu, Mar 2, 2023, 3:33 AM Christopher Rackauckas < ***@***.***> wrote:
Is downstream all set?
—
Reply to this email directly, view it on GitHub
<#391 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHJF57TCVQM5KWE5FNCLLZTW2BLONANCNFSM6AAAAAAU5A3QR4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Co-authored-by: David Widmann <devmotion@users.noreply.github.com>
The interface tests for ODE.jl are working locally & (Stochastic)DelayDiffEq.jl is also working. We should be good to go. |
This change broke ProbNumDiffEq.jl: By which I don't really mean to criticise, I'm not familiar enough with the API though to know if that's semver problem, I might also just be too reckless in ProbNumDiffEq.jl. I'm mostly wondering: Would it make sense to also add ProbNumDiffEq.jl to the integration tests to catch this stuff earlier? (maybe @ChrisRackauckas) EDIT: Actually I'm not sure where the issue is exactly, locally OrdinaryDiffEq.jl is the thing that fails, but I didn't have a thorough look yet. |
Everything should have a deprecation path? Let me know if there are still any missing, but I think I caught them all by now. |
No description provided.