Control: severity -1 important On Wed, 25 Apr 2018 10:20:28 +0100 Alastair McKinstry <alastair.mckins...@sceal.ie> wrote: > > > On 25/04/2018 10:04, Adrian Bunk wrote: > > On Wed, Apr 25, 2018 at 09:55:08AM +0100, Alastair McKinstry wrote: > >> This build-failure was fixed with the 3.0.1-5 release (incorrect > >> selections in the Makefile filter syntax). > > To me it looks like the same failure in -4, -5 and -8. > > > > On 3 different architectures. > > > Ok, this does look like a different bug. > >> The current build failure on i386 looks different - nothing relevant has > >> changed since -5 (in openmpi; perhaps gcc changes? ) > > The whole pattern looks like a race condition somewhere that randomly > > causes this FTBFS. > > > > Just look at > > https://buildd.debian.org/status/logs.php?pkg=openmpi&arch=arm64 > > > > -5 did FTBFS, but just an hour later the same sources built on > > the same architecture. > Agreed, looks like a race condition (on slower architectures ? )
arm64, ppc64el and i386 are fast architectures. > I will enable the verbose debugging (#896861). Perhaps --no-parallel > would be a good idea, but I will avoid inserting that in the next upload > until we understand the failure. I have built openmpi_3.0.1-9 on plummer (ppc64el porterbox) 20 times in a loop without a failure. It would be good to fix this but with such a low failure rate I'm downgrading this to allow migration to testing. Emilio
