Bug#1061605: scipy: tests skipped during build and autopkgtest not in sync

[Drew Parsons]

Source: scipy
Followup-For: Bug #1061605

Note that debci tests are passing on all arches (where built) for
scipy 11.

I'm inclined to accept this as a solution.
i.e. update the list of builds tests to skip for scipy 11
rather than reorganise debian/tests skips for scipy 10.

Bug#1061605: scipy: tests skipped during build and autopkgtest not in sync

[Drew Parsons]

Source: scipy
Followup-For: Bug #1061605

Easy enough to relax tolerances or skip tests if we needed to.
test_maxiter_worsening was giving problems on other arches.

But strange the test only started failing when pythran was deactivated.
I've reactivated it in 1.10.1-8, we'll see if it restores success.

Bug#1061605: scipy: tests skipped during build and autopkgtest not in sync

[Graham Inggs]

Source: scipy
Version: 1.10.1-7
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

scipy's autopkgtests have regressed on arm64 [1], i386 [2], ppc64el
[3] and s390x [4].

It seems (at least for arm64) that test_maxiter_worsening[lgmres] is
skipped during the build [5], but fails during the autopkgtest.  The
same may be true for the other architectures.

I think there are enough logs available to go through and figure out
the remaining.  I'll try to do this in the next week or so.

Regards
Graham


[1] https://ci.debian.net/packages/s/scipy/testing/arm64/
[2] https://ci.debian.net/packages/s/scipy/testing/i386/
[3] https://ci.debian.net/packages/s/scipy/testing/ppc64el/
[4] https://ci.debian.net/packages/s/scipy/testing/s390x/
[5] 
https://salsa.debian.org/python-team/packages/scipy/-/blob/debian/1.10.1-6/debian/rules?ref_type=tags#L33-35