Debian Bug report logs - #780659
insighttoolkit only built on amd64 and i386

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: insighttoolkit only built on amd64 and i386

Date: Tue, 17 Mar 2015 14:53:06 +0100

Package: src:insighttoolkit4
Version: 4.6.0-3

insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked on
some more architectures.  any reason for not trying to build that?  Sure, it
needs 50g - 100g disk for the build, a 500mb log file, and such.  given the
alternative to remove binaries for other architectures before the next Ubuntu
release, I gave it a try ...

patches at
http://patches.ubuntu.com/i/insighttoolkit4/insighttoolkit4_4.6.0-3ubuntu3.patch

updating the SSE stuff, and ignoring the test failures for now for other
architectures.

Tests failing on ppc64el:

The following tests FAILED:
        468 - itkPatchBasedDenoisingImageFilterTest0 (Failed)
        469 - itkPatchBasedDenoisingImageFilterTestGaussian (Failed)
        470 - itkPatchBasedDenoisingImageFilterTestRician (Failed)
        471 - itkPatchBasedDenoisingImageFilterTestPoisson (Failed)
        772 - itkHDF5ImageIOTest (Failed)
        1526 - itkSingleLevelSetsv4DenseImage2DTest (Failed)
        1528 - itkSingleLevelSetsv4WhitakerImage2DTest (Failed)
        1529 - itkSingleLevelSetsv4WhitakerImage2DTestThreads (Failed)
        1531 - itkSingleLevelSetsv4ShiImage2DTest (Failed)
        1532 - itkSingleLevelSetsv4WhitakerImage2DWithCurvatureTest (Failed)
        1536 - itkLevelSetsv4EquationPropagationTermTest (Failed)
        1537 - itkLevelSetsv4EquationLaplacianTermTest (Failed)
        1549 - itkMultiLevelSetsv4WhitakerImageSubset2DTest (Failed)
        1652 - itkImageToImageMetricv4Test (Timeout)

