Lisandro Dalcin

Results 47 issues of Lisandro Dalcin

The problem is actually rooted at libevent. This affects the latest release tarball 5.0.2, possibly 4.1.6 too. Without running `./autogen.sh` first on the libevent source directory, at some point the...

question
Target: v5.0.x

Support for `MPI_TYPECLASS_LOGICAL` as being proposed in mpi-forum/mpi-issues#699. As a bonus, add preliminary support the `MPI_LOGICAL16` datatype. TODO: Support for 128bit integral C types via GCC/LLVM `__int128` extension.

Target: main

This is with branch `v5.0.x`, but I guess `main` has the same issue (currently, I'm unable to build `main` with internal pmix on Fedora 38, I'll submit another issue). ###...

bug
Target: main
Target: v5.0.x

https://github.com/mpi4py/mpi4py-testing/actions/runs/9654833551/job/26629748498 ```python Traceback (most recent call last): File "/home/runner/work/mpi4py-testing/mpi4py-testing/test/main.py", line 304, in main(module=None) File "/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/unittest/main.py", line 104, in __init__ self.parseArgs(argv) File "/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/unittest/main.py", line [13](https://github.com/mpi4py/mpi4py-testing/actions/runs/9654833551/job/26629748498#step:16:14)6, in parseArgs self._do_discovery([]) File "/opt/hostedtoolcache/Python/3.12.4/x64/lib/python3.12/unittest/main.py", line...

## Pull Request Description Possible additions from the upcoming MPI 4.2 standard. ## Author Checklist * [x] **Provide Description** Particularly focus on _why_, not _what_. Reference background, issues, test failures,...

A few times a month, mpi4py's testsuite running daily in GitHub Actions fails the following way: ``` ====================================================================== FAIL: testInterrupt (__main__.TestRunScript.testInterrupt) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/runner/work/mpi4py-testing/mpi4py-testing/demo/test-run/test_run.py", line...

mpi4py 's own nightly CI testing on GHA has been failing with ompi@main in the last three days. However, I understand that OMPI's own CI had not failed, otherwise you...

While trying to workaround an build regression issue issue in 5.0.8 with cross-compiling in conda-forge, I ran configure natively on maOS-arm64 and Linux-x86_64. After inspecting `configure.log`, I noticed the following...

bug
Target: main
Target: v5.0.x

Spawn with ch4:ofi has become unreliable in GitHub Actions CI. https://github.com/mpi4py/mpi4py-testing/actions/runs/15009974924/attempts/1 https://github.com/mpi4py/mpi4py-testing/actions/runs/15009974924/attempts/2 The logs are not very informative, but past experience indicates that something must be going on. I'll run...

Configured with `--with-libfabric=embedded`... ``` In file included from ../../../mpich/modules/libfabric/prov/opx/include/rdma/opx/fi_opx_reliability.h:36, from ../../../mpich/modules/libfabric/prov/opx/include/rdma/opx/fi_opx_domain.h:44, from ../../../mpich/modules/libfabric/prov/opx/src/fi_opx_av.c:35: ../../../mpich/modules/libfabric/prov/opx/include/rdma/opx/fi_opx.h:232:44: error: expected identifier or '(' before 'if' 232 | #define OPX_COMPILE_TIME_ASSERT(cond, msg) if(0){switch(0){case 0:case cond:;}} |...