-
Notifications
You must be signed in to change notification settings - Fork 259
CI with Julia v1.11 #3836
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
CI with Julia v1.11 #3836
Conversation
I installed julia 1.11 on the Caltech cluster, but we haven't made a module yet (but it's coming today or so) |
There's only one manifest? |
I assume he's referring to this new feature of Julia 1.11: https://julialang.org/blog/2024/10/julia-1.11-highlights/#manifest_versioning |
The PR adds another Manifest specifically for v1.11 and keeps the older Manifest that works for v1.10. Or we can just have one Manifest (the one for v1.11) and drop the one for v1.10 |
The Manifest was deleted in #3783 |
|
oh great! I missed that! |
Deleting it seemed to help increase the likelihood that CI passed. Although, it did not fully solve the problem (and note a few other changes were also made on #3783). |
|
Noting that internal_tide.jl gives NaN with Julia v1.11 while all is OK with Julia v1.10; something with immersed boundaries....? I'm looking into it. |
|
I think it's a plotting issue. We are filling up the immersed boundaries with NaN and, apparently, we cannot plot NaNs anymore? The error says: ERROR: LoadError: On worker 2:
| Looking up a non-finite or NaN value in a colormap is undefined. |
|
I ran the script and the actual simulation NaN-ed. |
That means Oceanangians isn't compatible with julia 1.11. Do any other tests catch the issue? We can use this opportunity to add more tests. |
|
I’m trying to make an mwe |
|
@glwagner, note that the ocean mixing example NaNs.... |
|
Since Debugger.jl seems to have started working with Julia 1.11 (JuliaDebug/Debugger.jl#361) I thought I should take another look here. But with Julia 1.11.6 all the examples seem to run just fine. I built the docs and ran all the examples, and the outputs all look good. So maybe no examples are blowing up anymore? Looking at a recent-ish test build, if the docs will build now then it's just an Enzyme test failure plus a few test failures (see #4663 (comment)) that might be fixed by #4734 (tentatively)? I'll run the full test suite locally with Julia 1.11 (with and without this potential fix: #4663 (comment)) and report back. |
Are you on ubuntu? I believe the errors only manifest on ubuntu (possibly only on CPU). I'd expect them to get fixed eventually though. |
I ran the examples locally on Arch Linux / EndeavourOS (where the examples have NaNed before). The tests are currently running on Debian. Curious why it would be specific to a Linux distro. |
Yes, this is the question of the hour! |
|
Not sure if it is something relevant, but this was giving me a bounds error in julia 1.11 |
|
Got pretty far in before Maybe it will be easier to run tests for Julia 1.10 + 1.11 (CPU + GPU) once CI is back online (hopefully next week!). |
|
This is worth trying again now that CUDA.jl v5.8.4 is out which should fix some of the GPU failures on Buildkite. |
* Update CI to Julia version to 1.12.0 * try increasing reactant compact * try without reactant * just run the docs * bugfix * Change grid bottom function to GridFittedBottom * Update warning for Julia version compatibility * take up the changes in #3836 * try without distributed * imports alphabetically * use a local accumulator and reinstate tests * reinstate all tests * white line * reinstate distributed examples * Update KernelAbstractions version to 0.9.39 * Disable doctest temporarily * Update pipeline.yml * separate out reactant and enzyme tests * try like this * don't need to make the new directory * fixing * use a new key * need to create the new folder * mv manifest to new version * Update .buildkite/pipeline.yml Co-authored-by: Mosè Giordano <[email protected]> * [CI] Automatically create version-specific manifests * enzyme on 1.10 * whyt would / not compile? meybe because of / 0? * try removing internal closures * this should do the trick * up to six operands * Update make.jl * Apply suggestion from @simone-silvestri * Apply suggestion from @simone-silvestri * Apply suggestion from @simone-silvestri * another bugfix --------- Co-authored-by: Simone Silvestri <[email protected]> Co-authored-by: Gregory L. Wagner <[email protected]> Co-authored-by: Mosè Giordano <[email protected]>
|
Superseded by #4836! |
This PR switches the CI to use Julia v1.11.
It also adds a Manifest with
v1.11ending so that there is still compatibility with previous versions.Note the the distributed CI still does not have Julia v1.11 (right @Sbozzolo?) so there Julia v1.10 is used. This is possible because there are two Manifests.