-
Notifications
You must be signed in to change notification settings - Fork 31
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
Call for volunteers to test the updated NetCDF v4.8.1 (in particular for Windows and Apple users) #165
Comments
Hi Alex, if time allows I'll give it a try with Windows. |
To just test the pre-compiled binares, you do not need to have MinGW. MinGW is (only) necessary to compile the C code. |
Thanks for your efforts! I followed the steps on Windows, but unfortunately I still get hit by the same issue. Just like with the previous version, it loads fine, and can create NC3 fine, but not NC4 (HDF5). You can see from the DLL name and version that it is picking up the new one you built.
(rest of the stacktrace)``` NC_create at C:\Users\visser_mn\.julia\dev\NCDatasets\dev\prefix\bin\libnetcdf-19.dll (unknown line) nc__create at C:\Users\visser_mn\.julia\dev\NCDatasets\dev\prefix\bin\libnetcdf-19.dll (unknown line) nc_create at C:\Users\visser_mn\.julia\dev\NCDatasets\dev\prefix\bin\libnetcdf-19.dll (unknown line) nc_create at C:\Users\visser_mn\.julia\packages\NCDatasets\TCrQh\src\netcdf_c.jl:255 unknown function (ip: 0000000060b0dc3d) #NCDataset#12 at C:\Users\visser_mn\.julia\packages\NCDatasets\TCrQh\src\dataset.jl:201 NCDataset at C:\Users\visser_mn\.julia\packages\NCDatasets\TCrQh\src\dataset.jl:157 #NCDataset#13 at C:\Users\visser_mn\.julia\packages\NCDatasets\TCrQh\src\dataset.jl:218 jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined] do_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:713 NCDataset at C:\Users\visser_mn\.julia\packages\NCDatasets\TCrQh\src\dataset.jl:218 jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined] do_call at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:126 eval_value at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:215 eval_body at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:461 eval_body at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:516 eval_body at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:516 jl_interpret_toplevel_thunk at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:731 jl_toplevel_eval_flex at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:885 jl_toplevel_eval_flex at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:830 jl_toplevel_eval at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:894 [inlined] jl_toplevel_eval_in at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:944 eval at .\boot.jl:373 [inlined] include_string at .\loading.jl:1196 _include at .\loading.jl:1253 include at .\client.jl:451 jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined] do_call at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:126 eval_value at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:215 eval_stmt_value at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:166 [inlined] eval_body at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:583 jl_interpret_toplevel_thunk at /cygdrive/c/buildbot/worker/package_win64/build/src\interpreter.c:731 jl_toplevel_eval_flex at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:885 jl_toplevel_eval_flex at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:830 jl_toplevel_eval_flex at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:830 jl_toplevel_eval at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:894 [inlined] jl_toplevel_eval_in at /cygdrive/c/buildbot/worker/package_win64/build/src\toplevel.c:944 eval at .\boot.jl:373 [inlined] eval_user_input at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\REPL\src\REPL.jl:150 repl_backend_loop at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\REPL\src\REPL.jl:246 start_repl_backend at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\REPL\src\REPL.jl:231 #run_repl#47 at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\REPL\src\REPL.jl:364 run_repl at C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.7\REPL\src\REPL.jl:351 #930 at .\client.jl:394 jfptr_YY.930_36349.clone_1 at C:\Users\visser_mn\.julia\juliaup\julia-1.7.2+0~x64\lib\julia\sys.dll (unknown line) jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined] jl_f__call_latest at /cygdrive/c/buildbot/worker/package_win64/build/src\builtins.c:757 #invokelatest#2 at .\essentials.jl:716 [inlined] invokelatest at .\essentials.jl:714 [inlined] run_main_repl at .\client.jl:379 exec_options at .\client.jl:309 _start at .\client.jl:495 jfptr__start_21275.clone_1 at C:\Users\visser_mn\.julia\juliaup\julia-1.7.2+0~x64\lib\julia\sys.dll (unknown line) jl_apply at /cygdrive/c/buildbot/worker/package_win64/build/src\julia.h:1788 [inlined] true_main at /cygdrive/c/buildbot/worker/package_win64/build/src\jlapi.c:559 jl_repl_entrypoint at /cygdrive/c/buildbot/worker/package_win64/build/src\jlapi.c:701 mainCRTStartup at /cygdrive/c/buildbot/worker/package_win64/build/cli\loader_exe.c:42 BaseThreadInitThunk at C:\WINDOWS\System32\KERNEL32.DLL (unknown line) RtlUserThreadStart at C:\WINDOWS\SYSTEM32\ntdll.dll (unknown line) Allocations: 8319222 (Pool: 8314332; Big: 4890); GC: 10 ```
The testing can just be done in Windows. MinGW is used for building the library. Environment info
|
Thanks a lot for the quick feedback. I will try to activate debug information in the builds. Maybe we will get line numbers with the error stack traces. |
Here is a link with the libraries with debug information: |
Now with line numbers!
|
The tarball also contains nccopy.exe. I am wondering if we get also an error when we use:
(probably all *.dll files need to be in the same folder next to the binary on Windows) |
I tried to setup a CI test and it seem to work when I downgrade HDF5_jll to 1.12.0 on Windows. Binaries are in: https://github.com/Alexander-Barth/NCDatasets.jl/runs/5403552073?check_suite_focus=true |
Ah yes, if I download this latest debug build, and |
Thanks for pushing this. I tested it on Ubuntu and it works. |
@visr Yes, this seems to be a HDF5_jll issue (unfortunately, only HDF5_jll 1.12.1 supports Apple M1). @felixcremer Thanks for checking and reporting back! |
I cannot get any of the executables to produce any output, they all return directly. I tried copying either version of the HDF5_jll DLLs into the same directory but it doesn't help. Probably other DLLs bundled with Julia or HDF5_jll dependencies are needed as well. That makes these zips hard to test outside of julia. To use them from inside julia they should be added as It would be easier to test these builds if we didn't only have the tarballs, but also the JLL package. Did you know that it is possible to create these locally with https://docs.binarybuilder.org/stable/building/#Building-a-custom-JLL-package-locally |
I did not know about the I did not realize that the exe files in the tar balls cannot be (easily) used. If somebody has an idea how to get Windows support back, one can generate the binaries with the following command (after cloning Yggdrasil
Testing in julia is indeed much easier as one can install it via |
Closing this issue in favor of : |
I updated NetCDF to v4.8.1 and I would like to have some feedback in particular from Windows and Apple users (x86_64 and M1 (also called aarch64)). Currently Windows support is broken in NetCDF_jll.
Does somebody volunteer to test the NetCDF library ?
Here are the steps on Linux. In the following one should adapt the file names for other system. Please let me know if you are unsure what to do.
test-dir
)For example:
NCDatasets.jl
NetCDF.jl
Note
Pkg.test("NCDatasets")
orPkg.test("NetCDF")
does not work because it ignores the defined preferences.One should have
HDF5_jll
with the version v1.12.1+0 to make these tests:Binaries are generated from these scripts:
https://github.com/Alexander-Barth/Yggdrasil/tree/NetCDF-v4.8.1/N/NetCDF
CC @visr @Datseris @truedichotomy @felixcremer @meggart
The text was updated successfully, but these errors were encountered: