Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

2018-07-11 Thread Alastair McKinstry
This may also be due to recent uploads of a new PMIX (OpenMPI now uses an external pmix library). This linkage seems fragile and I need to come up with package tests in pmix / openmpi to test it. regards Alastair On 10/07/2018 18:57, Anton Gladky wrote: Source: openmpi Version:

Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

2018-07-11 Thread Drew Parsons
On Wed, 11 Jul 2018 13:29:54 +0800 Drew Parsons wrote: > > Not just the autopkgtest, it's fouling up petsc and dolfin too ;( Might be worth mentioning though, openmpi 3.1.1.real-1 has been with us over a week now, but the problem with the dolfin build (unable to build with petsc, and getting

Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

2018-07-10 Thread Drew Parsons
On Tue, 10 Jul 2018 19:57:57 +0200 Anton Gladky > > it looks like the version 3.1.1.real-1 introduces the regression in autopkgtest. > Not just the autopkgtest, it's fouling up petsc and dolfin too ;(

Bug#903492: Runtime error "PMIX-XFER-VALUE: UNSUPPORTED TYPE 28016"

2018-07-10 Thread Anton Gladky
Source: openmpi Version: 3.1.1.real-1 Severity: serious Dear maintainer, it looks like the version 3.1.1.real-1 introduces the regression in autopkgtest. We are preparing some set of autopkgtests for the boost libraries (not in the package yet) [1]. And the MPI-autopkgtests are failing, when