GNU bug report logs - #60640
Gnu: Add gdcm

Previous Next

Full log

Message #106 received at 60640 <at> debbugs.gnu.org (full text, mbox):

From: Tor-björn Claesson <tclaesson <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 60640 <at> debbugs.gnu.org
Subject: Re: bug#60640: Gnu: Add gdcm
Date: Fri, 27 Jan 2023 17:06:37 +0200

[Message part 1 (text/plain, inline)]

Hi!

Ludovic Courtès <ludo <at> gnu.org> writes:
>
> The following tests FAILED:
> 	195 - TestStrictScanner1 (Failed)
> 	196 - TestStrictScanner2_1 (Failed)
> 	197 - TestStrictScanner2 (Failed)
> 	198 - TestStrictScanner2_2 (Failed)
> Errors while running CTest
>
> Passing #:parallel-tests? #f doesn’t help.
>
> Could you take a look?

The TestStrictScanner tests fail because they expect TestWriter to have
run, but we disabled it.

TestWriter, TestAnonymizer4, and TestPrinter1 are also reported as
failing in the GDCM ctest dashboard
(https://open.cdash.org/index.php?project=GDCM).
It is strange that they passed previously in my local checkout
(they fail now, some change in the toolchain?)
I will try to look into this.

For now, here is a patch to ignore the remaining failures, giving us
an installable package, and also updated patches to add a bin output
and use more system libraries.

Investigating the remaining failing tests and using more system
libraries feels like a fairly big, if fun, task possibly involving
work on GDCM as well as this package. Should we close this bug report
if we have a working package when the attached patches are applied?

-- 
Mvh,
Tor-björn Claesson

[0001-gnu-gdcm-Ignore-remaining-failing-tests.patch (text/x-patch, attachment)]

[0002-gnu-gdcm-Add-bin-output.patch (text/x-patch, attachment)]

[0003-gnu-gdcm-Use-more-system-libraries.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.