Closed wenrongcao closed 2 months ago
thanks for reporting. The reason for this appears to be that MUMPS_jll
was upgraded from version 5.6.2 to 5.7.0. PETSc_jll
was build vs. 5.6.2 which thus breaks all tests that use mumps (partly my mistake as I did not FIX the version of packages while building PETSc, but foolishly only indicated the lower bound of versions).
Thanks! I updated LaMEM.jl to 0.3.5 and the code is working. The only issue is that TM_Subdcution_example needs permission to read and open files, which causes an error. The code itself seems to run ok if testing is not included.
Writing LaMEM marker file -> ./markers/mdb.00000000.dat
TM_Subduction_example: Error During Test at /Users/wenrongcao/.julia/packages/LaMEM/TmPTE/test/test_examples.jl:9
Got exception outside of a @test
LoadError: SystemError: opening file "./markers/mdb.00000000.dat": Permission denied
At the end of all tests:
Test Summary: | Pass Error Total Time
examples in /scripts | 4 1 5 5m13.9s
TM_Subduction_example | 1 1 1m08.8s
Subduction3D | 2 2 2m46.3s
StrengthEnvelop | 2 2 1m18.8s
ERROR: LoadError: Some tests did not pass: 4 passed, 0 failed, 1 errored, 0 broken.
in expression starting at /Users/wenrongcao/.julia/packages/LaMEM/TmPTE/test/test_examples.jl:5
in expression starting at /Users/wenrongcao/.julia/packages/LaMEM/TmPTE/test/runtests.jl:12
ERROR: Package LaMEM errored during testing
tests on windows also still fail because the code runs too long, so its not fully fixed yet. I did encounter the file permission issue before (but how was that solved again...). But yes, the only thing I did is fixed MUMPS_jll to 5.6.2
I solved some of the issues with testing on windows. Can you try again to see if it now works for you?
Updated to LaMEM.jl 0.3.6, testing LaMEM still gives a file permission error on Macbook. I don't have a Windows PC at hand right now so I cannot test on windows.
Writing LaMEM marker file -> ./markers/mdb.00000000.dat
TM_Subduction_example: Error During Test at /Users/wenrongcao/.julia/packages/LaMEM/kjlav/test/test_examples.jl:10
Got exception outside of a @test
LoadError: SystemError: opening file "./markers/mdb.00000000.dat": Permission denied
Stacktrace:
Test Summary: | Pass Error Total Time
examples in /scripts | 4 1 5 1m17.4s
TM_Subduction_example | 1 1 23.4s
Subduction3D | 2 2 14.8s
StrengthEnvelop | 2 2 39.2s
ERROR: LoadError: Some tests did not pass: 4 passed, 0 failed, 1 errored, 0 broken.
in expression starting at /Users/wenrongcao/.julia/packages/LaMEM/kjlav/test/test_examples.jl:5
in expression starting at /Users/wenrongcao/.julia/packages/LaMEM/kjlav/test/runtests.jl:12
ERROR: Package LaMEM errored during testing
I think I now created a fix for the failing tests. can you please test the main branch of LaMEM on your machine?
pkg> rm LaMEM
pkg> add LaMEM#main
pkg> test LaMEM
If it works for you, I'll create a new release.
Using LaMEM#main, all tests are passed without issues:
--------------------------------------------------------------------------
Test Summary: | Pass Total Time
examples in /scripts | 6 6 1m20.4s
Testing LaMEM tests passed
Thanks for reporting!
Ok this should now be fixed in version 0.3.7, so I’ll close this issue
Hi Boris, after running LaMEM.jl 0.3.4 without any problem in teaching and research last month (last running on AWS on April 12). I encountered an issue to pass testing LaMEM.jl today on my Macbook. My student using Linux (Linux installed on top of Windows, also using LaMEM.jl 0.3.4), however, told me everything is normal and he can run 8 cores without issues.
I am wondering if you could take a look at them when you have time. Thanks much!
I am using Julia 1.10, LaMEM 0.3.4, GeophysicalModelGenerator 0.7.1 and Macbook Pro Intel chip (same error on Macbook using M2 chip, I tested). It gives the following error when running the FallingBlock_DirectSolver test.
I also tested TM_Subduction_example.jl. Using 1 core and multiple cores both give errors. But errors seem to be different: Error when using 1 core:
Error when using 2 cores:
Finally, I tested the subduction_example.ipynb. I CAN run it using 1 core. But using 2 cores, it gives an error (seems to be MPI related):