-
Notifications
You must be signed in to change notification settings - Fork 195
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
Attempt to unclog documentation builds on Buildkite #1561
Conversation
@mukund-gupta Maybe try this branch to see if it fixes the issue you encountered with this error: https://buildkite.com/clima/oceananigans/builds/1947#b5157111-6448-4db8-bc8b-8a777f85001a/19-300 |
6b2a92a
to
aed2138
Compare
Seems that many builds are not getting stuck on both CPU and GPU. I wonder if it's a new package version causing problems since this started happening after I updates the Manifest.toml. And the docs update Oceananigans.jl/.buildkite/pipeline.yml Line 326 in e027902
|
Can confirm that tests get stuck when I manually run
so presumably whatever is causing it to hang is a commonly used function/bit of code... |
When I killed it I got
so maybe we have a bad KernelAbstractions.jl |
Ah, interesting. I think you're right that it seems probable to be a KernelAbstractions thingy (but want to point out that Also explains why it mysteriously started happening due to auto update of |
I was able to reproduce the hanging by running the test manually in the REPL. It gets stuck somewhere in It does not hang in v0.54.0. I tried downgrading and pinning KernelAbstractions.jl and CUDA.jl back down to the version used in the v0.54.0 Manifest.toml but it still got stuck... Could be some other package.
Couldn't find anything in the Pkg.jl docs that would help but maybe we should switch the order of the Oceananigans.jl/.buildkite/pipeline.yml Line 326 in e027902
|
I notice that in the Documenter.jl Docs it's suggested: julia --project=docs/ -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate()' |
Here's the differences in how
The differences are:
|
@navidcy I think its a red herring. The issue is that the update of some package is causing |
Actually, I believe that @ali-ramadhan found that the issue is compilation of |
omg... I'm thoroughly confused. also, what is puzzling even more, is that on the list on the left (that you mention all is "ok") I see |
I see
https://github.com/JuliaGPU/CUDA.jl/blob/5767efb7fa65c3811b187ab310f0bb5e484bc2e4/Project.toml#L31 What does that mean? |
That's not v2.4.1... https://github.com/JuliaGPU/CUDA.jl/blob/v2.4.1/Project.toml (You were looking at v2.4.3) |
Touche. |
PencilFFTs 0.12.2 also requires AbstractFFTs v1: https://github.com/jipolanco/PencilFFTs.jl/blob/master/Project.toml |
Indeed....! But again the url you provided is from PencilFFTs#master and not v0.12.2... :) |
I'm simply confused with the whole shenanigans of this issue. I need a fresh start perhaps :) |
True, its still tagged as 0.12.2 but I guess the compat could have been updated without bumping the version. |
Nice. This might help our investigations. Will get to it tomorrow. |
Still also confused here... Just merged |
Wishful thinking.. |
Can close this now since #1573 ... |
No description provided.