Your message dated Mon, 27 Nov 2023 10:08:50 +0100
with message-id <a7666aba-f912-44a6-9ea6-56cbe78ac...@debian.org>
and subject line Re: Bug#1055600: transition: suitesparse-7.3
has caused the Debian Bug report #1056392,
regarding suitesparse breaks the octave autopkgtest on 32bit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1056392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suitesparse
Version: 1:7.3.1+dfsg-2
Tags: ftbfs
https://tracker.debian.org/pkg/suitesparse
Issues preventing migration:
∙ ∙ autopkgtest for octave/8.4.0-1: amd64: Pass, arm64: Pass, armel: Regression
♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻
(reference ♻), ppc64el: Pass, s390x: Pass
...
254s libinterp/corefcn/qr.cc-tst ....................................fatal:
caught signal Segmentation fault -- stopping myself...
254s Segmentation fault
254s autopkgtest [17:25:32]: test upstream-testsuite: -----------------------]
254s autopkgtest [17:25:32]: test upstream-testsuite: - - - - - - - - - -
results - - - - - - - - - -
254s upstream-testsuite FAIL non-zero exit status 139
255s autopkgtest [17:25:33]: @@@@@@@@@@@@@@@@@@@@ summary
255s builtin-features PASS
255s smoke PASS
255s upstream-testsuite FAIL non-zero exit status 139
--- End Message ---
--- Begin Message ---
Hi,
On 26-11-2023 18:20, Sébastien Villemot wrote:
The only remaining issue is an autopkgtest failure of octave in
testing, reported as #1056392.
I’ve argued there that this issue only affects partial upgrades, and
that I’m not sure how to fix it (if fixing is needed at all). Please
advise.
Although I'm not 100% sure, I think that cases like this are
imperfections in our upgrade system. I believe that we started to care
much more about partial upgrades since we started using autopkgtest, but
I don't think we have the means (apart for always tightening relations
and giving up much of the flexibility we so much appreciate) to fix skew
in a mechanical way (particularly in transitions and our use of
binNMUs), hence I think it's OK to occasionally let this happen currently.
I have rescheduled the failing tests with octave from unstable, which
should automatically resolve the migration blocker. (There are several
conditions where britney2 already does this trick automatically and
where potential broken partial upgrades are not prevented either, so
this is matching status quo).
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
