Howard Pritchard

yes. including it in this correction for romio in this PR would be fine with me. nice catch!

wrt mpi4py failures, they look to be related to problems we are seeing with intercommunicators. intermittent. they are highly unlikely to be triggered by the work in this pr.

interesting. I couldn't get past the configure stage if I set ```FCFLAGS="-init=snan"```

I hit another problem. If one is trying to build a clone of ompi the variant of openpmix in the main branch doesn't compile with Intel classic compiler owing to...

Now I have something built with -init=snan and I can't reproduce the issue. Curiously my executables have no dependency on libxml2.so. Can you provide the output of ```ldd just_init.exe``` to...

@rhc54 don't worry about PMIx and intel classic compilers. Users aren't supposed to be using this compiler anyway as they (esp. icc/icpc) are past end of life. Indeed as I...

Have you had a chance to try the ```--with-hwloc-internal``` configure option to see if that is a workaround for this issue?

related to #12400 . see suggested workaround posted in that issue for a possible resolution to this one.

I don't think so. The ```--disable-libxml2``` get's passed to the hwloc configure which disables compilation of xml2 dependent parts of hwloc. it was libxml2 where the fpe was getting thrown,...

@janjust could someone from nvidia check out what's going on with nvidia ci?