Re: insighttoolkit4 backport on wheezy 32bit -- 2 tests failures
On Thu, 29 May 2014, Gert Wollny wrote:
> Hello Yaroslav,
> On Thu, 2014-05-29 at 10:33 -0400, Yaroslav Halchenko wrote:
> > I have (again) tried to provide a backport build of itk4 for wheezy (to
> > be shipped from NeuroDebian) and got those 2 tests to fail.
> > 926 - itkTIFFImageIOCompression_RGBTestImageJPEG_JPEG (Failed)
> > 2168 - itkOtsuThresholdImageFilterTestShort (Failed)
> > Would you be so kind to share your expertise on
> > 1. either I could consider such a failure "minor" thus probably just
> > excluding those tests from being run
> I don't think we should disable tests without also disabling the
> according functionality.
> > 2. or may be you see how I could easily mitigate/fix underlying problem?
> I will try to compile it myself to debug the errors (if I can reproduce
> them). Actually, I already tried a
> nd_build nd+debian wheezy i386 ...
> but the dependencies could not be resolved. Could it be that you
> backported a gccxml but didn't upload it to the neurodebian repo yet?
That is strange since if you used that command, it should have resulted
in identical environment (given that you nd_updatedist recently):
regarding the gccxml:
~/deb/builds/insighttoolkit4/4.5.2-1$ grep gccxml insighttoolkit4_4.5.2-1~nd70+1_i386.build | head
Depends: debhelper (>= 9), cmake, swig (>= 2.0), gccxml (>= 0.9.0+cvs20120420), zlib1g-dev (>= 1.2.2), libpng12-dev, libtiff-dev, libfftw3-dev, libdcmtk2-dev, libgdcm2-dev, libdouble-conversion-dev, uuid-dev, libminc-dev, libhdf5-dev, python-all-dev, libvtk5-dev, python-vtk
pbuilder-satisfydepends-dummy depends on gccxml (>= 0.9.0+cvs20120420); however:
Package gccxml is not installed.
gccxml{a} gettext{a} gettext-base{a} groff-base{a} hdf5-helpers{a}
Selecting previously unselected package gccxml.
Unpacking gccxml (from .../gccxml_0.9.0+cvs20120420-4_i386.deb) ...
Setting up gccxml (0.9.0+cvs20120420-4) ...
so it comes from the stock wheezy:
https://packages.debian.org/search?keywords=gccxml
wheezy (stable) (devel): XML output extension to GCC
0.9.0+cvs20120420-4: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
Just in case -- uploaded my currently completed logs to http://neuro.debian.net/_files/_buildlogs/insighttoolkit4/4.5.2
from NeuroDebian it just gets
Unpacking neurodebian-popularity-contest (from .../neurodebian-popularity-contest_0.32~nd70+1_all.deb) ...
Unpacking libdouble-conversion1:i386 (from .../libdouble-conversion1_2.0.1-1~nd70+1_i386.deb) ...
Unpacking libdouble-conversion-dev (from .../libdouble-conversion-dev_2.0.1-1~nd70+1_i386.deb) ...
> > Details: actually looking at 926 -- it complains "out of disk space" but I
> > consider it VERY unlikely since that box has it in abundance :-/
> That smells like a integer conversion gone wrong.
ah -- could well be... I had somewhat similar symptoms from apt while trying to
update some very elderly 32bit ubuntu chroot on this box...
> It could be that for
> the backport one has to enforce libtiff5-dev.
rright -- that one was not pulled in, while in sid it does it
$> wget -q -O- 'https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit4&arch=i386&ver=4.5.2-2&stamp=1401264590' | grep libtiff5-dev
libtiff5 libtiff5-dev libtiffxx5 libtk8.5 libtorque2 libudev1 libunistring0
libtiff5-dev libtiffxx5 libtk8.5 libtorque2 libudev1 libunistring0 libva1
Get:257 http://mirror.bm.debian.org/debian/ unstable/main libtiff5-dev i386 4.0.3-8 [335 kB]
Selecting previously unselected package libtiff5-dev:i386.
Preparing to unpack .../libtiff5-dev_4.0.3-8_i386.deb ...
Unpacking libtiff5-dev:i386 (4.0.3-8) ...
Setting up libtiff5-dev:i386 (4.0.3-8) ...
would you mind adding a direct dependency to insighttoolkit4 package's control?
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist, Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
Reply to: