This should work now, with pmix and openmpi updated.
Can you check?
regards
Alastair
On 08/01/2019 19:10, Adrian Bunk wrote:
On Tue, Jan 08, 2019 at 02:49:13PM +0000, Steve McIntyre wrote:
On Tue, Jan 08, 2019 at 02:12:06PM +0000, Steve McIntyre wrote:
On Tue, Jan 08, 2019 at 10:42:01AM +0000, Alastair McKinstry wrote:
Hi Steve
On 05/01/2019 15:40, Steve McIntyre wrote:
Package: src:p4est
Version: 1.1-5
Severity: important
I've been doing a full rebuild of the Debian archive, building all
source packages targeting armel and armhf using arm64 hardware. We are
planning in future to move all of our 32-bit armel/armhf builds to
using arm64 machines, so this rebuild is to identify packages that
might have problems with this configuration.
You submitted this and a number of other MPI-test based bugs. I believe they
may be due to #918157, a regression in pmix that breaks MPI on 32-bit archs.
I've uploaded a new openmpi (3.1.3-8) that uses its internal pmix until a fix
is found for #918157, so these should now work. Can you re-test ?
Sure, no problem. I've just queued all those builds to rebuild again
now. I'll let you know how that goes.
Not looking good, I'm afraid. The errors are different, but still
seeing errors. From the dune-common rebuild:
...
1/91 Test #1: indexsettest ........................... Passed 0.01 sec
Start 2: remoteindicestest
2/91 Test #2: remoteindicestest ......................***Failed 0.05 sec
[mjolnir:16218] mca_base_component_repository_open: unable to open
mca_pmix_pmix2x:
/usr/lib/arm-linux-gnueabihf/openmpi/lib/openmpi3/mca_pmix_pmix2x.
so: undefined symbol: OPAL_MCA_PMIX2X_PMIx_Get_version (ignored)
...
That's #918713, which is caused by the workaround for #918157 in 3.1.3-8.
cu
Adrian
--
Alastair McKinstry, <alast...@sceal.ie>, <mckins...@debian.org>,
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.
