[Debian-med-packaging] insighttoolkit4 doesn't build on i386, failed tests

[Gert Wollny]

Hello Gianfranco, 

> (sorry for the top quoting, yahoo mail client for android doesn't
> allow me to correctly quote)
don't worry, most people do it like this nowadays, so I'm quite
accustomed to it. 

> (maybe tighteen the version in control file can be useful if somebody
> will ever try to backport it).
I think the problem is which version of g++ is used, i.e. with g++4.7
the older version of gccxml would probably work.

> Anyway do you plan to do you rules trick?
What was holding me back is that I would like to test it with a simple
fake package were a test fails before I actually add it to ITK. Sending
ITK to the build servers just to test if my understanding of the d/rules
file is correct just doesn't seem right. I will see if I get around to
do it this week. 

> Otherwise I can try to do it, but I'll need a sponsor, 
Me too.

> and I'm not sure how I can call make tests (or the override) and and
> just discard the exit status...
The test override is already in place in the rules file: 
I would replace it by

override_dh_auto_test:
    LD_LIBRARY_PATH=`pwd`/BUILD/lib dh_auto_test && exit 0 
    cat `pwd`/BUILD/Testing/Temporary/LastTest.log
    exit 1 

This should run through if all tests pass and dump the log and bail out
if a test fails.

Ciao 
Gert 

> From: Gert Wollny <gw.fossdev at gmail.com>; 
> To: <debian-med-packaging at lists.alioth.debian.org>; 
> Cc: Gianfranco Costamagna <costamagnagianfranco at yahoo.it>; 
> Subject: Re: [Debian-med-packaging] insighttoolkit4 doesn't build on
> i386, failed tests 
> Sent: Tue, May 20, 2014 5:44:26 PM 
> 
> 
> Hello, 
> 
> On Tue, 2014-05-20 at 18:14 +0100, Gianfranco Costamagna wrote:
> > Hi Steve and all debian-med developers,
> > 
> > I didn't open a bug, but I would like to let you know that
> > insigntoolkit4 doesn't build on i386 because of two tests failed [1]
> > while on ubuntu doesn't build for another reason [2]
> > 
> > This is preventing many packages to migrate in testing, and I would
> > like to help but the problem is that I cannot reproduce on local
> > pbuilder the test failures.
> I had the same problem - unable to reproduce the problem. I was
> thinking
> about adding something to the d/rules file to dump the test log if
> dh_auto_test fails so that it also ends up in the pbuilder log to at
> least see why the tests fail.
> 
> For the Ubuntu build gccxml fails to run, probably because they use an
> older gccxml (2013xxx) version compared to 2014xxx currently in
> unstable. Maybe moving to the new gccxml version will fix that
> problem. 
> 
> best,
> Gert 
> 
> 
> > 
> > 
> > [1]
> >
> https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit4&arch=i386&ver=4.5.2-1&stamp=1397463745
> > [2]
> >
> https://launchpad.net/ubuntu/+source/insighttoolkit4/4.5.2-1/+build/5938916
> > 
> > 
> > 
> > cheers,
> > 
> > Gianfranco
> 
> > 
> > 
> > _______________________________________________
> > Debian-med-packaging mailing list
> > Debian-med-packaging at lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20140521/b2ecc442/attachment.sig>