Source: blockdiag
Version: 1.5.3+dfsg-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
> f73d6000-f73d7000 r--p 00022000 ca:02 6950262                            
> /lib/i386-linux-gnu/ld-2.24.so
> f73d7000-f73d8000 rw-p 00023000 ca:02 6950262                            
> /lib/i386-linux-gnu/ld-2.24.so
> f73d8000-f7733000 r-xp 00000000 ca:02 6822683                            
> /usr/bin/python2.7
> f7733000-f7734000 rwxp 00000000 00:00 0 
> f7734000-f7735000 r--p 0035b000 ca:02 6822683                            
> /usr/bin/python2.7
> f7735000-f7795000 rw-p 0035c000 ca:02 6822683                            
> /usr/bin/python2.7
> f7795000-f77aa000 rw-p 00000000 00:00 0 
> f90e4000-f96dc000 rw-p 00000000 00:00 0                                  
> [heap]
> ff8b3000-ff8d4000 rw-p 00000000 00:00 0                                  
> [stack]
> Aborted
> E: pybuild pybuild:283: test: plugin distutils failed with: exit code=134: cd 
> /<<BUILDDIR>>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m 
> nose 
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:13: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   
http://aws-logs.debian.net/2017/04/18/blockdiag_1.5.3+dfsg-1.1_testing-i386.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to