test_save_deg2 fails for FEniCS stable

[kvslab]

test_save_deg2 fails for FEniCS stable

[keiyamamo]

Failure of save_deg=2 is related to PETScDMCollection.create_transfer_matrix and is reported here

[johannesring]

@keiyamamo - Yes, I think that is okay for now.

[keiyamamo]

The error seems to come from MPI, but it’s a bit weird since we are not using MPI in the test. I don’t know how to fix this immediately but maybe using updated version of container might help?

https://github.com/KVSlab/turtleFSI/blob/fc46e6d32e713de22784706f934ea8c13edc6b38/.github/workflows/test_turtle.yml#L20C16-L20C61

or @jorgensd might know how to fix this.

[johannesring]

That is for the tests that are run against FEniCS master (test_turtle.yml). This is not failing, but it should probably be updated to the latest tag (2023-08-14). The failing tests are run against FEniCS stable (test_turtle_conda.yml).

[keiyamamo]

I see. It seems like there were some updates on conda-forge fenics last couple of weeks, so that might be related...

https://github.com/conda-forge/fenics-feedstock

[jorgensd]

The conda envs are using PETSc 3.20, which could cause many issues for us, as PETSc no longer does garbage collection in Python (since 3.16).

[keiyamamo]

If it's related to PETSc version, I'm guessing there's little we can do to fix. One way is to simply remove the test for save_deg=2. I guess the problem might be related to 'PETScDMCollection.create_transfer_matrix' function.

[keiyamamo]

This problem affects conda-forge as you can see here. Should we simply deactivate test for save_deg=2 for now? @johannesring @jorgensd

[johannesring]

@keiyamamo - I don't think the issue with turtle on conda-forge is related to this issue. When looking at the logs, you can see that all the tests are failing due to a segfault. This is the same problem I see when restarting the tests for Python 3.10. The first test, test_cfd, fails with a segfault (see here). I've also tried to run the tests locally using act, and for Python 3.10, all the tests fail with a segfault.

I'm not sure whether we should consider disabling the test_save_deg2. It looks to be a problem only with the conda packages for Python 3.8 (and possibly Python 3.10).

Note that all the various Python versions we test use the same PETSc version (3.20.0), so the issue doesn't look to be related to the PETSc version.

[jorgensd]

I saw a related issue yesterday, due to using the latest version of mpi4py. Maybe try to pin it to a sensible version? @MariusCausemann, what version did you end up using?

[MariusCausemann]

I solved my problem by using mpi4py 3.1.4, but I'm not sure if it's the same problem. Good luck!

[keiyamamo]

Thank you @MariusCausemann ! I tried with 3.1.4 but did not solve the problem keiyamamo#3
I noticed that hdf5 has different versions than before so that might be related as well.

[johannesring]

Using PETSc 3.19.6 fixed the problem with Python 3.8, but it did not fix the problem with segfaults with Python 3.10.

[keiyamamo]

I tested with hdf5 version 1.12.2 and that solved the problem with python3.8 and 3.10 but created a problem with 3.9.... maybe some combination of versions work fine.

[minrk]

I don't understand the interactions enough, but the segfault in conda-forge/fenics-feedstock#192 is because PetscInitialize is never called. This seems to clearly be a bug in fenics, as PetscInitialize seems like it should be required before using petsc at all.

Fixing that seems ot be easy, and requires calling SubSystemsManager.init_petsc() before using petsc. But that only lets you get as far as the MPI error 98, which I also don't understand, and may be related to mpi initialization.

[keiyamamo]

Thank you @minrk for the explanation! I lowered version of hdf5 and mpi4py (here), and it passes pytest now, so it seems to be somehow related to the recent version of mpi4py. It might be related to this ?

@johannesring @jorgensd Do you think it would be okay to specify hdf5 and mpi4py version in environment.yml so that it passes the pytest for now?