Lisandro Dalcin

Could you please try to run setting `export LD_PRELOAD=/path/to/libmpi.so` ? Althernatively, could you build the [MPI-enabled Python interpreter](https://mpi4py.readthedocs.io/en/latest/appendix.html#mpi-enabled-python-interpreter) and use that binary executable to run your script? I'm wondering whether...

> Of course mpi4py could work around it by aligning pickled buffers on 4-byte boundaries mpi4py cannot do that in general, as it does not have any control on how...

@bartoldeman Any updates?

@hppritcha I'm seeing just one issue left, although perhaps I did not reported it before. Sorry about that, there were many loose ends, and I just missed the following one....

@hppritcha Another recent issue [[logs]](https://github.com/mpi4py/mpi4py-testing/runs/8114520639?check_suite_focus=true), it happened on GitHub actions with 3 MPI processes (but not 1 or 2). I could not reproduce with in main (updated a few hours...

@hppritcha Another maybe related issue: when running in singleton init mode, the reproducer above deadlocks at the ~`pset = session.Get_nth_pset(num)`~ `num = session.Get_num_psets()` line.

@hppritcha Now I'm not sure this new issue is related to this one. Do you want me to open a new one?

Hi, @nariba-fj, thanks for contacting us. My primary question is the following: Is there any way to distinguish Fujitsu MPI (and its version?) at **compile time** such that I could...

> I haven't actually tried it, but I think mpi4py will recognize Fujitsu MPI as Open MPI. Yes, that's the case, indeed. mpi4py detects Fujitsu MPI as Open MPI. But...

Thanks! No hurries, once you have news, please come back to me.