On Sat, Jun 24, 2017 at 10:39:15PM +0200, Andreas Tille wrote:
>...
> Thanks for the explanation. Do you have a better idea what might lead
> to the test failures of the d/rules file is changing only things that
> are happening after the tests are runned?
>
> I admit I'm quite clueless and just ignoring test errors on the
> affected architectures would be really the last resort.
Looking closer through the build history, it seems my 2.3.1-1/2.3.1-2
comparison in the bug report was wrong and misleading, sorry for that.
I was looking only at some architectures, looking through all
architectures the situation based on all 3 2.3.1-* builds is:
2.3.1-* always FTBFS on armel with tests 5,6,11 failing
2.3.1-* always FTBFS on armhf with tests 5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips with tests 4,5,6 failing
2.3.1-* always FTBFS on mipsel with tests 4,5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips64el with tests 5,6 and sometimes 11 failing
2.3.1-* sometimes FTBFS on ppc64el with test 6 failing
2.3.1-* sometimes FTBFS on sometimes with test 5,6,11 failing
So the problems sterted with 2.2.0-1 -> 2.3.1-1,
which actually makes sense.
All test failures are timeouts except the test 4 failures on
mips/mipsel, which are "Failed" and likely a separate issue.
> Kind regards
>
> Andreas.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
