hey niko,
i get this timeout as well, on a MIPS32R2 device running DD-WRT 4.9.77 with
perl 5.26.1 (mipsel-threads-multi).
it’s good to know it isn’t just me. i also get “failed to find leader” on all
threads-based tests for the shared libperl installation.
-on a non-shared libperl installation, i still got the timeout for
fold_grind, but the threads tests (_thr) that ran, did so successfully.
so clearly it’s not you or i, but likely something to do with perl, threads,
and RISC-y machines.
either way, the inability to complete these tests on my router (lol) won’t
result in me abandoning my shared libperl installation.
that’s what i get for testing things on a router ;)
On Fri, 21 Jul 2017 23:49:05 +0300 Niko Tyni <nt...@debian.org> wrote:
> On Fri, Jul 21, 2017 at 02:30:07PM -0400, Aaron M. Ucko wrote:
> > Source: perl
> > Version: 5.26.0-4
> > Severity: important
> > Justification: fails to build from source (but built successfully in the
> > past)
> >
> > Recent builds of perl on sparc64 (admittedly not a release
> > architecture) have been failing:
> >
> > t/re/fold_grind ................................................ # Test
> > process timed out - terminating
> > FAILED--no leader found
> >
> > Could you please take a look?
>
> Thanks. Copying the debian-sparc list in the hope somebody there will
> debug this. 5.26.0-4 built on the 'landau' buildd fwiw so it seems either
> nondeterministic or hardware related.
>
> It looks like there's a test timeout of 300 seconds, maybe it's just
> too slow? That would be a bit odd given it doesn't happen on the "small"
> architectures (arm*, mips*)...
>
> See also #869124 for another apparently timing related issue on sparc64.
> --
> Niko Tyni nt...@debian.org
>
>