Tests failing on powerpc:
The following tests FAILED:
        532 - itkDicomDifficultFile (Failed)
        665 - itkFFTWF_FFTTest (OTHER_FAULT)
        666 - itkFFTWF_RealFFTTest (OTHER_FAULT)
        667 - itkVnlFFTWF_FFTTest (OTHER_FAULT)
        668 - itkVnlFFTWF_RealFFTTest (OTHER_FAULT)
        741 - itkGDCMImageIOTest1 (Failed)
        744 - itkGDCMImageIOTest4 (Failed)
        754 - itkGDCMImageIONoCrashTest (Failed)
        772 - itkHDF5ImageIOTest (Failed)
        1010 - itkIOTransformMatlabTest (SEGFAULT)
        1526 - itkSingleLevelSetsv4DenseImage2DTest (Failed)
        1528 - itkSingleLevelSetsv4WhitakerImage2DTest (Failed)
        1529 - itkSingleLevelSetsv4WhitakerImage2DTestThreads (Failed)
        1531 - itkSingleLevelSetsv4ShiImage2DTest (Failed)
        1532 - itkSingleLevelSetsv4WhitakerImage2DWithCurvatureTest (Failed)
        1536 - itkLevelSetsv4EquationPropagationTermTest (Failed)
        1537 - itkLevelSetsv4EquationLaplacianTermTest (Failed)
        1549 - itkMultiLevelSetsv4WhitakerImageSubset2DTest (Failed)
        1551 - itkMultiLevelSetsv4MalcolmImageSubset2DTest (SEGFAULT)
        1652 - itkImageToImageMetricv4Test (Failed)
        1662 - itkMattesMutualInformationImageToImageMetricv4Test (Timeout)
        1664 - itkMultiStartImageToImageMetricv4RegistrationTest (SEGFAULT)
        1669 - itkImageToImageMetricv4RegistrationTest (Timeout)
        1670 - itkImageToImageMetricv4RegistrationTest2 (SEGFAULT)
        1671 - itkImageToImageMetricv4RegistrationTest3 (SEGFAULT)
        1676 - itkEuclideanDistancePointSetMetricRegistrationTest (SEGFAULT)
        1678 - itkObjectToObjectMultiMetricv4Test (SEGFAULT)
        1679 - itkObjectToObjectMultiMetricv4RegistrationTest (SEGFAULT)
        1877 - itkMattesMutualInformationImageToImageMetricTest (SEGFAULT)
        1879 - itkMattesMutualInformationImageToImageMetricTest3 (SEGFAULT)
        1880 - itkMattesMutualInformationImageToImageMetricTest4 (SEGFAULT)
        1910 - itkTimeVaryingVelocityFieldImageRegistrationTest (SEGFAULT)
        1911 - itkTimeVaryingBSplineVelocityFieldImageRegistrationTest (SEGFAULT)
        1912 - itkSyNImageRegistrationTest (SEGFAULT)
        1913 - itkBSplineSyNImageRegistrationTest (SEGFAULT)
        1914 - itkQuasiNewtonOptimizerv4RegistrationTest1 (Failed)
        1932 - itkDiffeomorphicDemonsRegistrationFilterTest01 (SEGFAULT)
        1933 - itkDiffeomorphicDemonsRegistrationFilterTest02 (SEGFAULT)
        1934 - itkDiffeomorphicDemonsRegistrationFilterTest03 (Failed)
        1935 - itkDiffeomorphicDemonsRegistrationFilterTest04 (Failed)
        1936 - itkDiffeomorphicDemonsRegistrationFilterTest05 (SEGFAULT)
        1937 - itkDiffeomorphicDemonsRegistrationFilterTest06 (SEGFAULT)
        1938 - itkDiffeomorphicDemonsRegistrationFilterTest07 (SEGFAULT)
        1939 - itkDiffeomorphicDemonsRegistrationFilterTest08 (SEGFAULT)
        1940 - itkDiffeomorphicDemonsRegistrationFilterTest09 (Timeout)
        1941 - itkDiffeomorphicDemonsRegistrationFilterTest10 (SEGFAULT)
        1942 - itkDiffeomorphicDemonsRegistrationFilterTest11 (SEGFAULT)
        1943 - itkDirectFourierReconstructionImageToImageFilterTest (Timeout)
        1944 - itkDiscreteGaussianDerivativeImageFilterScaleSpaceTest (SEGFAULT)
        2526 - DicomSliceReadPythonTest (Failed)

Message #10 received at 780659@bugs.debian.org (full text, mbox, reply):

From: Paul Novotny <paul@paulnovo.us>

To: Matthias Klose <doko@debian.org>, 780659@bugs.debian.org

Subject: Re: [Debian-med-packaging] Bug#780659: insighttoolkit only built on amd64 and i386

Date: Tue, 24 Mar 2015 16:27:02 -0400

On Tue, 2015-03-17 at 14:53 +0100, Matthias Klose wrote:
> Package: src:insighttoolkit4
> Version: 4.6.0-3
> 
> insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked on
> some more architectures.  any reason for not trying to build that?  Sure, it
> needs 50g - 100g disk for the build, a 500mb log file, and such.  given the
> alternative to remove binaries for other architectures before the next Ubuntu
> release, I gave it a try ...

I looked at this a while back. From what I could tell, some of the tests
were failing because GDCM was reading files incorrectly on big-endian
systems. The GDCM package is built with its tests off, so I think that
is how GDCM can be built for big endian architectures. Upstream GDCM
lists big endian support as a "major" missing feature, and unlikely to
work [1].

-Paul

[1] http://gdcm.sourceforge.net/wiki/index.php/Missing

Message #15 received at 780659@bugs.debian.org (full text, mbox, reply):

From: Andreas Tille <andreas@an3as.eu>

To: Paul Novotny <paul@paulnovo.us>, 780659@bugs.debian.org

Cc: Matthias Klose <doko@debian.org>

Subject: Re: Bug#780659: Bug#780659: insighttoolkit only built on amd64 and i386

Date: Wed, 25 Mar 2015 08:28:09 +0100

Hi,

