Hi Sébastien,
On Tue, Oct 24, 2017 at 02:17:26PM +0200, Sébastien Villemot wrote:
> > (see build log[2]). My suspicion is that this is not really an error in
> > the test suite but some problem with the autobuilder? Could somebody
> > please have a look? If not the only chance I see is to deactivate armhf
> > for pandas.
>
> pandas is uncompiled on armhf, so this is not a blocker for testing migration.
I can confirm that
https://packages.debian.org/buster/python-pandas-lib
does not list armhf but
https://buildd.debian.org/status/package.php?p=pandas&suite=buster
lists armhf as "installed". So what is true?
If we do not need armhf, than we are through all released archictectures
now:
https://buildd.debian.org/status/package.php?p=pandas&suite=sid
I just realise that #877419 is set to important anyway, so there is no
need to reduce its severity and the package could migrate (migration
status says only "to young")
I would love if somebody would take over to inform upstream about the
failed tests. They have released first RC candidates for next version
and may be it makes sense to get this in. I'm very busy (mostly real
life from now on the whole next week.
Kind regards
Andreas.
--
http://fam-tille.de
