Hi Adrian,
On Sat, Jun 24, 2017 at 11:30:05PM +0300, Adrian Bunk wrote:
> >
> > Hmmm, this would most probably lead to successfully built packages but I
> > would prefer spending some additional thoughts on this. It would
> > explain the issue why the package has built before but does not any more
> > without any visible change on "weak" architectures. I could imagine
> > that after stretch release the run on the build servers increased and
> > that possibly parallel builds are happening which lead to performance
> > loss for single packages.
> >...
>
> No, a buildd never builds more than 1 package at a time.
>
> Some of the weaker architectures currently have 100 packages
> queued to be built and it can take a few days until a package
> gets built, but during the build the situation stays the same.
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.
Kind regards
Andreas.
--
http://fam-tille.de
