[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#994741: regression tests: skipped vs failed



Come on, inkscape 1.0 is not _that_ buggy.  It has been around for a whole year (with a few fixing releases in-between), and it's the version present in Debian 11.  If it really has grave bugs (I really mean grave), then those should be filed separately, and I should work on getting them fixed as patches on top of 1.0.2.

Then, concerning the ftbfs of 1.1.  I know of it of course.  Just that I've been busy over the past month.  I'm as weirded out by that test failure as you, especially since I couldn't reproduce it anywhere else.
But no, I'm not going to ignore a test failure just because it's skipped in other architectures for different reasons: I'll need more convincing reasons.

If you'd like other bugs in inkscape 1.1: opposed to 1.0.2 it's doing some kind of unaligned memory access somewhere (yet to debug), which makes it crash on armhf when run on arm64 hardware.  I was basically forced to ignore that test failure on Ubuntu and that annoyed me enough, I really don't want to ignore tests just because it's convenient for somebody.


On Tue, 21 Sep 2021, 6:51 pm , <ian_bruce@mail.ru> wrote:
On Tue, 21 Sep 2021 18:57:41 +0300
Andrius Merkys <merkys@debian.org> wrote:

> I cannot reproduce the failure myself on amd64. I tried building on a
> machine without a display, and yet the test succeeds. I will try a
> porterbox next.

If the test succeeds, is the overall build then successful? Is that the
cause of the amd64 build failure on the autobuild systems?

If so, then cannot this problem be temporarily fixed by ignoring the
test result on amd64, also? If it's acceptable to not run the test at
all on 32-bit architectures, and to ignore the result on 64-bit BE
architectures, then it cannot really be that important for 64-bit LE
architectures.

By temporarily ignoring the test result, the immediate problem can be
solved: Inkscape v1.1 is not currently available for amd64 and other
64-bit LE systems. Having temporarily disabled this test, the actual
cause of the failure can then be investigated at anybody's convenience,
without further delaying the availability of the Inkscape distribution
package.

Inkscape v1.0.2 is REALLY buggy. This needs to be fixed soon.


Reply to: