Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

2017-03-23 Thread Radovan Birdic
Hi,

I tried to run tests from chroot and all tests executed successfully but 
execution takes a long time:

> real  804m47.257s
> user  43m32.480s
> sys   760m33.150s

On 21/03/17 11:47, Dejan Latinovic wrote:

> One solution could be to blacklist atlc on boards without FPU,
> the other solution could be to disable benchmark.test on MIPS.

I have created and attached a patch which disables this tests.
With this patch package builds successfully, without benchmark.test execution.

Regards,
Radovan--- atlc-4.6.1_orig/debian/rules	2011-12-26 07:50:12.0 +
+++ atlc-4.6.1/debian/rules	2017-03-23 08:40:37.763877641 +
@@ -7,7 +7,7 @@
 # from having to guess our platform (since we know it already)
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
+DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
 
 CFLAGS = -Wall -g
 
@@ -21,6 +21,10 @@
 endif
 
 config.status: configure
+ifeq ($(DEB_HOST_ARCH_CPU), $(filter $(DEB_HOST_ARCH_CPU), mips mipsel))
+	sed -e '/s*\tbenchmark.test/d' -i tests/Makefile.in
+	sed -e 's/\tWARNING-The-next-test-is-a-benchmark-and-takes-a-long-while.test \\//g' -i tests/Makefile.in
+endif
 	dh_testdir
 	cp -f /usr/share/misc/config.sub config.sub
 	cp -f /usr/share/misc/config.guess config.guess


Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

2017-03-19 Thread Adrian Bunk
On Sun, Mar 19, 2017 at 07:28:47AM -0600, Bdale Garbee wrote:
> Adrian Bunk  writes:
> 
> > Now one test is taking over 6 hours (is that completely hanging?).
> 
> I have no idea.  Never seen that happen.  Makes me wonder what's changed
> in your kernel or toolchain since the last build?

Nothing of this is "mine", this is a build failure seen on the
Debian buildds:
  https://buildd.debian.org/status/logs.php?pkg=atlc=mips

The latest successful build was in 2011 using gcc 4.6 on a machine 
running kernel 2.6.32

The failing attempts are with gcc 6 and kernel 3.16

> Bdale

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

2017-03-19 Thread Bdale Garbee
Adrian Bunk  writes:

> Now one test is taking over 6 hours (is that completely hanging?).

I have no idea.  Never seen that happen.  Makes me wonder what's changed
in your kernel or toolchain since the last build?

Bdale



signature.asc
Description: PGP signature


Bug#858095: atlc FTBFS on mips: Build killed with signal TERM after 360 minutes of inactivity

2017-03-18 Thread Adrian Bunk
Source: atlc
Version: 4.6.1-1
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=atlc=mips

...
PASS: 13a-check_rect_cen_in_rect.test
PASS: 13b-check_rect_cen_in_rect.test
PASS: 13c-check_rect_cen_in_rect.test
PASS: 13d-check_rect_cen_in_rect.test
PASS: 14a-check-circ-in-rect.test
PASS: 14b-check-circ-in-rect.test
PASS: 14c-check-circ-in-rect.test
PASS: 14d-check-circ-in-rect.test
PASS: WARNING-The-next-test-is-a-benchmark-and-takes-a-long-while.test
E: Caught signal ‘Terminated’: terminating immediately
make[3]: *** wait: No child processes.  Stop.
make[3]: *** Waiting for unfinished jobs
make[3]: *** wait: No child processes.  Stop.
make[2]: *** wait: No child processes.  Stop.
make[2]: *** Waiting for unfinished jobs
make[2]: *** wait: No child processes.  Stop.
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
Build killed with signal TERM after 360 minutes of inactivity


The latest successful build of the same source took 17 minutes.
This includes configuring, building and running all tests.

Now one test is taking over 6 hours (is that completely hanging?).