On Tue, Mar 24, 2015 at 04:27:02PM -0400, Paul Novotny wrote:
> On Tue, 2015-03-17 at 14:53 +0100, Matthias Klose wrote:
> > Package: src:insighttoolkit4
> > Version: 4.6.0-3
> > 
> > insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked on
> > some more architectures.  any reason for not trying to build that?  Sure, it
> > needs 50g - 100g disk for the build, a 500mb log file, and such.  given the
> > alternative to remove binaries for other architectures before the next Ubuntu
> > release, I gave it a try ...
> 
> I looked at this a while back. From what I could tell, some of the tests
> were failing because GDCM was reading files incorrectly on big-endian
> systems. The GDCM package is built with its tests off, so I think that
> is how GDCM can be built for big endian architectures. Upstream GDCM
> lists big endian support as a "major" missing feature, and unlikely to
> work [1].

I personally creating packages with tests switch of because we know the
tests will fail for certain architectures does not make any sense.  We
do not provide packages to fill in gaps in our package x architecture
matrix but to serve users.  We also should not trust on users on those
architectures since these leaf packages are usually run on mainstream
architectures and thus the packages with failed test would just fill
space on our ftpserver with no use at all.

Kind regards

       Andreas.

-- 
http://fam-tille.de

Message #20 received at 780659@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: Andreas Tille <andreas@an3as.eu>, Paul Novotny <paul@paulnovo.us>, 780659@bugs.debian.org

Subject: Re: Bug#780659: Bug#780659: insighttoolkit only built on amd64 and i386

Date: Wed, 25 Mar 2015 09:34:24 +0100

On 03/25/2015 08:28 AM, Andreas Tille wrote:
> Hi,
> 
> On Tue, Mar 24, 2015 at 04:27:02PM -0400, Paul Novotny wrote:
>> On Tue, 2015-03-17 at 14:53 +0100, Matthias Klose wrote:
>>> Package: src:insighttoolkit4
>>> Version: 4.6.0-3
>>>
>>> insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked on
>>> some more architectures.  any reason for not trying to build that?  Sure, it
>>> needs 50g - 100g disk for the build, a 500mb log file, and such.  given the
>>> alternative to remove binaries for other architectures before the next Ubuntu
>>> release, I gave it a try ...
>>
>> I looked at this a while back. From what I could tell, some of the tests
>> were failing because GDCM was reading files incorrectly on big-endian
>> systems. The GDCM package is built with its tests off, so I think that
>> is how GDCM can be built for big endian architectures. Upstream GDCM
>> lists big endian support as a "major" missing feature, and unlikely to
>> work [1].
> 
> I personally creating packages with tests switch of because we know the
> tests will fail for certain architectures does not make any sense.  We
> do not provide packages to fill in gaps in our package x architecture
> matrix but to serve users.  We also should not trust on users on those
> architectures since these leaf packages are usually run on mainstream
> architectures and thus the packages with failed test would just fill
> space on our ftpserver with no use at all.

but who do you trust to build on i386 with warnings like:

  warning: converting to non-pointer type
  warning: iteration 3u invokes undefined behavior

Message #25 received at 780659@bugs.debian.org (full text, mbox, reply):

From: Andreas Tille <tille@debian.org>

To: Matthias Klose <doko@debian.org>

Cc: Paul Novotny <paul@paulnovo.us>, 780659@bugs.debian.org

Subject: Re: Bug#780659: Bug#780659: insighttoolkit only built on amd64 and i386

Date: Wed, 25 Mar 2015 09:56:48 +0100

Hi,

On Wed, Mar 25, 2015 at 09:34:24AM +0100, Matthias Klose wrote:
> > I personally creating packages with tests switch of because we know the
> > tests will fail for certain architectures does not make any sense.  We
> > do not provide packages to fill in gaps in our package x architecture
> > matrix but to serve users.  We also should not trust on users on those
> > architectures since these leaf packages are usually run on mainstream
> > architectures and thus the packages with failed test would just fill
> > space on our ftpserver with no use at all.
> 
> but who do you trust to build on i386 with warnings like:
> 
>   warning: converting to non-pointer type
>   warning: iteration 3u invokes undefined behavior

I have not said that I trust these and I have no idea why you mix up
this with the other case we discussed in this bug report.

Kind regards

        Andreas.

-- 
http://fam-tille.de

Send a report that this bug log contains spam.