On Wed, Sep 30, 2015 at 11:26:39AM -0300, Miguel Landaeta wrote: > BTW, can another builds be retried?
yes, every team member has a mean to schedule packages for building.
> I was interested on retriggering jruby build since is tagged as FTBFS
> since some days ago and I know for sure is not FTBFS. When I inspect
> the log for the failed build I found out[1] an incomplete log file, so
> I suspect it was also a disk space related problem as well.
personally I don't think it's caused by ENOSCP, but I scheduled it
anyway.
The last build lasted 43213 seconds, and we timeout builds at 12 hours
(with SIGTERM) and 12h6m with SIGKILL. so it reached the timeout and
all those errors are from some java thinghy erroring out due to SIGTERM,
imho.
From a look at the past builds this seems to be started with the 1.7.22
upload:
id name version suite architecture status
build_date build_duration builder
----- ---------- ---------- ---------- ------------ ---------------
---------------- -------------- -------------
24387 jruby 1.5.6-9 testing amd64 unreproducible
2015-03-26 15:22 1991
50111 jruby 1.5.6-9 testing amd64 unreproducible
2015-04-17 12:26 992
68362 jruby 1.5.6-10 unstable amd64 unreproducible
2015-05-05 09:20 1096
73002 jruby 1.5.6-10 testing amd64 unreproducible
2015-05-08 14:20 1361
11257 jruby 1.5.6-10 unstable amd64 unreproducible
2015-06-03 03:31 1263
13163 jruby 1.7.19-1 experiment amd64 FTBFS
2015-06-16 02:40 3
13473 jruby 1.7.19-1 experiment amd64 unreproducible
2015-06-17 07:51 2791
13552 jruby 1.5.6-10 testing amd64 unreproducible
2015-06-17 20:14 1125
13866 jruby 1.7.20.1-1 experiment amd64 FTBFS
2015-06-20 06:57 1428
14090 jruby 1.7.20.1-2 unstable amd64 unreproducible
2015-06-21 16:01 2630
14612 jruby 1.7.20.1-2 testing amd64 FTBFS
2015-06-28 11:36 18
16076 jruby 1.7.21-1 unstable amd64 FTBFS
2015-07-11 02:49 157 beta/55072
16720 jruby 1.7.21-1 testing amd64 FTBFS
2015-07-16 05:00 39 gamma/55754
18549 jruby 1.7.21-2 unstable amd64 unreproducible
2015-07-29 22:09 7979 zeta/23067
18852 jruby 1.7.21-2 testing amd64 FTBFS
2015-08-01 12:01 60 zeta/23429
21071 jruby 1.7.21-2 testing amd64 depwait
2015-08-13 22:28 19 alpha/60854
22091 jruby 1.7.21-2 testing amd64 depwait
2015-08-21 23:58 32 gamma/62859
24007 jruby 1.7.21-2 testing amd64 depwait
2015-09-03 15:50 34 gamma/65105
24398 jruby 1.7.21-2 unstable armhf FTBFS
2015-09-05 15:04 19278 armhf_3/325
24548 jruby 1.7.21-2 unstable armhf FTBFS
2015-09-06 18:41 16542 armhf_1/459
25272 jruby 1.7.21-2 testing amd64 depwait
2015-09-10 19:49 45 amd64_3/753
26175 jruby 1.7.21-2 unstable amd64 unreproducible
2015-09-16 10:09 2602 amd64_8/1634
26537 jruby 1.7.21-2 unstable amd64 FTBFS
2015-09-17 22:35 2768 amd64_4/3308
26629 jruby 1.7.22-1 unstable amd64 FTBFS
2015-09-18 00:34 43213 amd64_6/3043
26771 jruby 1.7.22-1 unstable armhf FTBFS
2015-09-18 22:49 25378 armhf_2/587
27150 jruby 1.7.21-2 testing amd64 FTBFS
2015-09-20 01:32 44709 amd64_3/2590
28098 jruby 1.7.22-1 testing amd64 depwait
2015-09-24 23:24 234 amd64_13/1021
28121 jruby 1.7.22-1 testing amd64 FTBFS
2015-09-25 00:09 12191 amd64_9/2831
Everything I said can be true for unstable, but not for testing, since
the failure there happens only in the second build with tests errors:
3354 files, 19543 examples, 52878 expectations, 5 failures, 4 errors
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
