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

Re: itk-4.5 and python



> > OK, thanks!  I'll run a build and upload.
> 
> Mmm.  It failed again:
> 
> The following tests FAILED:
>         1813 - itkSimpleImageRegistrationTestFloat (Failed)
> Errors while running CTest
No, I didn't see this, never. 

> I have an amd64 system but did the build in a 32-bit chroot.  This is the same 
> chroot that I successfully used a week ago.  (Well, except that I did apt-get 
> update to the latest stuff last night)
The changes I did to the package should not be able to induce a failing
test of a non-python part. 

I use a cowbuilder based pbuilder environment installed by using the
Neurodebian scripts. I thing it always runs an "apt-get update" before
it starts the actual build. The latest packages in the package cache are
from March/22. I started a new build now  and it says: 

 Upgrade the following packages:                            
1)      cpp-4.8 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]          
2)      g++-4.8 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]          
3)      gcc-4.8 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]          
4)      libasan0 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]         
5)      libatomic1 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]       
6)      libgcc-4.8-dev [4.8.2-16 (now) -> 4.8.2-17 (unstable)]   
7)      libgcc1 [1:4.8.2-16 (now) -> 1:4.8.2-17 (unstable)]      
8)      libgomp1 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]         
9)      libitm1 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]          
10)     libquadmath0 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]     
11)     libstdc++-4.8-dev [4.8.2-16 (now) -> 4.8.2-17 (unstable)]
12)     libstdc++6 [4.8.2-16 (now) -> 4.8.2-17 (unstable)]       

I will let it run and then we will see if this upgrade introduces some
regression. 

> I also wanted to ask: do you build in parallel or not?
Wenn I use svn-buildpackage directly in my installation then yes, when I
use the pbuilder environment not, mainly because I use the NeuroDebian
nd_build scripts that run build for both, 32 bit and 64 bits, and I
haven't figured out how I can pass a the parallel build flag. The other
reason is that I still have to do some work on this machine.

Get back to you tomorrow when the build is finished (one way or the
other). 

regards, 
Gert 

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: