-
Notifications
You must be signed in to change notification settings - Fork 6
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
Zygote 0.6.41 breaks the tests #135
Comments
Maybe the same as FluxML/Zygote.jl#1240 (comment)? |
Interestingly, this linked Zygote issue seems to present only on Julia nightly, so some change on the Julia master branch must be responsible for it. |
Did you check if tests pass with 1.6 and 1.7? |
Not yet, but maybe you could just re-run the CI for the last commit on master. |
Julia 1.6 and 1.7 pass the tests with Zygote 0.6.41. |
So it really seems to be the upstream issue. Probably easiest to not use Julia 1.8 for now but of course that's not a good long term solution 😄 |
Ah, is passing the tests for Julia 1.8 not required for PRs in Zygote to be merged? It seems that this would have been caught by having a must-pass CI run for 1.8.0-rc1. |
No, tests don't have to pass with unreleased versions/Julia master. I assume things would just be broken too often, that's at least what I observed in Turing and other packages that make use of AD, compiler tricks, etc. |
I think this makes perfect sense for the nightly build. But for the release candidate I think it would make sense to be testing already and making sure that new additions are already compatible to be fully ready once it is released, plus potentially allowing to discover more bugs in Julia before it is released. Otherwise as soon as it is released your current release of Zygote is going to be broken (as the CI for version '1' will now be pointing to 1.8). |
When I re-run the tests locally with the most recent Zygote version, the above error no longer occurs. |
Tested on Julia 1.8-rc1.
Pinning Zygote to 0.6.40 passes all tests.
The text was updated successfully, but these errors were encountered: