Bug#1008369: scikit-learn testing migration

[Andreas Tille]

Hi again,

Am Thu, Aug 04, 2022 at 01:25:42PM +0200 schrieb Andreas Tille:
> Am Fri, Jul 29, 2022 at 06:09:26AM +0200 schrieb Andreas Tille:
> Before we fall into another "do nothing" period:  I will upload
> scikit-learn restricted to those architectures only which have all tests
> passing and will ask ftpmaster for removal of the others.  If you think
> this is a bad idea please give good reasons not to do so or even better
> fix the package for the problematic architectures.

When looking at the rules file I noticed that we currently exclude
(more or less randomly) certain tests for certain architectures.
So I had two options:

  1. Simply add the other failing tests
  2. Ignore all failures but print the failures into the build logs

I decided for the latter now in scikit-learn_1.1.2+dfsg-3 and you see
that the package is building now.  I've added according README.Debian
which are *architecture specific*[1] to inform our users about
poptential issues.

The drawback of this solution is that we will not get any warning for
new *potentially more important* issues since all test failures will be
ignored now.  For me this is outweighted by the advantage that we can
present upstream a full log of all issues in certain architectures and
can open according issues.  I admit I'm not really enthusiastic that
upstream will care much about this - but at least we have the logs at
hand and can do something in case someone wants to invest time into
this.

I do not plan to close bugs #1003165 and #1008369 but I think it is
appropriate to reduce its severity to important and thus enable the
package and its dependencies to migrate to testing (I have not checked
debci yet).

Any comments about this strategy?

Kind regards

      Andreas.

[1] https://salsa.debian.org/science-team/scikit-learn/-/blob/master/debian/rules#L227

-- 
http://fam-tille.de