Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2022/03/26/scikit-learn_1.0.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Hi,

BTW, there is another bug in scikit-learn, but I can't reproduce it and
have set tags accordingly.  Could someone else please give it a try?

Kind regards

     Andreas.

Am Wed, Jul 20, 2022 at 09:23:28PM +0200 schrieb Andreas Tille:

The previous segfault on armel becomes Bus Error on armel and armhf.
I can build it on Power9, but it seems that the test fails on power8 (our buildd).

Am Wed, Jul 27, 2022 at 08:57:09AM -0700 schrieb M. Zhou:

Which does not make it much better as long as no-one is investigating
the issue in a timely manner.  So my suggestion to remove arm 32 bit
architectures (at least until the issue is fixed) remains.

Hmmm, can we talk to buildd admins about this?

Kind regards

   Andreas.

Hi

In #1003165, one of the arm porters wrote they are happy to look at
the bus errors, but the baseline issue should be fixed first.

This may be the cause of the test failures on power8.

Regards
Graham

Hi Graham,

Am Thu, Jul 28, 2022 at 09:15:06AM +0200 schrieb Graham Inggs:

... this was five months ago and silence since then.  We've lost lots of
packages in testing and I see no progress here.  It seems upstream is not
actually keen on working on this as well.  Meanwhile they stepped forward
with new releases and I simply refreshed the issues for the new version
(which are the same and not solved).

Currently we have bus errors on arm 32 bit architectures and a baseline
violation on power.  If there is no solution at the horizon I'd vote for
excluding these three architectures instead of sit and wait (which is all
I can personally do in this topic).

Could someone give this a try?  I know I could use a porter box to do
so but my time is to limited to do it in a sensible time frame.

Kind regards

      Andreas.

I have a long-term power 9 VM (not QEMU) as testbed.
I'm trying to investigate the issues for release architectures,
but this package is too slow to build with QEMU (multiple hours).
(abel.debian.org is also extremely slow for scikit-learn)
I've not yet given up, but the build speed means I cannot
address this issue in timely manner.

Am Thu, Jul 28, 2022 at 08:15:45PM -0700 schrieb M. Zhou:
architectures, that we will not manage to fix it, it is in the interest
of our users to not support the problematic architectures in favour of
providing it for the architetures where the package is used in practice.

I have perfectly understood that we will loose several packages on that
architectures and that this is not a good step.  But having those
packages not at all is eve worse.

Kind regards

     Andreas.

Hi again,

Am Fri, Jul 29, 2022 at 06:09:26AM +0200 schrieb Andreas Tille:
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.

Kind regards

      Andreas.

Hi again,

Am Thu, Aug 04, 2022 at 01:25:42PM +0200 schrieb Andreas Tille:

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

Considering long term maintainance this does not seem to be nice especially
keeping in mind the fact that sklearn is a key package.
I think it is OK to do it _for the moment_ to allow the dust to settle a bit,
and rm'ed packages to get to their destination once again
but I'd suggest ``incrementally'' enabling the tests once everything is in place.

I agree that upstream is probably not very enthusiastic about fixing those, but
if we get fixes, we should keep propagating them.

In a nutshell, IMO the sklearn revision that enters bookworm _should_ have tests enabled, without
hacks and the tests that do not pass can be disabled (after all, it does not come from our end)

Sounds good, and thanks for caring for it.

Hi,

as discussed on Debian Science the affected test suite errors are
ignored for the moment so the package does not FTBFS any more and
thus the bug is not serious any more.  Since issues are remaining
the bugs are not closed yet.

Kind regards
    Andreas.

