-
Notifications
You must be signed in to change notification settings - Fork 89
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
Update to new API #169
Update to new API #169
Conversation
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.
Tests pass on this branch if I add the corresponding branches
(ChainRules) pkg> add ChainRulesTestUtils#wct/frule-api-fix
(ChainRules) pkg> add ChainRulesCore#wct/frule-api-fix
so seems good to me, once the other PRs are merged and tagged and the compat here updated
Co-Authored-By: Nick Robinson <[email protected]>
Co-Authored-By: Nick Robinson <[email protected]>
Co-Authored-By: Nick Robinson <[email protected]>
…nRules.jl into wct/frule-api-fix
@nickrobinson251 let me know if you're happy for this to be merged now. |
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.
LGTM. Just need CI to pass before merge / your other PRs merged and tagged first.
Thanks for your work on this!
.travis.yml
Outdated
@@ -10,7 +10,6 @@ julia: | |||
- nightly |
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.
- nightly | |
- 1.4 |
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.
It is worrying how few tests needed to be updated
Yeah. This is what caused this slip up with the API in the first place -- we simply didn't have the range of things implemented to catch the problem. I think that the right place to resolve this issue is the core though -- I've implemented extra tests to prevent API regression, but presumably there are other things we're not handling properly (kwargs, for example). |
@oxinabox @nickrobinson251 anyone able to reproduce the errors locally? Tests are passing for me on 1.3.1. Have checked versions, and I appear to be using the same as CI is using... |
Oh is this: #149 ? I think we had travis disabled on 1.3 for reasons because it was just broken even though it worked fine in 1.3 on everyones local machines |
Ahh I see. Will re-disable and merge once tests pass. |
See ChainRulesCore for related PR