We believe that the bug you reported is fixed in the latest version of
scikit-learn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1008369@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille <tille@debian.org> (supplier of updated scikit-learn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 17 Feb 2024 14:59:42 +0100
Source: scikit-learn
Architecture: source
Version: 1.4.1.post1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Andreas Tille <tille@debian.org>
Closes: 1003165 1008369 1018635 1027208 1029701 1046775 1049646 1059206
Changes:
 scikit-learn (1.4.1.post1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
     Closes: #1029701, #1008369, #1027208, #1003165
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Build-Depends: python3-sphinx-copybutton
   * Support loong64
     Closes: #1059206
   * Drop nose from Build-/Test-Depends
     Closes: #1018635
   * Fix clean target
     Closes: #1046775, #1049646
   * Work around unknown key 'recommender' in sphinx
   * Exclude minimized jquery JS from source and use symlink to Debian
     packaged min.js instead (crossing fingers that the version plays nicely)
Checksums-Sha1:
 978606cc96691237880a3a2be6ed02ab48cb8d66 3087 scikit-learn_1.4.1.post1+dfsg-1.dsc
 6ac713f80103107381d0b104041df96bddaa9fbd 6389528 scikit-learn_1.4.1.post1+dfsg.orig.tar.xz
 8fb820f431db091a454ef18754aca750e1b0ae61 23312 scikit-learn_1.4.1.post1+dfsg-1.debian.tar.xz
 22158fff23ff6e5925c620b3949954429b024a43 14091 scikit-learn_1.4.1.post1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 52a55300a41630a6a7a79bce38947f7dacfb643bfba558049944f4b5aad19a6a 3087 scikit-learn_1.4.1.post1+dfsg-1.dsc
 25cd7954717180112f66a8e8b0340021a58e3b2cdbd59f82c83d7991dca5ff9f 6389528 scikit-learn_1.4.1.post1+dfsg.orig.tar.xz
 62c3ee142fd41ee13bf925e2a1efa3cbbe835c1db3fb8a0a829ffaa1eb7f3ced 23312 scikit-learn_1.4.1.post1+dfsg-1.debian.tar.xz
 ce99b0a829e7f4ccbae52e3c609d4c00ae434524b01f5b58e0923fdad5ac422b 14091 scikit-learn_1.4.1.post1+dfsg-1_amd64.buildinfo
Files:
 afe4d752ce09c233ff177c28208ae191 3087 python optional scikit-learn_1.4.1.post1+dfsg-1.dsc
 313775874d682e4ababcbc4a08e740a6 6389528 python optional scikit-learn_1.4.1.post1+dfsg.orig.tar.xz
 459683bbda96e5072242b20d7e36bffe 23312 python optional scikit-learn_1.4.1.post1+dfsg-1.debian.tar.xz
 e16b327c5110e32b273e44290c324ff6 14091 python optional scikit-learn_1.4.1.post1+dfsg-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXQy6IRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGbORAAm3M86V3z/Q/2ByGlDFQFHBnyaRCDxbTm
jrqSVT6JBW4YEQXs1jPw4a+4mV3mqh+pIQ2tmH5u+u4VJhNPqWiqjQjyG3RpeVhq
USiVX/7XaWYzcbvtyVynksqxGJY+of0RN1L16d6wLfJhSjNKBTBtKtyv4lL730eB
3q3YoRWeuUtH+/jrn1/uPIsjNry07l98TrauupZvLojKvuyQr9xgK3Me2yddu/v4
lcKigj5Yk+tJJLBy4f1ZqsWDtonGNT3YNnde3DbM+fmLheCOAlNo7OQaCuMhN1Om
dvCZEd65RdvfLJXzpYSq5RrExN/B0xtmO5BBn/2lAbTWHXadFKonLTOC/U4skUXP
4tp0C6j/Zj/a6uBy1ZejEKLYmqclChgahPRj6l4c3lTrfla1YpLOnsZRRBKQQ/PC
7GLjhZxusBzxIYCoprMXwktmCcICIi/wvEdszjS8MlEr+uRsnec45vbEu3+d7Z+C
njaG3TQAV7B1b988LrFLZ0ia2xq6WVYyO4NAth6J/+1emoLmk2nZdHwoDmXJu+rn
oh10ozbcT8/j3L84cxB3gZCa8lC1VgwA86EieZjE54Kl0afsZqUiwqWSW9OUqR1r
JWdLoWBHnkMYf0ogOVAm7rp4BkcBMV7BDp74O0SSRbfcbShTQgOuWTABhg/SrEWz
iSJHBfpNqAU=
=z95P
-----END PGP SIGNATURE-----